3D View Toolbar: Reorganize Object Mode Tools and Options #37569

Closed
opened 2013-11-21 16:29:54 +01:00 by Jonathan Williamson · 28 comments

The 3D View toolbar needs reorganized for Object Mode. This organization should be based on the new vertical toolbar tabs.

The 3D View toolbar needs reorganized for Object Mode. This organization should be based on the new vertical toolbar tabs.
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Jonathan Williamson self-assigned this 2013-11-21 16:29:54 +01:00
Author
Member

Added subscribers: @JonathanWilliamson, @brecht, @PawelLyczkowski-1, @ack-err, @CodeManX, @billrey, @Januz

Added subscribers: @JonathanWilliamson, @brecht, @PawelLyczkowski-1, @ack-err, @CodeManX, @billrey, @Januz

Added subscriber: @koilz

Added subscriber: @koilz

edit.

edit.

Added subscriber: @AditiaA.Pratama

Added subscriber: @AditiaA.Pratama

This is how i see the object tools.
The second set is reordered into balanced categories.
http://www.pasteall.org/pic/show.php?id=63023

Im not sure how to reorganize them, but thats how i would divide the object tools.

This is how i see the object tools. The second set is reordered into balanced categories. http://www.pasteall.org/pic/show.php?id=63023 Im not sure how to reorganize them, but thats how i would divide the object tools.
Author
Member

Thanks for the suggestion @koilz. Although it won't be practical to have different layouts for new/advanced users likely. This may not be the case, if we get more of Ack-err's GSOC work in, but so far as the initial organization goes it'll be one layout by default for everyone.

Thanks for the suggestion @koilz. Although it won't be practical to have different layouts for new/advanced users likely. This may not be the case, if we get more of Ack-err's GSOC work in, but so far as the initial organization goes it'll be one layout by default for everyone.

Sorry.
Im sure i keep posting on the wrong topic, or forgetting to read one.

Sorry. Im sure i keep posting on the wrong topic, or forgetting to read one.
Author
Member

@koilz, nope this is right place for comments regarding Object Mode toolbar organization. This task is mostly waiting on #37601 though.

@koilz, nope this is right place for comments regarding Object Mode toolbar organization. This task is mostly waiting on #37601 though.

Here's a sketch:

3D_View_Object_Mode_Tools.png

With the same rationale as:

http://developer.blender.org/T37568

Here's a sketch: ![3D_View_Object_Mode_Tools.png](https://archive.blender.org/developer/F44156/3D_View_Object_Mode_Tools.png) With the same rationale as: http://developer.blender.org/T37568

Heres some tools for animation.
For the Mesh and Pose objects.

.anim.PNG

I think having the menu to switch actions can be useful.
Also keying sets are easier to access here.
And Auto Keyframe is pritty useful.
And some play buttons for fun.

The other tools already exist.

From billreys post, I think Bake Action will also be usefull.

