Re: [Opensg-core] PyOpenSG?

[Patrick H. <pat...@pr...>]

Dirk Reiners wrote:
> 	Hi All,
> 
> I just had a question about the status of PyOpenSG today here at SIGGRAPH. Can 
> anybidy give me an update on how that is doing? Is it up to date? What does/does 
> not work right now?

PyOpenSG is up to date with r1896 of the OpenSG SVN trunk. I was just trying
yesterday to get it up to date with r2015, but GCC-XML (used as part of the
bindings generation) is crashing while parsing the C++ code. I haven't had
time to try to figure out why, but I expect that I will have to submit a bug
report to the GCC-XML developers. (That's what happened last time anyway.)

As far as what does and doesn't work, that is a broad question. PyOpenSG
currently covers nearly 600 OpenSG classes. The coverage has been more than
sufficient for our company to make heavy use of PyOpenSG on Windows and
Linux. I am trying to keep it working on Mac OS X, but I have limited time
to test on that platform at the moment. The vPresent project
(http://code.google.com/p/vpresent/) also makes excellent use of a lot of
OpenSG features including clustering, although that code is currently based
on OpenSG 2.0 circa June 2007.

One of the in-progress aspects of PyOpenSG is support for the Complex Scene
Manager. Much of the CSM code is covered by PyOpenSG, but I still need to
verify that it is all working. I am very interested to see the CSM be usable
from Python.

Beyond that, it is somewhat difficult for me to be specific about what is
there and what is not. OpenSG offers a great deal of functionality. What
PyOpenSG offers is driven largely by what the users of it need from Python.
Given that the user base is small, the features that are covered by PyOpenSG
are relatively limited compared to what the C++ API provides. The feature
coverage can always be improved upon as the need arises.

 -Patrick


-- 
Patrick L. Hartling
Senior Software Engineer, Priority 5
http://www.priority5.com/

The information transmitted in this communication is intended only for
the person or entity to which it is addressed and contains proprietary
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please destroy any copies, contact the sender
and delete the material from any computer.