mbien commented on PR #7925:
URL: https://github.com/apache/netbeans/pull/7925#issuecomment-2571659609
I think the main lesson here is that UI discussions should happen _before_
implementation. Since having extra buttons as part of the tree, a toolbar or
part of the tab implementation are three different stories. This will also
decide _where_ they should show up, since "Projects" is not the only component
with a tree.
The next question would be _what else_ could be added to that component in
future - this might also influence how it is implemented and where to put it.
UI changes are never as easy as they seem, esp not in a core component of a
20+ year old IDE. The last trivial-looking contribution we merged will probably
take 1-2 releases to stabilize. The committer which ends up merging this
feature should also be willing to do that, since I am still busy thinking about
how to fix the fallout of the last contribution :P
My personal opinion is that a toolbar on the bottom (or moveable), analog to
navigator is still a very flexible contender since:
- the feature is already there (easier to implement + UI consistency
perspective + self explanatory)
- can be minimized out of the box (since the first question after release
of this feature will be "how to turn it off")
- is very flexible and has space, e.g
- Favorites view could have the "Add to Favorites..." action on it
- buttons for project group management could be nice on the "Projects"
view
- "synchronize editor with views" toggle could also move there on the
main 3 views
- if it turns out that the toolbar is not cool enough, some actions could
be still moved into something else later
- (someone once said that the main purpose of toolbars is to discover
features and their hotkeys via tooltips without having to read the doc)
For me personally I like the proposal to move it to the tab component the
least, since it will likely end up being the most difficult implementation and
it is the spot with the smallest amount of space (I have no room left so i
would likely end up turning it off anyway). The button count will also change
when switching between views which might look weird/cause other problems. Also
for me personally again, the collapse/expand actions are probably the most
uninteresting actions to put there. Since for expand I use
`ctrl+shift+[1,2,3]`, which will also switch to the right view too - all in one
action. So I would not have a reason to ever click on it in the first place ;).
But I don't really feel strongly about any of this (also super busy
recently), so I will slowly leave the room again and let others handle this ;)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
