![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <Xns94DEB31C7DB23raf256com@203.29.75.35>,
"Rafal 'Raf256' Maj" <spa### [at] raf256 com> wrote:
> Some of us dont have too much time and I assumed that small spelings errors
> want confuse anyone, especialy in advanced group like this one.
If you want to be taken seriously by programmers, you should try to be a
little more professional. This includes using the correct terminology:
it exists for a reason, and misusing it gets in the way of efficient,
clear communication.
Also, programming well requires patience and careful thought, and
rushed-through messages don't give the impression of a patient or
thoughtful person.
> Btw, no chance of incorporating most important innovations from i.e. SDLPov
> (like HDR) into 3.6 :( ?
No, there is no chance. 3.6 is primarily bug fixes and internal
restructuring, and in any case, is already far along in the public beta
stage. There will be no major feature additions in 3.6, and at this
point, only minor bug fixes which can be fully implemented and tested in
time for release.
--
Christopher James Huff <cja### [at] earthlink net>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: <chr### [at] tag povray org>
http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
cja### [at] earthlink net news:cjameshuff-
B8516F.09483705052004@news.povray.org
> No, there is no chance. 3.6 is primarily bug fixes and internal
> restructuring, and in any case, is already far along in the public beta
> stage. There will be no major feature additions in 3.6, and at this
> point, only minor bug fixes which can be fully implemented and tested in
> time for release.
Sorry for being so "fast", but I realy am interested in this - when we
could expect official PovRay to have HDRI (and other greate pathces like
highfield fix, 4D noise by slime, .hdr output etc) - (version/date).
Is it like a month and 3.7, or more like a year and 4.0 ?
Maybe authors of un-official version should have guidelines about writting
patches, so that their code could be easly incorpotated into official Pov
and allow it to grow faster? And some licence agreement template to allow
TAG to modyfie and use their donated code.
PovRAY is realy greate :)
--
http://www.raf256.com/3d/
Rafal Maj 'Raf256', home page - http://www.raf256.com/me/
Computer Graphics
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <Xns94E0F14E55E3Fraf256com@203.29.75.35>,
"Rafal 'Raf256' Maj" <spa### [at] raf256 com> wrote:
> Sorry for being so "fast", but I realy am interested in this - when we
> could expect official PovRay to have HDRI (and other greate pathces like
> highfield fix, 4D noise by slime, .hdr output etc) - (version/date).
>
> Is it like a month and 3.7, or more like a year and 4.0 ?
No.
We do not give release dates. We will not, period. And aside from that,
given that 3.6 hasn't reached final release yet, what makes you think
there will be a 3.7 released in a month, or 4.0 in a year?!? Or that we
have any kind of final feature list for these non-existent versions?
> Maybe authors of un-official version should have guidelines about writting
> patches, so that their code could be easly incorpotated into official Pov
> and allow it to grow faster?
If you would look at the MegaPOV project, you would see that they do
have such guidelines. This is fairly irrelevant to how long it takes to
include something in the official version, because most of the time to
include a patch is taken by redesign of the code and syntax, and then
extensive testing in private, then public betas. As has been said many
times, making an official release consists of far more than throwing a
bunch of patches in and getting it to compile!
> And some licence agreement template to allow
> TAG to modyfie and use their donated code.
The POV Team asks permission of the author, using donated code usually
isn't a problem. And the TAG has little to do with this.
--
Christopher James Huff <cja### [at] earthlink net>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: <chr### [at] tag povray org>
http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |