Bug 165160 - [TabbedProperties] Need support for declarative filters
Summary: [TabbedProperties] Need support for declarative filters
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Anthony Hunter CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 164455
  Show dependency tree
 
Reported: 2006-11-20 10:15 EST by Michael Valenta CLA
Modified: 2019-09-06 16:09 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Valenta CLA 2006-11-20 10:15:24 EST
Bug 164455 is a request to added tabbed properties for resources in order to show their CVS information in the properties view. The problem is that the filter is written in the CVS plug-in and will hence require that the CVS plug-in be loaded. The only solution that is possible now is to specify that the filter class can be loaded without starting the bundle. This has many problems associated with it:

1) We shouldn't need to run any CVS code if the user doesn't have any CVS projects loaded

2) Maintaining the separation between the excluded classes and the rest of the bundle is not trivial especially without tooling support.

3) There are already mechanisms in place in the Platform that support declarative filter (i.e. enablement rules).

I think it would be beneficial to support declarative filtering for tabbed properties contributions. Ideally the solution should use enablement rules in order to be consistent with the other contributions (e.g objectContributions and decorators).
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:09:21 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.