Hi Robert Is your app event driven or frame driven?
event driven Does your app have one scene graph, one view, one window? yes Does your app have one scene graph, one view but multiple windows? maybe in future Does your app have one scene graph, multiples views and one or more
windows?
maybe in future Does your app have multiple scene graphs, multiples views and one or
more windows?
no Do you open and close windows regularly in the life of your application? yes Do you need to integrate the OSG viewer functionality into existing
windows?
no Do you need to integrate the OSG viewer functionality into 3rd party
windowing toolkits/applications(i.e. IE/Firefox)?
yes, in my case is Java (I'm using the JOGL context creation for that). Inside JOGL you can use GLCanvas (an awt component) and GLJPanel (a swing component), the first is intended to be used only in awt applications and the second for Swing applicactions. I'm saying that becouse using the GLJPanel component internally uses a mechanism to extract the render and put it on a swing surface (using pbuffers or something compatible), therefore the OpenGL states is changed and OSG shows a warning. I know that is possible to save the state after render, and restore it before calling rendering process. A pair of methods doing that for us, will be very appreciated, if not on any application that we change the state after osg rendering we should to replicate the code. Do you need support for distortion correction/compositing? no Do you have availability of multiple/wish to use CPU cores? yes Do you have availability of/wish to use multiple GPU? no -- Rafa.
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
