Hi Wang, Your suggestion of splitting up the examples it to catagories is an interesting one. I'll ponder on this.
As for excepting excepting overlap of functionality as being a good thing, I'm not so sure. Rather I'd much prefer to see properly distinct examples, and where there is a common problem being solved in different ways to unify them where appropriate - sometimes by moving the common functionality into the core OSG. For instance I'd like to see recording movies support in the core OSG, we could us osgscreencapture as a prototype for developing this functionality but in the end the functionality should end up in the core. If we get it right it would just be an extension of the existing ScreenCaptureHandler. Once this is done osgscreencpature could be rewritten or removed entirely. What about osgautocapture and osgposter? Robert. On Tue, Nov 24, 2009 at 8:08 AM, Wang Rui <[email protected]> wrote: > Hi Robert, > > I would suggest dividing the 'examples' directory into multiple > subdirectories, each representing a kind of demonstrations. For > example, we may move osganimate and osganimation* into an 'animation' > subdirectory; osgvnc, osgbrowser, osgpdf and osgwidget* into a > '3dgui'; osgviewer* into a 'viewer'; capturing examples into a > 'capture'; and new and uncertain ones into an 'unsorted', etc. The > only trouble is to have a suitable classification strategy. > > IMHO, this will help end users look for a technique they are > interested in, and make choices among a limited range of > implementations, instead of searching over 140 examples. And I would > say that osgautocapture, osgscreencapture and osgposter are all > distinctive examples, which may be extremely useful sometime, but > inappropriate in other cases. Why not let users themselves decide the > best one to work? :) > > Cheers, > > Wang Rui > > > 2009/11/24 Robert Osfield <[email protected]>: >> Hi Guys, >> >> I'm ready to review osgposter but I'm struck by the issue of OSG >> example duplication - we already have two examples that illustrate >> screen capture - osgautocapture that specializes in loaded the highest >> res tiles of a paged database then capturing the image, and >> osgscreencapture that can record a series of frames. osgposter is >> different from these in pure function, but... perhaps we should be >> combining a two or more of these examples to avoid confusing end users >> about which technique to use. >> >> There is also the possibility of wrapping up some of this capability >> into osgViewer to work as a convenience method for capturing >> screenshots. We have an osgViewer::ScreenCaptureHandler that can >> capture a single frame, perhaps this needs generalize this and then >> have examples that use it rather than their own custom >> implementations. >> >> Thoughts? >> Robert. >> _______________________________________________ >> osg-submissions mailing list >> [email protected] >> http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org >> > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
