I'm wondering if there are any, even vague, ideas about how java3d 1.4
will look like. It targets extensibility, access to low level structures
etc. Things like vertex or pixel shaders are actually quite easy - I
worry about pluggable occlusion schemes, access to display lists etc.
Would it be possible to expose lower level api and then implement
current java3d on top of it ? Possibly making some internals public,
like visibility system - allowing people to substitute single parts of
java3d engine with their own classes.
At some point I was wondering if java3d retained mode was pure-java on
top of immediate mode. It is not true (especially performance wise), but
this would be kind of thing I now talk about - just with explicit
pluggable components for visibility system, material management,
collisions etc. Maybe making java3d internal message system public would
be a workable compromise ?
How such things would affect performance ? Maybe nio.Buffers would help
a bit to cross java/native barier ? Especially for all these stencil/etc
stuff ?
Artur
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
