Community
Participate
Working Groups
Using the 20020214 Windows build. 1) Go to the Java Perspective 2) Add the Navigator view to the perspective as a tab next to the Packages view 3) Select a project in the Packages view 4) Switch to the Team perspective 5) In the Navigator select a project 6) Switch back to the Java perspective The Navigator view will be surfaced, instead of the Packages view which was showing when the perspective was switched. Step 5 is the critical step -- if you just switch perspectives without selecting a project in the Navigator, the Navigator won't be surfaced in the other perspective. This is a problem for Websphere Studio because we have two perspectives which contain custom navigation views and have the Navigator available as a tab.
Can you provide more details about the problem that occurs in Websphere? Do you feel that the user would be confused because of the custom navigation view and the Navigator in the same perspective. One arguement that might work is that the perspctive is not in the exact state that the user left it in.
Created attachment 447 [details] Screen capture of J2EE view w/ Navigator
In both WebSphere perspectives, the custom Navigator-like views are specialized enough that it's useful to provide the Navigator in the perspective as well. See the attached picture for a screenshot of the J2EE perspective containing the J2EE view as well as the Navigator. As you said, the crux of this problem is that the perspective is not in the exact state that the user left it, and that's definitely confusing and annoying.
When switching to perspectives we should remember the active part.
Waiting for comments back from usability team. Currently the active part is shared across perspectives in the same page. The problem gets interesting if the editor was active when you switch back to the original perspective...in that case does it make sense for the J2EE view get focus instead of the editor? These are questions I'm waiting for the usability team to answer. I think this is one of these problem no matter which way we go, in some situations, it will be wrong.
If the editor was active, I think it makes sense for the editor to be active when you switch the perspective back. However, the real problem is that with the current behavior the Navigator is now showing (even though it's not active) instead of the J2EE view (they are part of the same folder group). I assume the Navigator is surfaced when it becomes active in another perspective. It's "what's on top in a folder group" that also needs to be remembered when switching perspectives. There are two cases there though: (1) Suppose both the Navigator and J2EE view are in perspectives P1 and P2. The J2EE view is active in P1, then the user switches to P2, does some work in the Navigator, then switches back to P1. (2) The J2EE view is only in P1, but the Navigator is in P1 and P2. Same usage scenario as (1). In (2), I definitely think the J2EE view needs to be on top (though not necessarily active) when switching back to P1. Not sure about (1). Thanks.
Defer until after release 2.0
Reopen to investigate
Reassigning bugs in component areas that are changing ownership.
Is this still a problem in 3.3? PW
Changes requested on bug 193523
The nav view is deprecated PW
