I agree that N panel is too miscellaneous, but that kind of drastic change is hard to happen IMO… Since Blender is evolving gradually(not dramatically) after 2.80 shift.
But this is what needs to happen, otherwise there will be no end to this clutter madness.
It has several dealbreaking issues:
- The popover system works in a way that you always need to have mouse over it when interacting with it. As soon as you click away into viewport, it disappears. Many addons, such as tree generators for example, are currently in the side panel. If you were to have your design, then every time you would want to as little as turn or move the viewport around, you’d inevitably close all the tree generator settings of the tree you are working on and would have to re-open the popover by clicking the label. That would be beyond infuriating.
- The bottom popovers would constantly obscure/block the contents of viewport, which would make it impossible to tweak the settings and observe the effects of the setting changes. Especially for the popover buttons near the center.
- Scrolling large UI sets in popover vertically would be way clumsier than scrolling a side panel.
This is a big no go.
2 Likes
I answered in the other thread, now i do here too.
As Rawalanche already pointed out, the issue is that apparently these addon panels would behave like popovers, so you don’t always have “at hand” the parameters but you should move the mouse all the way to the bottom and click on the required label each time you want th change or simply read a value.
For the last couple of months, I’m slowly shifting to Blender, coming from Cinema 4D.
The changes in 2.8 really made a big difference, which makes switching easier. Also, some of the future plans listed on the module roadmaps look very promising - some things are confusing though at the current moment.
‘Tool settings are on too many places’ and the N-Panel in general are probably the biggest UI Layout issues that made Blender confusing for me to use in the beginning. Rawalanche’s initial picture nails it:
the placement of information seems very random and scattered all around the screen, also the amount of information in different places isn’t consistent, which adds confusion.
I’d very much appreciate a unification-pass of the layout here. Rawalanches proposal seems to do this very well and smartly 
I agree, that changing the layout appears drastic, probably leads to friction, and might not be as shiny as a new Eevee feature, but a thought-through high-level UI will be a big win for usability and solidity in the long run and therefore more than worth it.
1 Like
My whole point is that Tools do not show the exact same settings though.
Criticism towards settings duplication applying specifically to operators might be fair enough, as is definitely settings duplication for tools.
But Tools aren’t exactly instancing the same settings as the operators.
edit: ah yeah, I was specifically replying to @1D_Inc
I don’t like to insist on my own opinion too much since there can be other point of view and better solutions… but this time, let me explain about this proposal a little more.
About clicking too much while switching between UI:
When it comes to switching between addons, clicking between vertical tabs can be harder than clicking and hovering over bottom menu buttons. It’s not hard to open popovers. We are already used to popovers of viewport settings, overlays, transform orientations, pivot point, proportional editing.
About clicking too much while simply reading or changing a value:
- If the addon or Blender feature is responsible for changing object’s custom properties, than it should register itself in the properties editor, not the sidebar. Object element properties(inside edit mode) such as edge crease weight and bevel weight should also be inside properties editor with a brand new element tab, just like current polygon material slot. Sidebar(previously N panel) was not intended to be used in that way when it was introduced in 2.50. It was originally for viewport settings, annotation(previously grease pencil) settings, etc. Sidebar just became a kitchen sink for a decade while addon developers continuously threw their addons inside it. I believe Blender should allow addon developers to register their custom tabs inside properties editor. Properties editor is the right place for properties of the objects or the scene.
- If the addon is responsible for providing operators to be used inside the 3D viewport, it should register itself in the header or footer menus.
- If the operator needs to be tweaked visually, those sliders should go inside adjust-last-operation panel.
In short:
Not only Blender has to improve its sidebar UI and API, but addon developers should too.
- Operator buttons should go inside header or footer menus
- Operator tweak sliders should go inside adjust-last-operation(redo-last previously) panel.
- Object or object element properties should go inside the properties editor.
- Even then if addon should use its own space, it can make its own popover at the footer.
To be fair the properties and toggles in popovers are things you likely don’t need to touch too often but when you do you want to have relatively quick access to them.
While depending on the add-on you might want to access it constantly to the point that even though popovers are a relatively quick access it will still become bothersome.
Unless the popover can be pinned to stay open for a while, which we can’t and probably wouldn’t want to anyways since it would cover a significant portion of the viewport.
2 Likes
All this list of “this should go here and this should go there” is just one point of view. As @megalomaniak says, a UI can also take into account how useful is to have something more or less prominent based on how often you may want to access it. Also many people might want to adopt full screen (I do sometimes) for certain tasks within a workflow, and that property editor (about sinks…) kills this possibility.
good luck for when you have the many addons enabled that are in the screenshots that show an overcrowded sidebar… 
I see you’re talking about accesability and preserving familiar workflows to existing users. That’s good because Blender is made to get the 3D art job fast and easy. I too think that’s important, but what I’m trying to talk about is logic, simplicity and consistency that makes the Blender reliable in the long run. Maya and 3ds Max is a good example of not doing this so well.