On 9/20/06, Chris Hanson <[EMAIL PROTECTED]> wrote:
Robert Osfield wrote:
> Further to the integration story is that awkwardness of getting
> different types of viewers setup in the multitude of windowing libraries
> that exist today. Making it easier to build 3d viewers into your
> existing or new apps is something that I feel strongly about. This what
> the osgViewer library I've previously talked about is really about.
This is possibly the only item of the ones listed that I would be useful with. I've
been trying to modularize some of the osgviewer code so that more bits of it are publicly
accessible from applications built one osgviewer. I plan to continue this, and at some
point perhaps there will be guidance on how to make osgviewer more of a proper library.
This fits well with what my company's application requires so I'm easily able to
justify contributing to it.
I would like to replace osgProducer::Viewer and osgGA with a set of classes that are more flexible and easier to integrate with other windowing libraries. The osgViewer::Viewer class would be need to do all the osgProducer::Viewer can do, but also encompass a much wider range of usage styles - such as multiple independent windows, multiple scenes, as well as multiple depdent and indepdent cameras that share these resources. The osgGA event system would also be part of this revamp.
Help in development of an osgViewer library would be great, but I'd need to get some basic code out before first. osgProducer::Viewer itself could be made more flexible, but there are real limits to its design and doesn't do the OSG or Producer real justice, so I'm inclined to not to continue too hard flogging this old horse.
Robert.
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
