 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rafal 'Raf256' Maj wrote:
> war### [at] tag povrayorg news:4093ae13@news.povray.org
>
>
>>>- can I get povray beta 4 source code
>>
>> No.
>
>
> What a warm welcome for someone willing to volunteer some bug-fixing.
>
Hi Rafal, this is nothing personal, they just don't ever release
beta code. There are some good reasons for that and I think you
might have enough experience in programming to come up with a
large number of good reasons yourself.
Andrel
-----------------------------------------
With every new release of Windows TM some things change and some things
stay the same. E.g. the logic behing the hardware configuration will
still be incomprehensible, but it will be incomprehensible in an entire
new way.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
stephen parkinson wrote:
> [...]
>
> pls find attached a build log and a modified optout.h
> apologies for size
Very funny.
You should read the posting guidelines in p.a.f-a-q. Attachments should
not be posted in this group. I can't find a reason why all this stuff
could be of any use for anyone anyway.
Christoph
--
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 01 May. 2004 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <409527d1@news.povray.org>,
stephen parkinson <ste### [at] zmemw16demoncouk> wrote:
> pls find attached a build log and a modified optout.h
> apologies for size
Don't apologize, just don't post it here! Put posts with attachments
where they belong, in the binary groups. In this instance, the proper
group is povray.binaries.programming.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: <chr### [at] tagpovrayorg>
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christoph Hormann wrote:
> stephen parkinson wrote:
>
>> [...]
>>
>> pls find attached a build log and a modified optout.h
>> apologies for size
>
>
> Very funny.
>
> You should read the posting guidelines in p.a.f-a-q. Attachments should
> not be posted in this group. I can't find a reason why all this stuff
> could be of any use for anyone anyway.
>
> Christoph
>
apologies, i did try to reply off list
and asked for a correct address to avoid a spam-bot reply
i think i posted this reply a bit prematurely in response to the spam-
bot reply
he was asking for howto compile instructions and install for user fred,
so i did
once again apologies, won't happen again
stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <Xns94DC9D68E435Fraf256com@203.29.75.35>, "Rafal 'Raf256' Maj"
<spa### [at] raf256com> wrote:
> - what commend from console write to compile from sources povray?
Not "commend", it is spelled "command" and that is still the wrong word. In
a programming language this is called "function". There is no problem with
making spelling mistakes, but please try to learn at least the basic English
terms and don't use them randomly throughout your message - it would make
reading your posts much easier!
> - with *.c file is responsible for interpolation in denisty_map
As density is a pattern, it would make sense to look at where all pattern
functions are implemented - in the files with just that name ;-)
> - can I get povray beta 4 source code,
No, obviously we do not make beta source code available if we don't want
non-time-limited beta versions. Use POV-Ray 3.5 source code to make your
patches or just wait a few more weeks for the 3.6 source code release.
> since I want to try to fix bug
> Xns94DB1FBCC42DAraf256com@203.29.75.35 (see below)
This isn't a bug at all.
> - whitch code is responsible for parsing density_map interpolation options,
> with funcion is used to "throw" parse-error?
This is really easy to find...
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
tho### [at] trfde news:4095e92c$1@news.povray.org
> Not "commend", it is spelled "command" and that is still the wrong
> word. In a programming language this is called "function". There is
> no problem with making spelling mistakes, but please try to learn at
> least the basic English terms and don't use them randomly throughout
> your message - it would make reading your posts much easier!
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.
>> - with *.c file is responsible for interpolation in denisty_map
> As density is a pattern, it would make sense to look at where all
> pattern functions are implemented - in the files with just that name
> ;-)
> This isn't a bug at all.
As You wrote in beta-test, this is new type of interpolation.
But its results are realy odd IMHO. I.e. galaxy.df3 looks very strange when
rendered with that interpolation. IMHO this code should be double-checked.
Btw, no chance of incorporating most important innovations from i.e. SDLPov
(like HDR) into 3.6 :( ?
--
http://www.raf256.com/3d/
Rafal Maj 'Raf256', home page - http://www.raf256.com/me/
Computer Graphics
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1 May 2004 09:29:55 -0400, "Rafal 'Raf256' Maj" <spa### [at] raf256com> wrote:
>- with *.c file is responsible for interpolation in denisty_map
http://megapov.inetart.net/manual/internals.html#architecture
> - whitch code is responsible for parsing density_map interpolation options,
Probably you are looking for such cryptic name like
"Parse_Media_Density_Pattern" and ...
> with funcion is used to "throw" parse-error?
... "Parse_Error"
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <Xns94DEB31C7DB23raf256com@203.29.75.35>,
"Rafal 'Raf256' Maj" <spa### [at] raf256com> 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] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: <chr### [at] tagpovrayorg>
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
cja### [at] earthlinknet 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <Xns94E0F14E55E3Fraf256com@203.29.75.35>,
"Rafal 'Raf256' Maj" <spa### [at] raf256com> 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] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: <chr### [at] tagpovrayorg>
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
