[Bf-funboard] Re: Add Mesh - Continued...

[GSR]

Hi,
cbarton at metavr.com (2007-04-05 at 1411.10 +1000):
> So Options are
> 1) Keep the python scripts and C coded meshes in the same menu, and dont 
> allow too many Py Scripts in official release

Seems one of the best options.

> 2) Have Python scripts in a submenu. Add->Mesh->Scripts->

It could be named Custom, and could also allow importing from lib, but
adds an extra navigation step. Not too good for workflow.

> 3) Have a Custom Menu slot Add->Custom, all scripts can go there.

3 is clearly a thing to avoid, as you are disallowing scripts for
NURBS, Lamps, etc, or forcing a change in the future. Also this
ignores how the menu system works when in edit mode vs object mode
(what would happen? disable wrong type entries? remove them?).

> 4) Keep The meshes in the same menu (same as 1) but add a menu for user 
> defined meshes. so if people want crazy stuff they can add it there, - 
> The menu could be at location suggested in 2 or 3.

I do not understand this one. Do you mean official scripts are treated
different than user scripts? Or script vs library based data? Or some
shapes vs others based in arbitrary policy?

> Id like to get away from python being second classm nested away where 
> people wont use it,
> Adding a Torus acts no different then adding a sphere. separating based 
> on language makes no sense from a user perspective.

It helps knowing what things are as can be tweaked easier than the
other, as well as keeps the common things in one fixed place, with
custom versions in other. But the separator is enough for that.

> Id prefer to separate by functionality..
> 
> Primitives in one menu, arbitrary objects in another - teapot, monkey 
> and user defined.

What if scripts also enable adding non mesh things? What is a
primitive? I can have octahedron, that while being a primitive, would
end in other place due being user defined. Or maybe I am doing lots of
toy brick models, and my primitives are bricks.

My conclusion until a huge UI rewrite allows total customization (and
even the, probably the default should be like):

- script (or library) based data appear in the same menu as their
type, after a separator, sorted. Thus no penalization & covers all
types. Not very "huge collection" friendly, but this is a quick
solution, not a full redesign.

- ship small demo collection, at best.

GSR