[Bf-committers] Collada importer/exporter kickout

Sebastian sebastian at opencollada.org
Mon Jan 9 12:09:39 CET 2012


Hi,

that would be the third try to have COLLADA tools available for Blender. 
Beside the technical implementation details (Python, OC Library, Python 
again) I suspect the major problem is and was the missing maintainer for 
these converters.

Having a scripted exporter is easy to write, I agree. But OpenCOLLADA is 
only 5% about exporting and 95% about importing files into DCC tools. I 
do not expect a <1k LOC Python script to successful import any DAE files...

Perhaps a solution that is based upon Erwin's idea of using blend and 
having a standalone converter from DAE to blend and vice versa could be 
a valid possibility to separate the DAE capabilities from the trunk and 
not to completely abandon DAE support at all.

Sebastian



On 09.01.2012 11:43, Ton Roosendaal wrote:
> Hi Juan,
>
> We work here with a lot of volunteers, people who can only contribute a little bit of time.
>
> What Campbell  mostly likes to see is you remaining to be involved, just keep using the code and when there's time check on changes or fixes by others. No obligations, no further commitments needed.
>
> It does add the obligation for us (Blender team) to find a new 'owner' for your script who does take responsibility to keep it work. And document it :)
>
> So; Collada users here, please check it the code and report back?
>
> -Ton-
>
> ------------------------------------------------------------------------
> Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
> Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands
>
> On 9 Jan, 2012, at 6:37, Juan Linietsky wrote:
>
>> Campbell, I don't mind accepting patches or helping out people to work on
>> the plugin , but what I can't do is to promise spending much time adding
>> more features myself or upon request. I don't really know much about the
>> development process of Blender, so if you feel this will work then I'll
>> gladly do that. I am also fine doing bug fixes if there are issues reported
>> to me or even adding small features upon request. I just can't work a large
>> amount of time myself on this.
>>
>> Cheers
>>
>> Juan
>>
>>
>> On Mon, Jan 9, 2012 at 1:39 AM, Campbell Barton<ideasman42 at gmail.com>wrote:
>>
>>> On Mon, Jan 9, 2012 at 2:16 PM, Juan Linietsky<reduzio at gmail.com>  wrote:
>>>
>>> @Juan, even if your not especially interested to maintain for such a
>>> wide variety of uses.
>>> (since it seems your happy with a fixed set of features which is
>>> understandable for a format with very broad spec).
>>>
>>> perhaps you could committed this as an addon so others can use it
>>> without having to manually download and install.
>>>
>>> As the author you can accept/reject changes so it wont become
>>> something too different from your original intentions.
>>>
>>> Reason I suggest this is that I'd rather not have the script committed
>>> and then you continue to maintain your own version - where both
>>> scripts get out of sync, fixes not applied to both - its worth
>>> avoiding a fork if we can.
>>>
>>> The addon can start in `contrib` repository which is available when
>>> `Testing` scripts are enabled.
>>>
>>> What do you think?
>>>
>>> --
>>> - Campbell
>>> _______________________________________________
>>> 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


More information about the Bf-committers mailing list