Bug 88476 - [Preferences] API needed to open pref pages on a keyword
Summary: [Preferences] API needed to open pref pages on a keyword
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-03-18 11:16 EST by Mazen Faraj CLA
Modified: 2009-08-30 02:20 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 Mazen Faraj CLA 2005-03-18 11:16:00 EST
currently the preference page support allows for an api that show a list of 
filtered preferences pages. This list is constructed from the ids of the 
preference pages. 
It would be nice if instead of ids, the PreferenceUtil methods accepted a 
keyword instead. This way I dont have to painstakingly find out what the pref 
page ids are by looking at numerous plugin.xmls.

Alternatively, an api that returns a list of pref page ids given a keyword. 

(and on the same topic, how come the a Java preference page appears when you 
filter by the string "Appe". I could not find any Java pref page that was 
defined with an appearance keyword. )
Comment 1 Mazen Faraj CLA 2005-03-18 12:55:44 EST
ps: maybe Im missing something here, but is the text filtering mechanism 
documented somewhere? Is this just a simple grep?
Comment 2 Mazen Faraj CLA 2005-03-21 10:18:29 EST
Tod,
is the filtering just a text grep on the begining of each pref page name? is 
that what is it? any * substitution?
Comment 3 Tod Creasey CLA 2005-03-21 10:21:28 EST
On the keyword and each word in the game. We don't prefix with * becuase of
false positives.
Comment 4 Tod Creasey CLA 2007-03-14 15:29:21 EDT
There are currently no plans for the Platform team to implement this feature.
Comment 5 Denis Roy CLA 2009-08-30 02:20:33 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.