Hi All, I'd like feedback from the community on what you needs are on the viewer front. The OSG has a huge range of users and different fields so I'd like to hear from you and how you use the OSG w.r.t viewer functionality - i.e. window management, frame management, threading, hardware/OS support, camera view manipulation etc.
It'd be useful to put a set of usage profiles together so that we can ensure that the osgViewer supports these usages, and we also can point new users to the right set of classes for their particular usage style. For instance: Is your app event driven or frame driven? Does your app have one scene graph, one view, one window? Does your app have one scene graph, one view but multiple windows? Does your app have one scene graph, multiples views and one or more windows? Does your app have multiple scene graphs, multiples views and one or more windows? Do you open and close windows regularly in the life of your application? Do you need to integrate the OSG viewer functionality into existing windows? Do you need to integrate the OSG viewer functionality into 3rd party windowing toolkits/applications(i.e. IE/Firefox)? Do you need support for distortion correction/compositing? Do you have availability of multiple/wish to use CPU cores? Do you have availability of/wish to use multiple GPU? Please feel free to add other ways of categorising viewer usage, or actually answer the above. Each of these deserves a discussion in its own right, so it might be appropriate to strike up separate threads on different types of usage and how osgViewer will facilitate these, or even how osgViewer will need to evolve to meet these usages. Thanks in advance, Robert. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
