Bug 30406 - [WorkingSets] General filter mechanism for resource based views.
Summary: [WorkingSets] General filter mechanism for resource based views.
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2003-01-28 12:27 EST by Michael Valenta CLA
Modified: 2019-09-06 16:06 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Valenta CLA 2003-01-28 12:27:44 EST
It would be helpful if there were a general filter mechanism provided by 
Platform UI that would allow plugins to provide resource filters that could be 
applied to resource views (e.g. Navigator, Package Explorer, etc). Here are 
some example cases were such a mechanism would be helpful.

The JDT UI provides several filters on their views related to properties on 
various resources (Jave element, non-Java element, package, etc.). A request 
has been made for a filter that shows shard projects (see bug 21896). Although 
Team does provide API to give them this and JDT UI can referecne the team 
plugin, the problem is that a JDT filter will be specific to the JDT UI and 
would have to be reimplemented by other views that wanted the same filter. 

Another example of a useful filter would be to show CVS resources that are 
dirty. This could only be done in a plugin that references the CVS plugin. 
Therefore, such a filter could never be provided for the JDT UI or Navigator 
unless a general filter definition mechanism were created.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:06:04 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.