[Bf-committers] Add-Ons & Primitive Objects.
ideasman42 at gmail.com
Sat Jun 5 20:02:05 CEST 2010
That'd work, the 'Addons' tab in the user preferences would act like a
frontend to the addons SVN repo,
probably not all that hard to do since we can assume a full python install now.
though at the moment I don't see it as that important since the addons
themselves are not big.
This has the advantage that addons can be updated after a blender release.
The problem it introduces is we would need some way to stop version
mis-matches between blender releases and the addons they download.
So if others agree this is acceptable, its just a matter of someone
submitting a patch to space_userpref.py :D
On Sat, Jun 5, 2010 at 7:19 PM, Stephen Christie <undersampled at live.com> wrote:
> Yes. That doesn't necessarily mean not listing them. Take a look at Firefox 3.x's add-on system, where you can search for, download, and install new add-ons in the "Get Add-ons" tab, and see, disable, uninstall, and change the options of your installed add-ons in their respective tabs (Extensions, Themes, and Plugins). Also note that vanilla Firefox does not come with any extensions installed.
>> Date: Sat, 5 Jun 2010 18:57:06 +0200
>> From: ideasman42 at gmail.com
>> To: bf-committers at blender.org
>> Subject: Re: [Bf-committers] Add-Ons & Primitive Objects.
>> On Sat, Jun 5, 2010 at 6:31 PM, Stephen Christie <undersampled at live.com> wrote:
>> > Actually, when I said "does it make since to have an official list of features that are
>> > included during install, that the user has to find and enable himself?", I was not saying that users should choose which plugins to include when they install blender. I was pointing out that the addons are always installed (using up a tiny
>> > ammount of space), and users have to discover that they exist by going
>> > to the options menu. It makes little since to me to have features (that one would normally presume the user would find online and choose to install on their own) hidden and disabled but installed by default. We should determine the best default feature set and leave it up to the user to expand their feature set.
>> Agree a good selection of tools should be enabled by default, at the
>> moment we dont enable any addons by default but I expect we will do so
>> before a stable release.
>> Some scripts, povray integration for example should be made into an
>> addon IMHO (currently its always loaded).
>> Are you saying that we should not include addons which are not enabled
>> by default?
>> Bf-committers mailing list
>> Bf-committers at blender.org
> The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail.
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers