[Bf-committers] proposal for better integration of addon functionality

[Gaia]

On 26.02.2013 15:44, CoDEmanX wrote:
> The addon's name could be added to the tooltip, but screencasts wouldn't
> benefit then...
Adding the Addon Name to the tooltips sounds good.
> for video tutorials it would make sense to indicate
> whether users need an addon or if need just the built-in functions
>
> append_after(bpy.ops.*) looks ok, but shouldn't it rather be
> append_after("mesh.foobar") ?
yes, good.
>
> And what to call the other function? prepend_before (I dislike)?

maybe: name add_after() and add_before()

> One problem is still not covered: what if someone uses an addon with
> older blender, addon works but the given op / op name of a built-in
> function doesn't exist in that version?

Isn't that a general problem ? We face this sort of issues a lot.
Blender developers told me they mostly just provide the "addon per release".
So in that case there should be no problems.

And when an addon shall span over multiple blender versions,
a lot of extra work needs to be done anyways (potentially) .

> Am 26.02.2013 14:04, schrieb Gaia:
>> Basically to help users to understand what comes from Blender
>> and what has been added from outside. Especially the first part
>> of my proposal about getting the ability to add menu entries
>> "inbetween" the standard entries might make it convenient to
>> know that "this" is from blender, and "that" is from an addon.
>>
>> Well it may be useful to distinguish between system addons
>> which are distributed along with blender (and can be considered
>> as part of blender), and the rest of the world.
>>
>> And ok, so lets make it a system option "mark addon elements" in
>> user preferences. then a screencaster can enable that to give visual
>> hints to the users. and users can decide to not care and disable the
>> visual mark...
>>
>> On 26.02.2013 13:36, Bart Crouch wrote:
>>> On Tue, Feb 26, 2013 at 10:41 AM, Gaia <gaia.clary at machinimatrix.org> wrote:
>>>
>>>> Currently you can not tell if a button or a panel has been added by an
>>>> addon.
>>>>
>>> Could you perhaps explain why it would be desired to make a visual
>>> distinction between add-ons and built-in functionality?
>>> >From a user-perspective I don't think it is very interesting to know
>>> whether a tool was written in Python or in C. And from a
>>> developers-perspective, I like the integration I can get when writing an
>>> add-on.
>>> _______________________________________________
>>> 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