Patrick Hartling wrote:
> On Nov 6, 2008, at 8:46 AM, Marcus Lindblom wrote:
>> Ok? But.. the trac browser shows absolutely no commits other than a copy
>> to create the branch from trunk?
>>
>> https://realityforge.vrsource.org/trac/pyopensg/changeset/540/branches/trunk_update
>>  
> 
> Ah, this shows just how accurate my memory of that work is. I haven't 
> committed my work because it didn't compile. I don't normally check in 
> things that I know are not working. I can check it in since it's on a 
> branch and won't necessarily impact anyone.

Thanks! That gives me a starting point at least.

>> Yup, but it seemed as if the osgmodule_... file was handcrafted, and
>> I've mainly worked with that as a start.
> 
> It is generated, although it is generated by gen_bindings.py rather than 
> by Py++.

Ok. I'll have to dig a bit deeper. :)

> I would favor merging the remaining changes from the fcptr_stable_jun07 
> branch to the trunk. That may require some code reviews and/or 
> discussion among interested parties. That said, the revision that I am 
> about to commit removes the generated code for OSG::PerfMonitor, 
> OSG::DoubleTransform, and other pieces that are not present on the 
> trunk. It is regrettable, but it's the best that I have to offer at the 
> moment. The relevant pieces in gen_bindings.py are still there, but they 
> are commented out.

We don't need those ATM, so I can live with it for a while. Hopefully 
everything will migrate into trunk eventually.

Cheers.
/Marcus

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to