Hi Wang Rui,

I have now refactored and merged your osg2 plugin into a combination
of include/osgDB, src/osgDB, src/osgWrappers/serializers/osg and
src/osgPlugins/osg.  In the osg plugin I have placed your
ReaderWriterOSG2.cpp alongside the original plugin rather than attempt
to merge them.  Later down the road I'll look at merging these to
allow the OSG to detect automatically which type of .osg ascii file we
have.

With moving the wrapper classes/macro's into osgDB I've had to put
them into the osgDB namespace, this had a knock on effect of me having
to modify a couple of dozen of the osg wrappers, functionally they
should be the same though - as long as I haven't introduced any typos
;-)

Given that I've tweaked quite a few of the files it would be worth
using the code I've just checked in for any further work you want to
do at your end as merging changes made to your original code will
potentially confuse the merge process.   An svn update will get all
the my changes/restructuring.

I haven't yet done anything about notifying of the deprecation of the
old Input/Output/DotOsgWrapper headers etc.  I will leave the new
wrapper/plugin scheme to be bedded in more before I make any changes
to other parts of the OSG, so for the time being well just run the two
schemes in a parallel.

One thing of note that I would like to change about the new
wrappers/readerwriter is that C++ exception support on embedded
platform is available but not recommend for the cost it brings in
execution size.  This has lead me to avoid using exceptions in all the
core OSG components, including .osg and .ive plugins.  You new codes
re-introduces the dependency so I'd like to find a way to remove this
to keep them all without exceptions.  For the .ive plugin I
implemented a scheme that mimics exceptions a little by setting an
exceptions object on the input/outputstream, my guess is something
similar could probably work just fine with your new codes.

Cheers,
Robert.

Robert.
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org

Reply via email to