Hi All, I would like feedback from members of the community on whether the use osgIntrospection, and if so how. I get the sense that this particular component of the OSG is not widely used, and largely ignored by projects that are providing integration of the OSG with other programming languages. I would like feedback on why this is.
I am currently reviewing Wang Rui's excellent efforts on a new extensible native ascii and binary format, that looks well placed to replace the existing .osg and .ive formats as the standard file formats for the OSG. This means we'd be able to deprecate the old .osg and .ive formats and just keep this for backwards compatibility for those who need it. Wang Rui's work provides hand built wrappers for class properties, the wrappers are actually more straight forward to develop and maintain than either the .osg or .ive wrappers, and of relevance to this thread, potentially opens the door for a generic scheme for access classing properties that use these wrappers. Could the new scheme deprecate much of the features of osgIntrospection as well as the old .osg and .ive formats? osgIntrospection does of course provide more than just ability to set and get properties, it enables you to call methods as well, is this critical? Could this be added to Wang Rui's new plugin? What parts of osgIntrospection do you use now? What parts are critical? Given the potential of these various developments and the what appears to me a relative lack of activity around osgIntrospection I'm wondering whether we should slim the core OSG distribution down by moving osgIntrospection and the associated wrappers out into a separate distribution that wraps up genwrapper, osgIntrospection and the wrappers into a single package that can maintained independently, but in sync with OSG distributions. Thoughts? Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
