Bug 252116

Summary:	[CommonNavigator] Allow Top Level Element Grouping In Navigator View
Product:	[Eclipse Project] Platform	Reporter:	Nicholas Wourms <nwourms>
Component:	UI	Assignee:	Francis Upton IV <francisu>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	3.5
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Nicholas Wourms

2008-10-26 09:04:00 EDT

While I find both Package and Project Explorer views to be somewhat useful, I have found myself using the Navigator view more and more due to the fact that it shows the *exact* filesystem layouts. One thing I miss from the other two views is the ability to group by top level elements, specifically by working sets. Just as you can in the other two, I know you can use "Select Working Set" to achieve similar results. However, I just find that cumbersome in comparison with the grouping by top level elements feature, since the latter allows unfettered access to any working set content. Since it has been implemented on the other two views, I am filing this feature request that it similarly be implemented in the Navigator view.

Comment 1 Kevin McGuire

2008-10-27 17:41:33 EDT

I suppose solution would be to add to CNF first (so we get Project Explorer), then someday have Package Explorer be based on it.  Thus logging this against CNF.

Comment 2 Francis Upton IV

2009-02-10 03:21:10 EST

I'm sorry, but I don't know what you mean by the "grouping by top level elements" feature.  The working set support in the resource navigator looks to be about the same as in the project explorer.

Can you elaborate more as to what we can do to the project explorer to make you like it better?

Comment 3 Eclipse Webmaster

2019-09-06 15:32:50 EDT

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.