Hi All, I'm mainly just tracking this thread trying to get a feel for what's working an what's not, and who might be able to help refine the right approach. So for nothing concrete has jumped out..
2009/5/13 René Molenaar <[email protected]>: > Have you seen David Guthries implementation (posted a few days ago), it uses > windowsystemwrapper to integrate osg/qt? No I haven't, was this posted on osg-users? Did I miss it spinning past a 100 knots? I don't know if it's related, but one design aspect to osgViewer which was built in front the start is the osg::GraphicsContext::WindowSystemInterface which provides the abstraction away from the implementation. This interface class was the potential of having multiple implementations, and for the implementations to be moved out into plugins, just like we have plugins for databases and wrappers right now. For ease of building and running OSG apps I didn't go for the full plugin approach from WindowSystemInterface, rather allowed implementations from X11, Win32, Carbon and Cocoa to be imbeded directly into the osgViewer. This means you only have to link against osgViewer to get a viewer up on the screen, but it does mean that the library itself isn't as flexible w.r.t dynamically loading the implementations. It wouldn't be a great deal of work to do this though. Or perhaps we could still have the inbuilt implementations, but allow plugins to add extra ones. A plugin for Qt support would certainly be possible. Potentially one could even compile the core osgViewer library without any default implementation and rely on such a plugin, or change the default implementation that one compiles against. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
