GUI reference structure

For each existing editor, a list of its GUI elements, depending on the context.

{{#tree:id=guiref|openlevels=5|root=Blender GUI|

APPLICATION
- WINDOW 1
  - SCREENS (Animation, Compositing, Default, Game Logic, Scripting, UV Editing, Video Editing)
    - AREAS
      - EDITORS/SPACES (3DView, Graph, NLA, ...)
        SELECTION (Camera, Transform widgets, Curves, Handles, ...)
        MODE (Object, Sculpt, Reconstruction, Edit, ...)
        VIEW
        menus
        
        buttons
        
        shortcuts
        
        mouse actions
        
        widgets (transformation widgets, curve handles, curves, ...)
        
        HEADER
        menus
        
        buttons
        
        TOOLSHELF
        Panel A
        screenshot
        
        menus
        type (Pulldown, ID menu, Search, ...)
        
        position in the panel
        
        name/label
        
        tooltip
        
        shortcut
        
        possible values
        
        buttons
        type (Toggle, Expanding toggle, Radio, Checkbox, Layers, ...)
        
        position in the panel
        
        name/label
        
        tooltip
        
        shortcut
        
        possible values (hard/soft min/max, ...)
        
        Panel B
        
        Panel C
        
        Panel ...
        
        PROPERTIES
        Panel A
        screenshot
        
        menus
        type (Pulldown, ID menu, Search, ...)
        
        position in the panel
        
        name/label
        
        tooltip
        
        shortcut
        
        possible values
        
        buttons
        type (Toggles, Expanding toggle, Radio, Checkbox, Layers, ...)
        
        position in the panel
        
        name/label
        
        tooltip
        
        shortcut
        
        possible values (hard/soft min/max, ...)
        
        Panel B
        
        Panel C
        
        Panel ...
- WINDOW 2
- ...

}}

GUI archetypes

For each GUI "archetype", we explain the usage not depending on the context.

Examples: how to collapse a panel, how to split a window, etc...

Application
Window
Editor
Toolbar
Properties toolbar
Header
View
Panel
Button
Input
Menu
Curves
- Handles
- ...
...
- ...
- ...

Mapping GUI item <-> operator

GUI items include buttons, menu entries, shortcuts, …

This will be done in the DB (mostly by auto-generating scripts).

Basically, an UI element can either fire an operator, or directly affect a property. If the later case is trivial, the former is a bit more trick, since a same operator can be used by different ui elements (e.g. different menu entries), with different parameters, and hence different effects!

So, for: