Hi Robert, There is another usage of this documentation included inside osgIntrospection. OSGEdit could benefit from it when the osgIntrospection support is finished. I could use the attributes documentation to automatically show tooltips in every editable attribute...
Btw, I'm not dedicating a lot of time to the osgIntrospection port of OSGEdit, it will not be released soon, sorry :( But I keep advancing as I get time... Regards. El vie, 22-09-2006 a las 17:06 +0100, Robert Osfield escribió: > A thought occured to me the other while I was waiting for a rebuild of > the osgIntrospection wrappers, that perhaps we could have an option in > osgIntrospection for having a documentation string for each namespace, > class and member function/variable. This documentation string would > be one of the doxygen strings that are embedded in header files. > You'd want to make this optional, as it'd be a bit more bloat to > wrappers, but it should be too hard to add since genwrapper is based > around doxygen anyway. > > So once you have a documentation string, and a suitable > scripting/interpreted language like Lua or Phython you can have a > script console window in your app that you could do something like: > > help(node) > > Or > > help(node:getChild(i)) > > This was my thought. Would it be useful? That bit I can only > speculate on. > > Thoughts? > > Robert. > _______________________________________________ > osg-users mailing list > [email protected] > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
