Bug 305963 - [Preferences] Allow all preference pages to contribute keywords to the filtered PreferenceDialog
Summary: [Preferences] Allow all preference pages to contribute keywords to the filter...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-16 04:52 EDT by Philipp Kursawe CLA
Modified: 2019-09-06 15:36 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Kursawe CLA 2010-03-16 04:52:01 EDT 
Build Identifier: 

Currently the filtering for keywords is reserved for workbench contributed preference pages.
It would be nice if custom, programmatically provided preference pages could also provide keyword labels for filtering.
To achieve that an easy patch would be required. A new interface
IKeywordLabelProvider would have to be introduced and org.eclipse.ui.internal.dialogs.PreferencePatternFilter would not check for instanceof WorkbenchPreferenceExtensionNode anymore but for IKeywordLabelProvider. WorkbenchPreferenceExtensionNode would implement IKeywordLabelProvider.

interface IKeywordLabelProvider {
  Collection getKeywordLabels();
}

This way the very useful feature of keywords could also be used in custom preference pages provided during runtime and not via extension.

Usecase:
I am currently implementing a preference dialog for OSGI ConfigAdmin configuration management.

Reproducible: Always
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:36:42 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.