Community
Participate
Working Groups
From [platform-ui-dev]: "first phase of ResourceNavigator end of life is done" http://dev.eclipse.org/mhonarc/lists/platform-ui-dev/msg04109.html: My suggestion for an orderly death would be: - Deprecate all APIs immediately but leave everything in place. - Make sure none of the SDK perspectives contain the Navigator in their default layout. - Advertise that it is deprecated and encourage people to move to CNF - Immediately after the 3.5 release, split the navigator view and APIs out of org.eclipse.ui.ide into a separate plug-in. - At some point remove this plug-in from the platform feature (perhaps in 3.6, or else in 4.0). org.eclipse.ui.ide version would need to bump to 4.0 at this point. This way the view is still available for people who still need it for whatever reason. And, with the slightly higher bar of having it in a separate bundle outside the platform, there will be strong incentive for people to move to the Project Explorer. --------- Johan's answer, which I fully support: hmm now i have a Navigator and a Package explorer side by side in almost all my perspectives Will this mean that when you kill both that i have to use a single view (because you cant have multiply copies of the project explorer in 1 perspective) to do the same thing? For example Package explorer does filter quite a lot of files that i sometimes just have to go to. Or i dont want that packages type of viewing for a certain file Now i just take 1 of the 2. So to have this behavior in 1 View, the project explorer, we should really have a very very quick way of switching between packages view and just resource view in side that Project explorer and then not what i have to do now, through menu's and dialogs and checkboxes and ok buttons... -------- Francis' answer: I think we can address this a couple of ways: 1) Leaving a Navigator view (that is based on the CNF but that does not have any of the Java CNF extensions so it looks like the resource navigator). 2) Allowing multiple instances of these navigator views, so that you can make your own project explorer and you can remove the Java CNF extensions using the view menu. Both of these issues are independent of the end of life process for the RN, and I recommend that an enhancement request be filed against the Common Navigator for this functionality so that we can track it. -------- My request: Leave a view in the SDK that behaves like the current Navigator (but may be implemented as a common navigator). All functionality of the resource navigator should be retained (and not deprecated!), especially: - 'Show View > Navigator', which opens a resource-only view - 'Navigate > Show In > Navigator' stays Multiple instances of the Project Explorer are not an option, since this would not support the two use cases above.
Another possibility is to follow the approach of the Synchronize view, which has a drop-down to allow you to select which "model" you want to view (Java, Resources, etc). This has the advantage of not requiring a whole other view for that rare case you need the different layout. As a user I find it annoying when I have to switch out of the Project Explorer into another Navigator-like view just for some small bit of function that wasn't available in the Project Explorer (like the lack of "Source" menu on projects). So, if there was a way to incorporate those use cases into a single view it would be better IMO. Less clutter/complexity/view switching for users.
Well actually the quickest thing that you can do (and you can do it right now) is to simply go to the View menu and go to Customize View, and in the Content tab, uncheck "Java Elements". Then you essentially have a plain navigator view. This works right now. The problem is that hardly anyone knows about this (so there is a documentation issue) Of course as John suggests this can be optimized in the same was as the synchronize view using the drop down button thing.
Cool, I didn't even know about this! Johan, if there was an easy, prominent way to do this switch, would it satisfy your use case?
yes that would do it, i already did know about that preference dialog, i described it already: "So to have this behavior in 1 View, the project explorer, we should really have a very very quick way of switching between packages view and just resource view in side that Project explorer and then not what i have to do now, through menu's and dialogs and checkboxes and ok buttons" problem is that the current way is for quickly doing stuff pretty annoying. Thats more a permanent settings that you want to configure once. So if the contents of the Content tab that we now have in the "Available Customizations" dialog was a quick drop/pull down menu on in the Project Explorer. That would help my case pretty well. Because that would just kind of be the same as switching between package and navigator (but ofcourse not that obvious and does require a bit more ui interaction) So my vote would go to keep the Navigator view and Package Explorer view. But let the contents of that view just be the Project Explorer but then configured differently by default.. Then you dont have old code anymore, you just have the same 2 views that people now love and use, but they use the same code beneath it. But i can live with the second option of having a quick switch in the project explorer.
(In reply to comment #4) > But i can live with the second option of having a quick switch in the project > explorer. > I think we should probably do both, the little button at the top of the view to instantly switch to certain view contents could be very useful for lots of purposes. We can even include various sorting and filters there. And we can certainly keep the Navigator view (which of course would be implemented with the CommonNavigator rather than the RN). Both of these things will happen early in 3.6.
We would also need a way so that I can continue to use Show In > and select either the simple mode (Navigator) or the full model mode (Project Explorer). And of course be able to invoke this directly via key binding.
(In reply to comment #6) > We would also need a way so that I can continue to use Show In > and select > either the simple mode (Navigator) or the full model mode (Project Explorer). > And of course be able to invoke this directly via key binding. > Yes, the idea is that the Navigator view would function pretty much exactly as before, the only different being it does not use the ResourceNavigator class. I will update the RN end of life page to reflect this.
Re switching content extensions with a toolbar dropdown button to get a "resource only" view: This is only quick if there's only one additional content extension. As soon as there's e.g. Java Elements, C++ Element, PHP Elements, etc. you would have to open the menu many times to disable them all.
(In reply to comment #8) > Re switching content extensions with a toolbar dropdown button to get a > "resource only" view: This is only quick if there's only one additional content > extension. As soon as there's e.g. Java Elements, C++ Element, PHP Elements, > etc. you would have to open the menu many times to disable them all. > most of the time i have 1 or the other (i think) so what about not only selecting (same as the checkbox on the list) But really choose just 1? (so not a checkbox thing but a radio, 1 selection allowed) So if package explorer is selected and i select then navigator, it deselects packages explorer and selects the navigator. What you also could do is something defined on top of the current contributions/content. So i will fill that drop down with my own things (like working sets) and item 1 is Navigator and PHP, item 2 is just the package explorer and the last item 3 is C++ and PHP together.
(In reply to comment #8) > Re switching content extensions with a toolbar dropdown button to get a > "resource only" view: This is only quick if there's only one additional content > extension. As soon as there's e.g. Java Elements, C++ Element, PHP Elements, > etc. you would have to open the menu many times to disable them all. > I was thinking along the lines of some additional configuration that would allow you to chose what you wanted in the button, and you could chose from content extensions, filters, or sorters. You should be able to set up this configuration using the view menu. So you can have a small list in the button, and perhaps the top thing in that list can be what the button toggles. This way the user can set it up to quickly get to the things they want.
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.
