On 8/9/07, Marcus Lindblom <[EMAIL PROTECTED]> wrote: > Allen Bierbaum wrote: > > Marcus Lindblom wrote: > > > >> Hi all, > >> > >> How are things going with PyOpenSG, are there any cute code examples to > >> look at? > >> > > > > You can see the latest code here: > > https://realityforge.vrsource.org/trac/pyopensg > > > Looks very nice! > > We are actively using it on a couple of production projects and are > > refining it as we find bugs/limitations. The most difficult part right > > now is that the HEAD of pyOpenSG is tracking the HEAD of the stable > > branch of OpenSG 2.0. What this means to a user is that the code may > > break/change from one day to the next. This is good in that development > > is moving quickly, but it is bad because things could break under your feet. > > > Good news! This means I can start hacking at it and OpenSG 2.0 at the > same time, when time comes. (Hopefully this autumn). > > As I said earlier, we use Windows, and IIRC you don't, so that would be > something to work with. Hopefully, there shouldn't be any showstoppers > and I'd be happy to contribute.
Actually we are using OpenSG 2.0 and PyOpenSG on Windows just as much as Linux. :) > > A slightly different question: (that's still relevant for > OpenSG/PyOpenSG users) (I'm a bit of a python-cpp-wrapper beginner (have > worked with JNI a bit though), so this might be a silly question): > > How easy it is to use PyOpenSG together with some of my own C++ classes > that are also wrapped (at least with boost::python, maybe with > pyplusplus)? I.e. do PyOpenSG employ any tricks that other users > wrapping their own OpenSG-code should be aware of (or should borrow)? Nope, as long as you wrap your code with Boost.Python everything should work fine. > > The wiki is pretty much dead. We moved most of our open source projects > > over to the same trac site that is hosting OpenSG. > > > Ok. A note there pointing ppl to the new site perhaps? Good point, Allen I don't have edit rights, can you look into this? > Also, shouldn't this be touted as a OpenSG 2.0 upcoming feature? :) Yep, we need to make a release so that we can have people test it. I might be able to pull something together pretty quickly so people code do limited testing. But we are no where close to a release yet. -Aron > Cheers, > /Marcus > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Opensg-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/opensg-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
