Community
Participate
Working Groups
I find it somewhat frustrating that every perspective shows all projects in their corresponding navigator-like views. It would be very helpful if there were a way to make the perspective show exclusively projects made to work with that perspective (both closed and opened projects), for example, show only normal Java projects in the Java perspective's "Package Explorer", only C/C++ projects in the CDT perspective's "C/C++ Projects", and so on. It would be practical to have this feature available as a switch, possibly on by default, and possibly as a button near "Link with Editor" but acceptable in a menu or under preferences... Worksets are not really an alternative, as they are failing on the "automatic" part of this feature request, which becomes a real burden when having lots of projects that are not already organized into worksets. Not to mention that you cannot add closed projects to CDT's "C/C++ Projects". And that every new project has to explicitly be categorized into a workset. The actual need for having this feature is not apparent before having a lot of projects in a single workspace and having to find a specific project, buried amongst projects which are normally not even theoretical candidates for the given perspective. -- Irfy
Not sure how best to categorize this. There is a consistency issue here, but in the end, if we decide that this is a good idea, it would have to be implemented by all the different navigators, and we would need separate bugs.
Its an interesting idea. Use perspectives to act not only as filters on the set of controls/views you see, but also on the information contained within them. But Boris is right in that at present there'd be no way to enforce it; it would need to be a design pattern people followed.
Hm. How do the individual Navigator-like views fetch their lists of projects? Sorry, I have no clue of the code behind Eclipse, so I'm just guessing - shouldn't there be some kind of abstraction/mechanism "above", which is used by all those views to at least fetch the list of projects? What if a kind of filter is passed on to this mechanism "above"? Not enforceable, but doesn't sound too difficult to think of either. If a view doesn't implement the feature - it works as usual. So, how difficult does it look?
(In reply to comment #0) > I find it somewhat frustrating that every perspective shows all projects in > their corresponding navigator-like views. It would be very helpful if there > were a way to make the perspective show exclusively projects made to work with > that perspective (both closed and opened projects), for example, show only > normal Java projects in the Java perspective's "Package Explorer", only C/C++ > projects in the CDT perspective's "C/C++ Projects", and so on. Well, there's definitely a demand for this as I've seen several users ask about this functionality on IRC. (In reply to comment #3) > Hm. How do the individual Navigator-like views fetch their lists of projects? They probably just query the workspace for all projects. > Sorry, I have no clue of the code behind Eclipse, so I'm just guessing - > shouldn't there be some kind of abstraction/mechanism "above", which is used by > all those views to at least fetch the list of projects? What if a kind of > filter is passed on to this mechanism "above"? Not enforceable, but doesn't > sound too difficult to think of either. If a view doesn't implement the feature > - it works as usual. > > So, how difficult does it look? It's not hard to write a filter implementation. I guess these views would have to listen to perspective changes and then query the workbench for o.e.ui.ide for the "projects" filter or something like that.
this might be interesting for e4, plus we have a new resource filtering story.
Removing outdated target milestone.
