[Bf-committers] Collada importer/exporter kickout

[skoti]

Assimp only importer (exporter in blender is the most important), and 
even in assimp Collada importer is weak. Blender use external library 
for Collada (OpenCollada libs).

Collada format is an important and IMO it should not be removed. Collada 
is used in many game engine, engine Web3D (WebGL or flash engine), and 
everywhere, where we exchange information.

It seems to me that it is better to leave the exporter in the trunk than 
reduce the functionality of the program (for many it becomes useless - 
now an exporter / importer, blender works well with programs based on 
OpenCollada / FCollada / Collada DOM - works better than autodesk 
exporter (creates files "Collada-like ")).
> I'm just curious: why can't an external library be used?
>
> I know about Assimp, i double checked and it seams that it supports collada
> import/export(at least they say so on their site, and i think it is full
> support since it isn't marked with an * [2][3]). It also has a C or C++ API.
> The licence is (a kind of [4])BSD, is this a problem?
> This would offload main devs from format support. In addition blender would
> be able to import/export all the format the external library already
> handles. And in case specific files must be supported, this can be archived
> with python or a specific imp/exporter.
>
> Is there a reason why blender shouldn't rely on an existing library, or
> it's a licence/features problem with the existing ones?
>
>
> [1] http://assimp.sourceforge.net/index.html
> [2] http://assimp.sourceforge.net/main_features_formats.html
> [3] http://assimp.sourceforge.net/main_features_export.html
> [4] http://assimp.sourceforge.net/main_license.html
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>