HI Eric,
On 1/11/07, Eric Sokolowsky <[EMAIL PROTECTED]> wrote:
> 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.
osgViewer uses osgGA for its event handlers and camera manipulatos in
a similar way to that osgProducer::Viewer did. The API can be cleaned
up a bit, so hopefully it'll be a bit more obvious how things plugin
together.
In the case of adding functionality back on the osgViewer::Viewer that
replicates osgProducer::Viewer had - this will be done this custom
even handlers, and by reusing standard ones. A stats handler is
something I need to write, we could possible place this in osgViewer
so that users can just attach it to their views if they need it.
W.r.t configuration from file, this is not supported yet, but will be,
probably by end of month.
Robert.
_______________________________________________
osg-users mailing list
osg-users@openscenegraph.net
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
