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.cl...@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@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
