I have been watching the evolution of OSG away from Producer with interest.
I haven't played with any of the new stuff yet because I was waiting to let
the dust settle a bit and see where things are going.
osgProducer::Viewer development ended up going down the route of
integrating a wide range of functionality - the big areas were:
statistics
state manipulation
saving to file
multiple camera manipulator selectable from a key press
escape key sets done
If you didn't want these then you'd have to switch them off via the
Viewer::setUpViewer(uint optionsMask).
All of these features of osgViewer are occasionally useful to me, though
I don't use any of them every day.
Now osgviewer is an app that I have used a lot for testing purposes
and model investigation purposes through the years. Facilities likes
stats, state manipulation and multiple cameras are all pretty useful
tools. So I'd like to port osgviewer across to osgViewer::Viewer, and
add these items one by one.
Since you're going to add these items, can you add them in a way that
makes it easy for user applications to add them too, perhaps with a line
or two of code? That way applications that don't need them don't need to
request them.
I don't know what you have planned for osgGA, but how do manipulators
fit into the new viewer? My application has a custom manipulator; how
much work will it be to convert my application to use the new viewer?
I very much depend on Producer's ability to be configured from a file;
is there such a facility in the new viewer? I need to decide whether to
stay with Producer or not.
--
____ __ Eric Sokolowsky (GST) NASA Goddard Space Flight Center
/ __/__/_/__ Visualization Programmer Scientific Visualization Studio
/ __/ _/ / _/ 301.286.3751 Mailstop 610.3 Bldg 28 Rm E102
/___/_//_/__/ [EMAIL PROTECTED] Greenbelt, MD 20771
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
