Community
Participate
Working Groups
I20070821-0800. 1. in the Resource perspective open the Navigator (or Package Explorer) 2. in the Navigator (or Package Explorer) select a project 3. context menu > Open in New Window ==> now there's no way to make the Project Explorer show the whole workspace.
This is because the page input of the new window is set to that project. There is nothing the package explorer can do (I think) to change the page input. It's annoying and confusing though. Should we try to get rid of the "Go Into"?
I believe Mcq was of the opinion that Go Into/etc should be removed. I'd agree. However, there was a bug he had opened looking for feedback on whether there were usage cases which required this. There was some discussion with one member of the community who wanted to keep them but I don't think a conclusion was reached.
>This is because the page input of the new window is set to that project. There >is nothing the package explorer can do (I think) to change the page input. Right, but that's not what I'm talking about: like the Navigator, the Package Explorer has a local tool bar button (UpAction from Platform UI) that allows to go up to the workspace ('Up to Workspace') - that's the same action that allows to 'Go Up' when 'Go Into' is used (but with a different - dynamic - label). The point is that besides the Project Explorer all other workspace views (Package Explorer, Navigator) allow to go up and show the workspace again even if the input is set and they also offer Go Into and Go Up. Personally I also don't use that functionality but no matter what the consensus was with that discussion we must be consistent now i.e. either - remove all that stuff from all views (including 'Open in New Window') - change the Project Explorer so that it can't go into an element (not so good) - add Go Into and Go Up to functionality the Project Explorer Maybe we should also change the UpAction so that it does not say 'Up to Workspace' but 'Reset Window Input' (and actually set the page input to the workspace).
(In reply to comment #2) > I believe Mcq was of the opinion that Go Into/etc should be removed. Let's discuss this when McQ is back from vacation.
Well, I'm back. :-) See bug 1925 for one user's use case. I'm not recommending that we remove this feature in the 3.4 stream, but for 4.0 we need to either make it work consistently everywhere and make it easy for our users to find, or decide once and for all that it's no longer needed. In this latter case, we need to ensure that all use cases (like the one in bug 1925) are covered.
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.
