blob: ce0714d8d373b2b52a4f64f6d679fa5604b17118 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
<HEAD>
<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>Plugging in help
</TITLE>
<link rel="stylesheet" type="text/css" HREF="../book.css">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>
Plugging in help</H1>
<P >
The Eclipse platform's help facilities provide you with the raw building blocks to structure and contribute
documentation to the platform. It does not dictate structure or granularity of documentation.
You can choose the tools and structure for your documentation that suits your
needs.&nbsp; The help plug-in allows you to describe your documentation
structure to the platform using a table of contents (toc) file.</P>
<P >Your plug-in's online help is contributed using the <a href="../reference/extension-points/org_eclipse_help_toc.html"> <b> org.eclipse.help.toc</b></a> extension point. You can either contribute the online help as part of your code plug-in or provide it separately in its own documentation plug-in.</P>
<P >
Separating the documentation into a separate plug-in is beneficial in those situations where the code and documentation teams are different groups or where you want to reduce the coupling between the documentation and code. </P>
<P >
Advanced features of the help system include context-sensitive help with
reference links (known as <b>infopops</b>) and the ability to invoke platform
code from the documentation.&nbsp; A help browser lets you view,
print, and search your documentation.&nbsp;&nbsp; </P>
<P >The best way to demonstrate the contribution of help is to create a
documentation plug-in.</P>
<p><a href="../hglegal.htm"><img border="0" src="../ngibmcpy.gif" alt="Copyright IBM Corporation and others 2000, 2003." border="0" width="324" height="14"></a></p>
</BODY>
</HTML>