What are you moving your customers to place of Java3D?
Right now we have our own scene graph API based on top of JOGL. Unlike Xith3D, our optimisations are for high-end devices, so it is somewhat like a clone of Performer. Multi-pipe/channel rendering, multithreaded stage management to make effective use of multi-CPU machines etc. Eventually we'll move to the output from JSR-231. I'm not particularly happy with the design of JOGL because it has many bad design decisions that really hamstring it running in multi screen displays. For example, for some completely stupid reason they've remove the glSwapBuffer command! ARRRGH..... We can't even do high-level genlocking with the code now. Very, very frustrating. I just hope JOGL isn't the final design that they're going to use for the offical spec.
Thanks also for the great background info!
Heh, watch me get in trouble for saying that much even... :(
-- Justin Couch http://www.vlc.com.au/~justin/ Java Architect & Bit Twiddler http://www.yumetech.com/ Author, Java 3D FAQ Maintainer http://www.j3d.org/ ------------------------------------------------------------------- "Humanism is dead. Animals think, feel; so do machines now. Neither man nor woman is the measure of all things. Every organism processes data according to its domain, its environment; you, with all your brains, would be useless in a mouse's universe..." - Greg Bear, Slant -------------------------------------------------------------------
=========================================================================== 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".
