Reorganize 3d View Menus: View, Add and Object Menu
This is on the behalf of @Brendon Murphy (meta-androcto) see T46853
Differential D1741
Reorganize 3d View Menus: View, Add and Object Menu Authored by Aaron Carlisle (Blendify) on Jan 19 2016, 6:05 PM.
Details
Reorganize 3d View Menus: View, Add and Object Menu This is on the behalf of @Brendon Murphy (meta-androcto) see T46853
Diff Detail
Event TimelineComment Actions hi, this patch will need to be rewritten soon to update to 2.8, I will get this underway in the week following 2.78 release Comment Actions updated file here: changes from here are not included: https://developer.blender.org/D2259 @Aaron Carlisle (Blendify) please test & apply your patch. changes in this update are: code clean up: whitespace remove, layout separator moved consistently to the end of it's ui "block" better representation of undo/redo menu original patch rebuild with revision: 2cd6a89 see T46853 Comment Actions Can we please not reuse icons for different purposes? Like using the ORTHO icon for duplicate or ROTATECENTER for joining. I don't know if we have a strict UI convention documented about that somewhere, but it's definitely a rule we followed in 2.5 design. Personally I don't think it's helpful to have such icons in menus even, there's only so much information you can see at a glance, and adding more is not necessarily good. To me it looks more like decoration rather than useful information, particularly if we reuse icons. For what it's worth, most operating systems and applications don't put icons in such menus either, or only sparingly. Comment Actions @Aaron Carlisle (Blendify) Thanks for help updating, much appreciated. Comment Actions Let's define a policy then.
Well that is a possible solution to the menu decoration issue. Different strokes for different folks :) For the general policy - an icon should have a function in menus apart from the visual identification of menu entries. It should also represent Types of entries. A proposal for the policy would be something like:
That's an issue that seems not easily solvable. There is a lot of operators, and explaining it's functionality through icons is not an easy task. What's the criteria for picking them? Only those which have buttons/ elements that use icons elsewhere in the UI? That seems reasonable as makes things consistent. What about the regularly used functions? This needs a bit of thought. One way of alleviate the visually busy submenu entries icons is to have them just in predefined color sets / monochrome. So they're distinguished from possible operator ones. And being original. Sorry for the long post. |