To continue 1.4 dreams... I know that there will be some support for pluggability for occlusion system, maybe also some other parts. There will be probably support for StencilBuffer, maybe also shaders. But all this stuff is given subset of 3d possibilities. Before we will see 1.4, some new extensions will pop up, with no chances to be supported for next two or three years...
My question is, if there will be any chance of adding _native_ extensions to java3d. Stuff like displacement mapping, hardware occlusion helpers etc. Some of the could be possibly added independent, but some of them would need access to java3d internals. I would imagine this as some kind of plugin/extension mechanism - every such feature would have to be provided separately for each binding/platform, but could be exposed by same api for java3d. Native method would be called, with binding-specific data passed to it. I know that this is hard to do properly. I probably even cannot imagine how hard. But without such ability, java3d will be always 2-3 years behind rest of bindings. With such extension mechanism, new possibilities could be added by random people, with some of them migrating to core over time (becoming 'core optional' stuff like cube maps are now). 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".
