[Bf-committers] Collada importer/exporter kickout

[Sebastian]

That would be *lots* of work. OC is never meant as a simple standalone 
API but more a library to statically link against. There is no simple 
"C" like api but relies on the same memory allocators etc.

If you want to use Python don't stick with OpenCOLLADA ;)



On 09.01.2012 14:38, Peter Amstutz wrote:
> This is great news!  I've reported bugs in OpenCOLLADA myself that I
> would have fixed but could not due to the lack of code generation tools.
>
> Here's a thought, could these tools be used to generate a Blender Python
> API for OpenCOLLADA, then the data conversion for import/export (which
> is really the hard part) could be a Python add-on?
>
> On 1/7/2012 4:22 PM, Sebastian wrote:
>> Erwin already announced it: I've contributed the code generation
>> libraries under the MIT license and committed it to our Subversion
>> repository.
>>
>> You should see this as our commitment to the future of OpenCOLLADA.
>> OpenCOLLADA is and was a lot of work, it's far away from being perfect
>> or even error free but I would not suggest to develop yet another DAE
>> importer/exporter specifically for Blender or even drop support for it.
>> For the COLLADA community Blender is definitely one of the most
>> important stakeholders to stop supporting COLLADA would make things in
>> DCC exchange even worse.
>>
>> We are currently discussing further financing of OpenCOLLADA and will
>> spend more time the next months on bugfixing and conformance tests.
>>
>> Sebastian
>>
>>
>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers