[Bf-committers] Rigify addon causes error, error, error,....

Campbell Barton ideasman42 at gmail.com
Tue Feb 19 06:12:36 CET 2013


On Mon, Feb 18, 2013 at 7:38 PM, Chad Fraleigh <chadf at triularity.org> wrote:
> This question probably has already be discussed, but are there any
> plans to implement an addon deployment like mozilla applications
> (firefox/thunderbird/seamonkey 2.x) uses where the client (blender)
> can just browse a central http://addons.blender.org/ site (or
> something) and with a click or two, install/upgrade what they want.
> Then there would be few (or none) bundled by default. And if they are
> bundled, they would act as defaults (i.e. only if that plugin hasn't
> already been installed for the user, regardless of versions). Then
> newer addons could be published without needing to align with the
> blender release cycle.
>
> Making sure already installed ones are compatible with potential
> internal blender changes will still be an issue. But if addon
> deployers (assuming more than just core blender developers could
> maintain these addons) would keep what versions of blender that each
> of their addons (by version) are compatible with. From that a single
> metafile could be generate automatically/daily/whatever for blender to
> download/check (with user consent) automatically when it detects a
> different blender version installed.
>
> Maybe  .bap  (Blender Addon Package) files (which are just zipfiles)? =)
>
> And I assume python can be used [client side] to do all this, as-is,
> and that resorting to trying a [much?] harder C implementation could
> be avoided.
>
>
> -Chad

Gaia Clary has a working online addon browser, I'm not sure of the
status right now though of if she intends to further develop it.

As I see it. the issue with this is we end up having to write our own
package manager which is simple to begin with but gets complicated
fast
(consider existing extension repositories of mature applications -
firefox and eclipse for example).

So we need someone to write & maintain it, then buy-in from existing
extension developers.
Since we already have a hard time maintaining existing addons in
subversion, I'm not sure this would be a success at the moment.

> On Sun, Feb 17, 2013 at 11:28 PM, Knapp <magick.crow at gmail.com> wrote:
>>> Is there some way that we could rework addon loading such that local
>>> versions of addons (e.g. in .config/blender/x.x/scripts/addons)
>>> override and take precedence over official repo versions?  That way it
>>> is easy to have local versions of addons.  With a lot of addons that
>>> might seem pointless, but with Rigify it's actually an important
>>> use-case.
>>>
>>> --Nathan
>>
>> Why not make the official version a dumby/empty that then seeks to
>> load a version. Then just load up the one you want.
>>
>>
>> --
>> Douglas E Knapp
>>
>> Creative Commons Film Group, Helping people make open source movies
>> with open source software!
>> http://douglas.bespin.org/CommonsFilmGroup/phpBB3/index.php
>>
>> Massage in Gelsenkirchen-Buer:
>> http://douglas.bespin.org/tcm/ztab1.htm
>> Please link to me and trade links with me!
>>
>> Open Source Sci-Fi mmoRPG Game project.
>> http://sf-journey-creations.wikispot.org/Front_Page
>> http://code.google.com/p/perspectiveproject/
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers



-- 
- Campbell


More information about the Bf-committers mailing list