[Bf-committers] Collada importer/exporter kickout

[Campbell Barton]

It can be done:
- Compile collada as C/Python module
- Add C/python module init hooks (we have this for blender as a py module)
- Export all symbols from blender which collada io uses
- make an addon which loads this c/python colada addon and adds menu items.

Possible but IMHO impractical, and we would need to sink even more
time into setting up the symbols to export, scons/cmake buildsystem
edits... just a hassle. Also think this is drifting off topic.


I'm happy with any suggestion that means we can allow interested devs
to continue development to a point where its acceptable to be enabled
in release again.

So +1 for Ton's suggestion to move into a branch & have its own
tracker. This also means we can give devs SVN commit access who are
keen to work on collada support (where we might be less likely to
grant them access to work in trunk)

On Fri, Jan 6, 2012 at 10:49 PM, Sergey Sharybin <sergey.vfx at gmail.com> wrote:
> Nope, it wouldn't be possible.
>
> Collada is implemented in C, not in Py and so can't be used as
> import/export addons.
>
> On Fri, Jan 6, 2012 at 5:42 PM, Gaia Clary <gaia.clary at machinimatrix.org>wrote:
>
>> Would it be an option to separate the current Collada implementation
>> into an addon module, which is disabled by default, but can be enabled
>> from the addon panel ? (with a text flagging it as "Experimental" for
>> example)
>>
>> This would keep it out of view for everybody who does not need it.
>> But people who actually work with the current Collada exporter
>> could still enable it easily.
>>
>> -gaia-
>>
>>
>> Am 06.01.2012 11:58, schrieb Ton Roosendaal:
>> > Hi,
>> >
>> > I think it's a bad precedence to create a tracker for every feature we
>> notice is badly supporting or failing. Just moving reports to another
>> tracker is not solving anything of course.
>> >
>> > I would rather tackle it more political&  practical:
>> >
>> > 1) Official announcement that Blender drops Collada support
>> > 2) Move Collada support into a branch, out of trunk
>> > 3) Create a tracker "orphanage" or "branches" or so, where we put all
>> reports that are not in support (anymore).
>> >
>> > BTW:
>> >
>> > I've personally had it with Collada and its supporters. Next time we add
>> this back in Blender it should be based on well defined and tested use
>> cases, on a level we (or the branch team) can support it. In my opinion
>> that's proven to be impossible, for reasons how Collada works, designed and
>> has been organized.
>> >
>> > Three months ago already I wrote this open letter:
>> > http://code.blender.org/index.php/2011/10/collada-momentum/
>> >
>> > -Ton-
>> >
>> > ------------------------------------------------------------------------
>> > Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
>> > Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands
>> >
>> > On 4 Jan, 2012, at 20:57, Sergey Sharybin wrote:
>> >
>> >> Hi,
>> >>
>> >> As everybody noticed current collada importer/exporter is very buggy
>> which
>> >> seems to make this format almost useless in Blender. And what's much
>> worse
>> >> -- we don't actually have developer who maintains this area.
>> >>
>> >> We discussed this already with Campbell and found that OpenCollada
>> itself
>> >> isn't actually maintaning -- there are only few commits in several
>> months.
>> >> Ofcourse it doesn't mean this library is useless and all bug from our
>> >> tracker is related on that issues, but still.. Maybe the time have come
>> to
>> >> re-think this importer/exporter (investigate if it's possible to fix
>> issues
>> >> in clear way, check if design is good enough -- not sure, haven't
>> touched
>> >> this code deep myself)?
>> >>
>> >> Here's our proposal:
>> >> - Move all collada-related issues into it's own tracker. Like it was
>> done
>> >> with BGE, it might help finding volunteer to fix them. Also, people will
>> >> see that it's not actually core stuff and that it's community-supported.
>> >> - Disable collada in release builds. It's not useable and only seems to
>> be
>> >> making artists disappointed.
>> >>
>> >> More optimistic targets would be find volunteer to pick up this stuff
>> who
>> >> will make it usable (maybe rewritting this stuff from scratch..)
>> >>
>> >> --
>> >> With best regards, Sergey Sharybin
>> >> _______________________________________________
>> >> 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
>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
>
>
>
> --
> With best regards, Sergey Sharybin
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers



-- 
- Campbell