> 
>   Let's take, for example, the 'finish' block of POV-Ray. While there are
> quite many parameters to fine-tune, it's still a fixed amount of possible
> parameters. As an example, fresnel reflection is available only because
> it has been added to the core code. However, if you would want to test
> with some other type of reflection algorithm there just isn't an easy
> way (the only way is to modify the source code and recompile the program).

We could imagine this :

- a shading language with it's own syntax (it have to be very
"programmatic"), allowing any algorithm one can imagine

- while, in POV-Ray SDL, existing texture/pigment/normal/finish features
are kept mostly as they are currently, but actually (and transparently 
to user) uses stuff defined in the new shading language.

Each existing pattern, reflection algoritm,... has to be transcribed
in shading language, which would form a huge base of sample code to
start writing new shaders.

Users can limit themselves to existing stuff without re-learning
anything.  Those who'd like to get their hands dirty can do it with
a smooth learning curve.

this would also put all texture-related algorithms out of POV-Ray's main
code, and allow people who aren't high-end programmers to contribute
to an important part of POV-Ray (thus less time spent on it by better
programmers in the re-write process).

(light sources and cameras should also become shaders, ideally, BTW)

note : some years ago, someone made a "POV-Man", which was POV-Ray
with the ability to use RenderMan shaders.  It would be interesting
to find it back and have a look.

Fabien.

Post a reply to this message