> Introspection is very powerful, but even for languages that provide good > capabilities in this area, like java or c#, nobody is building wrappers > that use introspection AT RUNTIME. This adds a huge overhead, which is
I tend to agree. Also, using osgIntrospection limits the Python API to what C++ can do and, as a Python familiar, this is not desirable. :) > PS I the past 6 months I have created (yet another) set of Python > bindings. These are made with SWIG. I've used them a lot for all sorts I thought about making Swig bindings to get a low-level binding and then write my own hihg-level API. If you can provide me with the means of accessing C++ objects via Python I would be happy to help you write a higher-level API that is more Pythonic and powerful. Would you mind sharing/showing what you have done so far? Also, I thought that all these (swig/boost/whatever) were fairly automatic in the way they work. That is, they look at C++ code and generate more C++ code to make Python bindings. Using things like gccxml could make much of the process even more automatic. Unfortunately, because C++ and Python have totally different methods for development I would rather like to see a Python API for the OSG libraries rather than a C++/Python 1:1 mapping. /Peter _______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
