Community
Participate
Working Groups
When I click on "Open Perspective" button, I often get only one perspective to choose from, in addition to "Other...". I find this quite annoying. Makes me move my mouse and click twice. Especially when the dialog that pops up show so few perspectives that they easily fit in the original list. I know progressive disclosure and showing me all the options are conflicting design tradeoffs, but I'd suggest to reconsider the use cases. I press "Other..." so often, in fact, more often than an offered choice, it makes me wonder. This button is really a role-switcher. Make it easier to switch roles?
Nick, If this is related to New Look, please reassign. Sorry.
We used to keep an MRU list of recently used perspectives, and add them to the shortcut list for free (up to a total size of 10). But this didn't scale well, and it went against the intent of allowing perspectives to spell out the valid transitions to/from other perspectives. What we could do, though, is recognize that if a user chooses a different perspective, then that is a valid transition and we should remember it in the shortcut list (for the originating perspective only). There are also cases where the perspective shortcut list does not include the current perspective. This is just silly since the menu should indicate which of the listed perspectives is the current one. We could also add more shortcuts in the SDK, e.g. have a CVS shortcut in the Java perspective. Unfortunately, these two don't know about each other so this would have to be added by a 3rd party.
Can you give concrete examples of transitions that you're missing?
The one I miss most often are the most basic perspectives: Resource and CVS. Couldn't they somehow specific that they want to be added to anyone's choice, regardless who it is? In other words, no matter what is my current perspective, I want a quick way to get to CVS or a resource perspective (none of which are proposed by Java)
Reassigning bugs in component areas that are changing ownership.
Is this still a problem in 3.3? PW
Changes requested on bug 193523
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
