|
»
»
»
« Return to Thread: Shader Preview Panel Dev Question
Re: Shader Preview Panel Dev Question
by Timothy M. Shead
::
Rate this Message:
Alex Curtis wrote:
> Right I have got the File IO part done (using k3d IO of course) -> Needs
> to be a bit more robust but will do for now.
>
> The next stage is getting a render (initializing an external render
> engine) done using a geometry object.
>
> Now I think the best way of doing this, is to create a new document (one
> you wont be able to play with). this document will set up with the
> geometry and camera specifics etc. Then k3d render facilities will be
> called using the document and the chosen render engine (rEngine
> selection bit done).
>
> Put simply can I do this.. create a new document? ... Is this the best
> way?.. I could go the root of creating render input files etc, but thats
> a lot of work to cover all k3d supported render engines. I may as well
> use stuff already provided.
>
I sort-of alluded to this in my reply to your earlier question. The
answer is that yes, you *can* create a "hidden" document and use it in
this way, but I don't think you want to (I'm willing to hear
counterarguments). The issue is that it is reasonable to (eventually)
give the user control over what happens - what sort of primitive to
render with (sphere, cylinder, plane, user-specified geometry) and how
to render (choice of render engine, details affecting quality /
performance tradeoffs, etc). As soon as you start giving the user that
control, they won't want to have to reproduce all their choices every
time they start the program. That means serialization, which may as
well be in the same document the user is working-on. After all, if they
*are* going to provide user-specified geometry for previewing, that
geometry has to come from somewhere, and it logically ought to come from
the current document. Same for all the hundreds of render-engine
parameters that are available. So I really do see your panel as working
with the contents of the current doc.
Cheers,
Tim
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development
> Right I have got the File IO part done (using k3d IO of course) -> Needs
> to be a bit more robust but will do for now.
>
> The next stage is getting a render (initializing an external render
> engine) done using a geometry object.
>
> Now I think the best way of doing this, is to create a new document (one
> you wont be able to play with). this document will set up with the
> geometry and camera specifics etc. Then k3d render facilities will be
> called using the document and the chosen render engine (rEngine
> selection bit done).
>
> Put simply can I do this.. create a new document? ... Is this the best
> way?.. I could go the root of creating render input files etc, but thats
> a lot of work to cover all k3d supported render engines. I may as well
> use stuff already provided.
>
I sort-of alluded to this in my reply to your earlier question. The
answer is that yes, you *can* create a "hidden" document and use it in
this way, but I don't think you want to (I'm willing to hear
counterarguments). The issue is that it is reasonable to (eventually)
give the user control over what happens - what sort of primitive to
render with (sphere, cylinder, plane, user-specified geometry) and how
to render (choice of render engine, details affecting quality /
performance tradeoffs, etc). As soon as you start giving the user that
control, they won't want to have to reproduce all their choices every
time they start the program. That means serialization, which may as
well be in the same document the user is working-on. After all, if they
*are* going to provide user-specified geometry for previewing, that
geometry has to come from somewhere, and it logically ought to come from
the current document. Same for all the hundreds of render-engine
parameters that are available. So I really do see your panel as working
with the contents of the current doc.
Cheers,
Tim
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development
« Return to Thread: Shader Preview Panel Dev Question
| Free Forum Powered by Nabble | Forum Help |