Description: This extension point allows a plug-in to register
search pages for specialized searches. When the search action is performed on
a resource, the search infrastructure locates the most specific registered search
page for it.
<!ELEMENT page EMPTY>
id CDATA #REQUIRED
label CDATA #REQUIRED
class CDATA #REQUIRED
icon CDATA #IMPLIED
sizeHint CDATA #REQUIRED
tabPosition CDATA #IMPLIED
extensions CDATA #IMPLIED
showScopeSection CDATA #IMPLIED
enabled CDATA #IMPLIED
- id - a unique name that will be used to identify this search page
label - a translatable label that will be used in the search page tab
class - a name of the class that implements org.eclipse.search.ui.ISearchPage.
We recommend subclassing org.eclipse.jface.dialogs.DialogPage.
icon - a relative name of the image that will be used for all resources
that match the specified extensions. If omitted, the
search page's tab will only contain a label.
sizeHint - a hint for the initial size of the page. This is a string
containing the width and height separated by comma (e.g. "50, 60"). In the case
this hint is omitted the page will be no larger than the other pages.
tabPosition - an integer defining where the page is placed in the
page book. The value does not define the absolute position but the position
relative to the other pages. The ordering of pages is as follows:
- if the tabPosition is not specified for a page then Integer.MAX_VALUE / 2 is used
- the page with the lower value comes first. If the values are equal
then the pages are are ordered alphabetically according to their labels
extensions - a comma separated list with file extensions on which the
search page can operate. Each extension must also include a weight (0 meaning
lowest weight) which enables the search infrastructure to find the best fitting
page. The weight is separated from the extension by a colon.
If a search page can search all possible resources then "*" can be used.
showScopeSection - if this attribute is missing or set to "false" then the
scope section is not shown in the Search dialog. To see the scope section this
attribute has to be set to "true". Plug-ins which add their own Search page and
want to see the scope section have to add this to their plugin.xml.
- enabled - if this attribute is missing or set to "false"
then the page is not initially shown in the Search dialog. The page can
be activated by the user via the "Customize..." button on the Search dialog.
The following is an example of a search page extension definition:
Supplied Implementation: The search infrastructure provides
a search page for full-text search.