Hi Wang, Thanks for the OutputStream.cpp update. I've now merged this with me local version.
I'm currently reviewing the code with a view of see what parts we can extract out and place in osgDB. I see that you adapted/greatly enhanced osgDB::Serializer, merging the new an improved one mean that I'd have to adapt the code that uses the present Serializer, and the only place that does is VPB, so it should be relatively straight forward. This would then have the knock on effect that VPB's .source ascii format would become an example of the new parsing scheme which is a good thing, the only awkwardness is judging the timing of when to make this change. I'm also looking at how we might start moving the old .osg functionality to become a deprecated feature, and how we might have osgDB decide whether a .osg file is a new one or an old one and choose which of the plugins to load. Me thought is that the ReaderWriterOSG.cpp and ReaderWriterOSG2.cpp implementations might need migrating into osgDB, and the plugins then become the source of the wrappers, just like the osgParticle, osgText plugins do for provide .osg ascii support. With the new support I'm expecting to that temporarily we'll have two sets of these NodeKit plugins one for each type of .osg - the new and the old. During the review I've noted that you have placed any copyright notice on any of the files, or notification of which license they are under. I presume it's the standard OSGPL that you intend, but I can't merged anything until I get confirmation. Cheers, Robert. _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
