mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-03 23:25:26 +02:00
Code Issues Wiki Activity

[211095] [doc] Remove duplication in list of RSE extension points

Browse source 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=211095
This commit is contained in:
David Dykstal 2008-06-06 18:47:20 +00:00
parent b2c5e27288
commit 8bf7fd17d4
1 changed files with 16 additions and 27 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
rse/doc/org.eclipse.rse.doc.isv/guide/Extensions.html
View file

@ -5,6 +5,7 @@
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2002, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<!-- David Dykstal (IBM) - [] remove unintended duplication from the list of extension points -->
<link rel="stylesheet" type="text/css" HREF="../book.css">
<title>Remote System Explorer Extension Points</title>
</head>
@ -15,9 +16,9 @@
<p>
This product is built on the Eclipse platform
(<A href="http://www.eclipse.org">www.eclipse.org</A>)
and so it offers all the
and so it offers all the
capabilities of Eclipse. This includes the ability to create new Eclipse plug-ins to contribute
additional functions to Eclipse. You can write plug-ins using Java, using Eclipse itself (or this product),
additional functions to Eclipse. You can write plug-ins using Java, using Eclipse itself,
with the Plug-in Development Environment (PDE) perspective. Plug-ins contain a file named <code>plugin.xml</code> that
registers their functions. All such functions are created by use of <b>extension points</b>.
These are either supplied by Eclipse or by other plug-ins. The plugin.xml file describes which extension
@ -26,8 +27,8 @@ additional functions. Each extension point identifies a Java interface (or base
classes exploiting the extension point must implement (or extend).
</p>
<p>
There are many Eclipse-supplied extension points, as described in
this product's online help. In addition to the Eclipse extension points, there
There are many Eclipse-supplied extension points described in
this documentation. In addition to the Eclipse extension points, there
are unique Remote System Explorer extension points that enable you to contribute property pages and
pop-up menu actions to remote objects within the Remote Systems view, among other things. The base Eclipse extension
points are not sufficient for these, as they do not allow scoping of those property pages and
@ -35,16 +36,13 @@ actions such that they only appear for certain remote objects meeting specific f
</p>
<p>
Here we will introduce the unique extension points defined by the Remote System Explorer. They are
further described in the reference section. These extension points are specifically designed to make
Listed below are the most common extension points defined by the Remote System Explorer.
They are further described in the reference section along with others that are more special-purpose.
The ones listed here are specifically designed to make
it easy to contribute functions to the pop-up menus of remote objects displayed in the Remote
Systems view. These extension points are defined in the plugin.xml file of the
<code>org.eclipse.rse.core</code> plugin, which you will find in the plugins sub-folder of your
installation directory. This file has comment blocks that offer further information about the
extension points defined in it.
Here are the extension points that are defined by the RSE:
</P>
Systems view. These extension points are defined by the
<strong>org.eclipse.rse.core</strong> and <strong>org.eclipse.rse.ui</strong> plugins.
</p>
<TABLE border="1">
<TBODY>
<TR>
@ -52,24 +50,24 @@ Here are the extension points that are defined by the RSE:
<TH>Description</TH>
</TR>
<TR>
<TD><A href="plugin/systemtype.html">org.eclipse.rse.core.<b>systemTypes</b></A></TD>
<TD><A href="plugin/systemtype.html">org.eclipse.rse.core.systemTypes</A></TD>
<TD>For defining new system types that show up in the New Connection wizard.</TD>
</TR>
<TR>
<TD><A href="plugin/subsystem.html">org.eclipse.rse.core.<b>subsystemConfigurations</b></A></TD>
<TD><A href="plugin/subsystem.html">org.eclipse.rse.core.subsystemConfigurations</A></TD>
<TD>For defining new subsystems that appear when a connection is expanded.</TD>
</TR>
<TR>
<TD><A href="../reference/extension-points/org_eclipse_rse_services_archivehandlers.html">org.eclipse.rse.services.<b>archivehandlers</b></A></TD>
<TD><A href="../reference/extension-points/org_eclipse_rse_services_archivehandlers.html">org.eclipse.rse.services.archivehandlers</A></TD>
<TD>For supporting additional archive file types, such as is done today for zip, jar and tar files. This adds support for expanding the archives and supporting all the usual actions on the contents.</TD>
</TR>
<TR>
<TD><A href="plugin/popup.html">org.eclipse.ui.<B>popupMenus</B></A></TD>
<TD><A href="plugin/popup.html">org.eclipse.ui.popupMenus</A></TD>
<TD>For defining actions, which appear in the pop-up menu of remote objects
listed in the Remote Systems view.</TD>
</TR>
<TR>
<TD><A href="plugin/propertypage.html">org.eclipse.ui.<b>propertyPages</b></A></TD>
<TD><A href="plugin/propertypage.html">org.eclipse.ui.propertyPages</A></TD>
<TD>For defining property pages, which appear in the Properties dialog when
users select the Properties action from the pop-up menu of remote
objects listed in the Remote Systems view.</TD>
@ -82,14 +80,5 @@ Here are the extension points that are defined by the RSE:
-->
</TBODY>
</TABLE>
<!-- TODO
should we add a reference to the runtime-options here,
instead of the old rseConfigDefaults extension point?
<TD>For solution providers that are building a product that includes RSE,
these runtime options allow you to pre-set some out-of-box preference
values. For example, whether the New Connection tree item is shown in
Remote Systems view.</TD>
-->
</body>
</html>