In 2.79b the Editor Type dropdown was a vertical list of literally all the editors available in Blender.
In Blender 2.8, the first step of splitting this list into columns/categories makes the layout a bit clearer. But we are still showing only the editors themselves, hiding a lot of important features under sub-editors.
Some examples of hidden functionality is how the Compositor and Shading Nodes editors are combined into the Node Editor entry even though their purpose is completely different. And with Animation Nodes or Modifier Nodes in the future this is only going to get worst.
This proposal is to expand sub-editors into their own entry to gain exposure and discoverability. They would work as sort of shortcuts to their own section.
List of changes:
- 3D View -> simply renamed to 3D Viewport
- Nodes Editor ->
- New: Shader Editor (for Material/World/Line)
- Texture Editor is not included as it is to be removed
- UV/Image Editor ->
- New: UV Editor
- New: 2D Paint
- New: Mask Editor - Read note below.
- Image Editor -> renamed to Image Viewer, put in the Data category
- Movie Clip Editor -> renamed to Motion Tracking
- New: Drivers (sub-editor of Graph Editor)
- Timeline: Now a sub-mode of Dopesheet Editor
- NLA -> simply renamed to Nonlinear Animation
- Info: see note below
- New: Image Viewer
- New: Assets Browser (in the future)
- User Preferences: remove it
- Mask Editor: The Mask editing functionality is duplicated in both the Image editor and the Movie Clip. The only difference is that they work with either Images (or render result) or Videos. These could be merged into one single editor, to be discussed with @Sergey Sharybin (sergey).
- Info Editor: I propose to remove it from the list. The top-bar will take over the menu entries, the status bar will take over the stats. The print of the operators runned is better fit as a sub-editor of the Python Console.
- Remove menu header. Not only makes it cleaner but also makes the "Editor" in entries not redundant. Removing 'Editor' from some entries introduce confusion (e.g. "Shader" could be confused with Properties or the Asset, "Graph", "Text", etc).