Community
Participate
Working Groups
I would like to be able to open the "Team Perspective" at any time. Or the "Debug Perspective" at any time. But, to be able to do this, I must customize the perspective which I am coming from, to allow me to choose the perspectives I want to go to. This doesn't make sense. The reason I am opening a new perspective is because I want to do something *unrelated* to what I am currently doing. There should be a single global list of perspectives which I can make available regardless of the current perspective. This would also simplify the UI.
Window > Open Perspective > Other...?
Yes, I'm aware of the "Other..." option. But, given that you can customize the menu to display N custom choices, I don't want to have to do so N times.
We could support multi-select in the Open Perspective dialog. Also, at one point in time we automatically added a shortcut under Window > Open Perspective if you chose an item from the dialog. Likewise for views. We have stopped doing this for both in 3.0 since some people found the free side effect confusing. Since then, I've found that it's really nice to have the free shortcut, especially for views (for perspectives, I generally keep them open if I'm using them). I think we should add the free shortcuts back, but explain the side effect better, e.g. add a checkbox to the dialog to add the shortcut (checked by default). Another option would be to allow the user to customize which perspectives always have shortcuts, independent of the perspective showing the shortcuts. Likewise for views. There's also a discrepancy between how action sets can appear and how they're presented in the Customize Perspective dialog. Currently action sets can be turned on globally (state="true" in the XML), associated with a perspective, or associated with a part (e.g. open Package Explorer in the Resource perspective). However, the Customize Perspective dialog only presents simple checkboxes for action sets. If you make a change, it's associated only with the current perspective. There's no way for the user to turn an action set on globally, or associate it with a part. I think at a minimum, we want to allow the user to: - turn on/off an action set globally - turn on/off an action set in the current perspective - make action set part associations clearer, even if the user can't create new associations - turn on/off a perspective shortcut globally - turn on/off a perspective shortcut in the current perspective - turn on/off a new wizard shortcut globally - turn on/off a new wizard shortcut in the current perspective
Nick, what ever happened to this bug? After thinking more about it, I don't understand why perspective choices and wizard choices would have anything to do with the current perspective. If I create a new project, often this causes a perspective change anyway. The flexibility you are suggesting would lead to a complex UI. I think a single global set of choices is better than the current behavior. Supporting both would be overkill IMO.
This got dropped. No changes planned for 3.0.
Reopening for 3.2. It's annoying that to open the CVS perspective from the Java Perspective, I must first select Resources. Or, to open Debug perspective from Resource, I must select Java. The list of available perspectives should be the same all the time. Or, at least a subset of that list should be static and determined by the user.
*** Bug 101781 has been marked as a duplicate of this bug. ***
See also the discussion in bug 101781. Marking for consideration for 3.2.
Reassigning bugs in component areas that are changing ownership.
There are currently no plans to work on this feature. 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.
