Hi Wang Rui, To help out with the migration to your new plugin I've moved the include/osgDB/Serializer header out of the OSG and back into VirtualPlanetBuilder where it was originally located. This move insulates VPB from changes you've made to Serializer so we'll be able adopt your version and not worry about accommodating the old usage model, and not worry about breaking the VPB build.
At a later date we can migrate VPB across to the new IO scheme, but right now it can just run along using the old style Input/Output/Serializer scheme. Another step I'm considering is refactoring the DotOsgWrapper could out of osgDB::Registry and placing it in its own singleton class. Thankfully apps use the the proxy singleton which hides the registration implementation so we'll be able to make such changes without breaking backwards compatibility. It might be that we'll want to have a OldDotOsgWrapperManager and NewStyleWrapperManager as classes that the osgDB::Registry owns, the NewStyleWrapperManger being just a place holder name for what your osg2 plugins Registry class is. Another thought I'm playing with is where to place all the wrappers, both old and new. For instance we could collect all the old .osg related plugins together and place them in separate deprecated native IO support sub directory, and then have the new wrappers in their own sub-directories - a bit like what we have right now for osgIntrospection's src/osgWrappers/ collection. Potentially we could name these various plugins differently as well - such as osgio_nodekitname as in your earlier suggestion. Robert. _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
