Okay I guess you did misunderstand my misuse of the word crappy. What I meant was more like "less likely to work with existing OpenCollada importers". Those which are already used in other apps. Clearly an OpenCollada exporter is more likely to work with an OpenCollada importer across apps. This was all I meant really. And implicitly this was also what Sebastian was saying in regards to the dangers of introducing yet another one. It's really a reflection of the Collada format being ridiculously broad. I am not calling anyone's code literally crap so sorry I misused this work.
On Sat, Jan 7, 2012 at 3:24 PM, Juan Linietsky <redu...@gmail.com> wrote: > > > > > > And Juan no offense intended here I am just making a comparison. I am not > > saying your code is literally crappy! > > > > > The word crappy is completely subjective. In this case, what matters is: > > 1) Whether something works or not. It may have bugs and need a little more > work in the export options area, but it definitely does work (or is very > close). > 2) How easy it is to maintain. I think we can agree that a ~1k loc python > codebase is much easier to maintain than a huge library and wrapper code. > > > Cheers > > Juan > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers