[Bf-committers] Split Collada into a python frontend and a C++ backend

Thomas Dinges blender at dingto.org
Sun May 20 17:25:32 CEST 2012

I don't see a benefit here. Even if you can enable/disable Collada from 
The User Preferences, the code would still need to be compiled and 
linked into the Blender executable.
So why have it there anyway?

Am 20.05.2012 15:45, schrieb Gaia:
> On 20.05.2012 14:37, Brecht Van Lommel wrote:
>> I don't think it's a good idea to do this.
> Is there any good reason to have the Collada User interface implemented
> in C++ instead of separating it out to a Python ADDON ? The only reason
> i can think of is "its working, why change it ?" ...
> The benefit of having the user interface separated would be that
> the Collada io behaves more like all other exporters do... (can be
> enabled/disabled
> from user preferences for example)
Thomas Dinges
Blender Developer, Artist and Musician


More information about the Bf-committers mailing list