 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I don't know it is good idea to stress TEAM with feature requests for non
existing version but I can't wait ;-)
I thought about something like 'project' and 'project manager' to link many
scripts with no connections. Not changed scripts are parsed once and stay in the
memory when not changed. Changed scripts are distributed between threads.
For example I open project with files people.pov, trees.pov, enviroment.pov,
mountains.pov. I start parsing. Parser checks number of processors (for example
P1 and P2) and distribute parsing jobs - people.pov to P1 and trees.pov to P2.
But trees.pov is long macro so people.pov finished and P1 takes enviroment.pov
and mountains.pov. I imagine these scripts have separated name-space but puts
generated objects into one object-space in memory. But every object generated
with it remember its original part of project. I don't know how renderer is
separated into threads. I though only about parser now. So when render is
finished I want change only color of the sky or light. Project manager checks
what part of project is changed and parses only enviroment.pov (or other parts
if I changed inlude files used by other scripts). Before parsing objects from
changed part are removed from object-space. I save time for parsing trees and
other things. If there were isosurface with 'evaluate' in not changed part then
it not calculate max_gradient again.
Sorry if reading was wasting of your time. It was my idea from yesterday bus.
ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> I don't know it is good idea to stress TEAM with feature requests for non
> existing version but I can't wait ;-)
>
> I thought about something like 'project' and 'project manager' to link many
> scripts with no connections. Not changed scripts are parsed once and stay in the
> memory when not changed. Changed scripts are distributed between threads.
>
> For example I open project with files people.pov, trees.pov, enviroment.pov,
> mountains.pov. I start parsing. Parser checks number of processors (for example
> P1 and P2) and distribute parsing jobs - people.pov to P1 and trees.pov to P2.
> But trees.pov is long macro so people.pov finished and P1 takes enviroment.pov
> and mountains.pov. I imagine these scripts have separated name-space but puts
> generated objects into one object-space in memory. But every object generated
> with it remember its original part of project. I don't know how renderer is
> separated into threads. I though only about parser now. So when render is
> finished I want change only color of the sky or light. Project manager checks
> what part of project is changed and parses only enviroment.pov (or other parts
> if I changed inlude files used by other scripts). Before parsing objects from
> changed part are removed from object-space. I save time for parsing trees and
> other things. If there were isosurface with 'evaluate' in not changed part then
> it not calculate max_gradient again.
>
> Sorry if reading was wasting of your time. It was my idea from yesterday bus.
>
Next step: you put a mouse interface and end-up with yet another GUI-modeler...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Please do not quote the whole message when replying. I would guess most of
us use threading newsreaders so we have the previous message.
news:3C04B82D.A8A98279@atosorigin.com...
> Next step: you put a mouse interface and end-up with yet another
GUI-modeler...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
<jer### [at] atosorigin com> wrote:
> Next step: you put a mouse interface and end-up with yet another GUI-modeler...
Thanks for the sarcasm but I don't see anything GUI- and platform-specific in my
idea. The MAKE tool is base for nearly every advenced tool. Checking time of
modification is very easy just like allocation and freezing of memory. You don't
need mouse for it.
ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
