Unify quick open windows (Editor UX)

[LukasDavidSchwarz]

Hey, very new Godot user here, so maybe take it with a grain of salt? Or maybe it's even beneficial because I have a fresh set of eyes? Idk.

Describe the project you are working on

Migrating a WIP 3D rougelite from Unity to Godot

Describe the problem or limitation you are having in your project

After opening one of the 'Quick Open' windows, I want to switch to a different one, because I opened the wrong one. I can't use the keybind of the correct one because the search textbox is in focus and the keypresses are consumed by it.

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

Option A)

Move the 'Quick Open...', 'Quick Open Scene...' and 'Quick Open Script...' Windows to one window with a tab for each of them. Also add keybinds (maybe 'Alt + Right Arrow' / 'Alt + Left Arrow' or 'Tab' / 'Shift + Tab') to move between the tabs.

Example of how this is done in the Rider C# IDE:

Pros:

• Makes it easier to discover all 'Quick Open' modes, after just one of them is discovered by the user
• Code of the different 'Quick Open' modes does not have to be entangled, just like before

Cons:

• Doesn't scale well in case 7 more 'Quick Open' modes are added in the future, because it gets a bit messy with that many tabs

Option B)

Use a unified 'Quick Open' mode, that uses special syntax in the search text box to select what to search for.

Example of how this is done in Unity Quick Search:

Pros:

• Scales well in case like 7 more 'Quick Open' modes are added in the future.

Cons:

• Code of the different 'Quick Open' modes might get entangled / code complexity might increase
• It's not so easy to discover the other 'Quick Open' modes, since it's hidden behind special syntax.
  • But it might be possible to add Buttons to toggle these features, which would then append/prepend the necessary kewords to the search string

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

I don't know

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

I don't know

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

I don't know

[LukasDavidSchwarz]

Somewhat related to #7717