-This product is built on the Eclipse platform
-(www.eclipse.org)
- 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),
-with the Plug-in Development Environment (PDE) perspective. Plug-ins contain a file named plugin.xml that
-registers their functions. All such functions are created by use of extension points.
-These are either supplied by Eclipse or by other plug-ins. The plugin.xml file describes which extension
-points are being exploited by each plug-in, and for each identifies the Java class that supplies the
-additional functions. Each extension point identifies a Java interface (or base class) that
-classes exploiting the extension point must implement (or extend).
-
-There are many Eclipse-supplied extension points, as described in -this product's online help. 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 -actions such that they only appear for certain remote objects meeting specific filtering criteria. -
- -
-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
-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
-org.eclipse.rse.core 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:
-
| Extension Point | -Description | -
|---|---|
| org.eclipse.rse.core.systemType | -For defining new system types that show up in the New Connection wizard. | -
| org.eclipse.rse.core.subsystemConfiguration | -For defining new subsystems that appear when a connection is expanded. | -
| org.eclipse.rse.core.archivehandlers | -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. | -
| org.eclipse.rse.ui.popupMenus | -For defining actions, which appear in the pop-up menu of remote objects - listed in the Remote Systems view. | -
| org.eclipse.rse.ui.propertyPages | -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. | -
| org.eclipse.rse.ui.remoteSystemsViewPreferencesAction | -For contributing a fastpath action to jump to your preferences page, from the local pulldown menu of the Remote Systems view. | -
| org.eclipse.rse.ui.compile | -For contributing compile commands to the Compile menus and Work With Compile Commands dialog. | -
| org.eclipse.rse.ui.rseConfigDefaults | -For solution providers that are building a product that includes RSE, this extension point allows you to - pre-set some out-of-box preference values. For example, whether the New Connection tree item is shown in Remote Systems view. | -
+This product is built on the Eclipse platform
+(www.eclipse.org)
+ 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),
+with the Plug-in Development Environment (PDE) perspective. Plug-ins contain a file named plugin.xml that
+registers their functions. All such functions are created by use of extension points.
+These are either supplied by Eclipse or by other plug-ins. The plugin.xml file describes which extension
+points are being exploited by each plug-in, and for each identifies the Java class that supplies the
+additional functions. Each extension point identifies a Java interface (or base class) that
+classes exploiting the extension point must implement (or extend).
+
+There are many Eclipse-supplied extension points, as described in +this product's online help. 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 +actions such that they only appear for certain remote objects meeting specific filtering criteria. +
+ +
+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
+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
+org.eclipse.rse.core 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:
+
| Extension Point | +Description | +
|---|---|
| org.eclipse.rse.core.systemType | +For defining new system types that show up in the New Connection wizard. | +
| org.eclipse.rse.core.subsystemConfiguration | +For defining new subsystems that appear when a connection is expanded. | +
| org.eclipse.rse.core.archivehandlers | +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. | +
| org.eclipse.rse.ui.popupMenus | +For defining actions, which appear in the pop-up menu of remote objects + listed in the Remote Systems view. | +
| org.eclipse.rse.ui.propertyPages | +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. | +
| org.eclipse.rse.ui.remoteSystemsViewPreferencesActions | +For contributing a fastpath action to jump to your preferences page, from the local pulldown menu of the Remote Systems view. | +
| org.eclipse.rse.ui.rseConfigDefaults | +For solution providers that are building a product that includes RSE, this extension point allows you to + pre-set some out-of-box preference values. For example, whether the New Connection tree item is shown in Remote Systems view. | +
The source code for all tutorials is available in the RSE-examples package, which
can be obtained from the DSDP
diff --git a/rse/doc/org.eclipse.rse.doc.isv/reference/extension-points/index.html b/rse/doc/org.eclipse.rse.doc.isv/reference/extension-points/index.html
index 79f2f92a819..972b3c0d501 100755
--- a/rse/doc/org.eclipse.rse.doc.isv/reference/extension-points/index.html
+++ b/rse/doc/org.eclipse.rse.doc.isv/reference/extension-points/index.html
@@ -13,7 +13,9 @@