blob: 6ee4697a0e62a68f23b60121a8f463f527c139ae [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
<HEAD>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<TITLE>Search support</TITLE>
<link rel="stylesheet" type="text/css" HREF="../book.css">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>
Search support</H1>
<p>
If your plug-in defines and manipulates its own resource types, you may have
special requirements for searching a resource.&nbsp; For example, the Java IDE
plug-in implements a search engine specialized for Java files.&nbsp;&nbsp;&nbsp;</p>
<p>
The <b>search</b> plug-in allows you to add a specialized page describing your
search to the workbench search dialog.&nbsp; This allows you to obtain any
specialized information needed from the user and perform a search using your
plug-in's internal model.</p>
<p>
You should also provide a specialized class for displaying the search results.
Abstract implementations of a search result page are provided to give you a head
start.</p>
<p>
These services are contributed using search plug-in extension points.</p>
</BODY>
</HTML>