That is instead of 9 separate 'Go to ...' actions in Navigate menu have just one 'Go to' action with submenu containing
all the actions. Disadvantage would be the impact on quick accessibility of actions - one more menu to go through. But
as it is now (look at the screenshot) it is little bit bloated.
Created attachment 69369 [details]
Yes, the Full IDE is even worse. Instead of pushing actions into a submenu (which is certainly a solution), I would suggest to try merging some of the items.
For example Go to File, Type, Symbol and Spring Bean is the same feature. The user needs to type a few characters and then choose from the search results.
Also various Go to Test, Action/View, Controller, and similar action may share a common UI. Maybe.
Merging sounds like a good approach to try.
Who actually owns task like this? Is it UI/HIE team who drive this? Because it is functionality cross several modules
which individual module owners tend to ignore. Recently I played with IDE from user's point of view and there are some
inconsistencies or "implementation/architecture" leaks. Perhaps the IDE needs another Out-of-Box Experience study? Do
you, Jano, plan to do something like that or have resources for that? I think it would be good theme for next release.
In theory, tasks like this should be driven by HIEs. The first step should be filing it as a PLAN issue so that it's considered during the planning phase for the
Taking ownership, jrojcek no longer works on NetBeans.
I'm coming to a conclusion that better way is to integrate these actions together, rather than just grouping them into a submenu. In a submenu containing many of these actions, it'll still be difficult to understand which action to use for given goal.
Marking as duplicate of issue which requests to integrate "Go To" actions.
*** This bug has been marked as a duplicate of bug 148052 ***