Heres some tools for animation. For the Mesh and Pose objects. .![anim.PNG](https://archive.blender.org/developer/F44281/anim.PNG) I think having the menu to switch actions can be useful. Also keying sets are easier to access here. And Auto Keyframe is pritty useful. And some play buttons for fun. The other tools already exist. From billreys post, I think Bake Action will also be usefull.

If we have a lot of space now, would moving the whole Object and Mesh menus to the toolbar be possible?

If it would, this would solve the duplication problem, where we have commands from the Object and Mesh menu in the toolbar, but only some, and chosen based on a vague criteria.

This would also allow some ordering of the commands, making things like Make Dupli-Face less visually important, while making things like Duplicate more visually important.

If we have a lot of space now, would moving the whole Object and Mesh menus to the toolbar be possible? If it would, this would solve the duplication problem, where we have commands from the Object and Mesh menu in the toolbar, but only some, and chosen based on a vague criteria. This would also allow some ordering of the commands, making things like Make Dupli-Face less visually important, while making things like Duplicate more visually important.

@PawelLyczkowski-1

I think if items are going to be removed from the menu, the object tools would have to be redesigned first.
Then the menu could be updated based on the present tools.

I dont know if devs are willing todo this, but i think its a good proposal.

@PawelLyczkowski-1 I think if items are going to be removed from the menu, the object tools would have to be redesigned first. Then the menu could be updated based on the present tools. I dont know if devs are willing todo this, but i think its a good proposal.

@koilz

I think if items are going to be removed from the menu

I was thinking of moving the whole Object/Mesh menu to the toolbar

the object tools would have to be redesigned first

Elaborate please.

@koilz >I think if items are going to be removed from the menu I was thinking of moving the whole Object/Mesh menu to the toolbar >the object tools would have to be redesigned first Elaborate please.

@PawelLyczkowski-1

I thought you would only want to move some of the tools, then remove tools from the menu, so there are no duplicates.
In that case the 3D view tools would have to be redesigned first, before removing items from the menu.

If your proposal is to move all the tools from the menu, to the 3D view, and not remove items from the menu.
The menu doesnt have to be redesigned, so, it doesnt depend on the 3D view tools being redesigned first.

The tab categories are still undecided, so if you did want to move all the tools, this could be a good way to design the tab categories.

@PawelLyczkowski-1 I thought you would only want to move some of the tools, then remove tools from the menu, so there are no duplicates. In that case the 3D view tools would have to be redesigned first, before removing items from the menu. If your proposal is to move all the tools from the menu, to the 3D view, and not remove items from the menu. The menu doesnt have to be redesigned, so, it doesnt depend on the 3D view tools being redesigned first. The tab categories are still undecided, so if you did want to move all the tools, this could be a good way to design the tab categories.

Added subscriber: @xrg

Added subscriber: @xrg
Author
Member

Anyone that wishes to test the toolbar tabs for Object Mode may get the current patch here: https://developer.blender.org/D128#comment-6

Anyone that wishes to test the toolbar tabs for Object Mode may get the current patch here: https://developer.blender.org/D128#comment-6

@JonathanWilliamson, looking good. The add mesh panel looks a little too long though (specially when addons start adding their own panels there). What about grouping buttons in dropdowns instead? For instance, primitives and special would be two dropdowns, same with Bezier and Nurbs.

Here's a screen for those that can't/don't want to build:

objectTabs.jpg

@JonathanWilliamson, looking good. The add mesh panel looks a little too long though (specially when addons start adding their own panels there). What about grouping buttons in dropdowns instead? For instance, primitives and special would be two dropdowns, same with Bezier and Nurbs. Here's a screen for those that can't/don't want to build: ![objectTabs.jpg](https://archive.blender.org/developer/F61023/objectTabs.jpg)
Author
Member

@Januz, in general I'm not a fan of dropdowns within the toolbar. I find it rather defeats the purpose of the toolbar, that being having tools quickly at hand for easy clicking, rather than being behind menus. A dropdown is little different than a normal menu.

That being said, I totally agree that it's too long. I've also considered doing two columns, but I know @billrey has been urging against that in order to maintain easy eye scanning.

I will do some more experimenting with it, though.

@Januz, in general I'm not a fan of dropdowns within the toolbar. I find it rather defeats the purpose of the toolbar, that being having tools quickly at hand for easy clicking, rather than being behind menus. A dropdown is little different than a normal menu. That being said, I totally agree that it's too long. I've also considered doing two columns, but I know @billrey has been urging against that in order to maintain easy eye scanning. I will do some more experimenting with it, though.
Author
Member

Here's a comparison for the Mesh primitives, showing a single column and double column:
Screenshot_2014-01-03_10.10.44.png Screenshot_2014-01-03_10.10.58.png

The double column looks good and saves a lot of vertical space, but it requires a much wider minimum width to maintain complete readability. As you can see here:
Screenshot_2014-01-03_10.12.47.png

Here's a comparison for the Mesh primitives, showing a single column and double column: ![Screenshot_2014-01-03_10.10.44.png](https://archive.blender.org/developer/F61087/Screenshot_2014-01-03_10.10.44.png) ![Screenshot_2014-01-03_10.10.58.png](https://archive.blender.org/developer/F61088/Screenshot_2014-01-03_10.10.58.png) The double column looks good and saves a lot of vertical space, but it requires a much wider minimum width to maintain complete readability. As you can see here: ![Screenshot_2014-01-03_10.12.47.png](https://archive.blender.org/developer/F61098/Screenshot_2014-01-03_10.12.47.png)

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

Ok, I just checked the latest patch from here: https://developer.blender.org/D128

  1. I am against exposing 6 panels just for primitive creation in the Toolbar, we have the SHIFT+A menu and the menu in the 3D View header. I don't think we should have the same functionality in 3 places. We can add one panel for the most used primitives, but not 6 dedicated panels.

  2. Rigid Body Tools panel is collapsed, even though it comes in its own tab. Expand per default?

  3. Grease Pencil buttons have weird alignment.(Draw/Line and Poly/Erase lines)

Ok, I just checked the latest patch from here: https://developer.blender.org/D128 1) I am against exposing 6 panels just for primitive creation in the Toolbar, we have the SHIFT+A menu and the menu in the 3D View header. I don't think we should have the same functionality in 3 places. We can add one panel for the most used primitives, but not 6 dedicated panels. 2) Rigid Body Tools panel is collapsed, even though it comes in its own tab. Expand per default? 3) Grease Pencil buttons have weird alignment.(Draw/Line and Poly/Erase lines)
Member

Added subscriber: @plasmasolutions

Added subscriber: @plasmasolutions
Author
Member

Thanks @ThomasDinges! Here is an updated patch. #37569.diff

Note: Rigid Body panel is not set to closed. Could it be local settings that are causing that to be shown closed?

Thanks @ThomasDinges! Here is an updated patch. [#37569.diff](https://archive.blender.org/developer/F61175/T37569.diff) Note: Rigid Body panel is not set to closed. Could it be local settings that are causing that to be shown closed?

Looks good to me then.

Looks good to me then.

Added subscriber: @DataDay

Added subscriber: @DataDay

If you plan on having a create or add tab, there is no reason not to have basic primitives in there, even if it seems redundant to the experienced user.
Maya has this as well, and it works fine. Primitives can be added via hotbox, icons in the polygon tab, and from the create menu on top. The perk of having buttons/icons or really less keyboard intensive means to add even basic polys is that the user can have a combination of full screen mode (hide other UI elements) and or the use of a wacom tablet without needing to move down to the keyboard.

If you plan on having a create or add tab, there is no reason not to have basic primitives in there, even if it seems redundant to the experienced user. Maya has this as well, and it works fine. Primitives can be added via hotbox, icons in the polygon tab, and from the create menu on top. The perk of having buttons/icons or really less keyboard intensive means to add even basic polys is that the user can have a combination of full screen mode (hide other UI elements) and or the use of a wacom tablet without needing to move down to the keyboard.
Author
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
10 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#37569
No description provided.