godotengine / godot-proposals

Godot Improvement Proposals (GIPs)
MIT License
1.17k stars 98 forks source link

Simplify Inspector dock #9836

Open derket25 opened 6 months ago

derket25 commented 6 months ago

Describe the project you are working on

Multiple projects.

Describe the problem or limitation you are having in your project

The Inspector dock is too cluttered. It contains buttons that are rarely used but take up three rows of usable space.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

The buttons for managing resources and opening documentation are suggested to be removed to a drop-down menu. Move the arrow buttons in front of the node name, as on the FileSystem dock. Remove History button. Instead, open history by holding down the Back button, as implemented in Google Chrome.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

Mock-up concept

If this enhancement will not be used often, can it be worked around with a few lines of script?

It's core.

Is there a reason why this should be core and not an add-on in the asset library?

It's core.

AThousandShips commented 6 months ago

Hiding a lot of functionality behind menus makes editing slower and hurts discoverability of features, making it harder for new and experienced users alike

KoBeWi commented 6 months ago

How exactly removing a single row, which is less than 5% of the whole inspector size, helps to remove clutter?

timothyqiu commented 6 months ago

4273 did something similar when creating the mockup.

It moved the sub-resource dropdown to a button beside the search box. The documentation button is moved to the top row.

action-area

9205 suggests hiding the search box row by default instead.

inspector

passivestar commented 6 months ago

I have some questions as a new user. I haven't seen this being done this way in other software and I haven't seen that functionality being mentioned in tutorials that I watched and read, so:

  1. When do you want to create a resource in memory through the editor and not save it?
  2. If you create a resource and not save it, how do you reference it?
  3. Is this functionality needed often enough to have the first row of inspector dedicated to it (as opposed to being in the dropdown menu like this proposal suggests)?
npinsker commented 5 months ago

I don't personally use these buttons (I do all of these through the FileSystem window), but can understand why they're there.

IMO the top of the Inspector is among the most valuable real estate in the entire engine, and it's worth carefully considering how that space is used. This isn't meant as support for this proposal specifically, but in my view, saving a single line is significant.