Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-ui-dev] Re: first phase of ResourceNavigator end of life is done

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.


Markus Keller wrote:

I fully agree with Johan. I have exactly the same use case, and I often do Navigate > Show In > Navigator from the Package Explorer to see the "Resource" view and context of the selected item.


From: Johan Compagner <jcompagner@xxxxxxxx>
To: platform-ui-dev@xxxxxxxxxxx
Date: 2009-03-10 10:31
Subject: [platform-ui-dev] Re: first phase of ResourceNavigator end of life        is        done

> applications out there that use it (or at least used to). 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.
> Note there are likely bits and pieces of API outside the navigator API
> package that will also need deprecating. IPageLayout.ID_RES_NAV comes to
> mind, for example.
> Next step: orderly death of the package explorer  :)

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
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...


platform-ui-dev mailing list

_______________________________________________ platform-ui-dev mailing list platform-ui-dev@xxxxxxxxxxx

You have brains in your head.
You have feet in your shoes.
- Dr Seuss, Oh the Places You'll Go

Francis Upton IV
Tel   510 835 3123
Fax   510 779 5226
Cell  510 432 1589
Skype francisupton

Back to the top