1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-06 08:35:26 +02:00

[cleanup] Review *.exsd schemas for incorrect references, fix some names along the way

This commit is contained in:
Martin Oberhuber 2006-08-24 14:40:15 +00:00
parent 5d23fe954d
commit f3ec227b11
9 changed files with 105 additions and 99 deletions

View file

@ -1,93 +1,95 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<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, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" HREF="../book.css">
<title>Remote System Explorer Extension Points</title>
</head>
<body>
<h1>Remote System Explorer Extension Points</h1>
<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
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 <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
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).
</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
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.
</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
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>
<TABLE border="1">
<TBODY>
<TR>
<TH>Extension Point</TH>
<TH>Description</TH>
</TR>
<TR>
<TD><A href="plugin/systemtype.html">org.eclipse.rse.core.<b>systemType</b></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>subsystemConfiguration</b></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_ui_archivehandlers.html">org.eclipse.rse.core.<b>archivehandlers</b></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.rse.ui.<B>popupMenus</B></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.rse.ui.<b>propertyPages</b></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>
</TR>
<TR>
<TD><A href="../reference/extension-points/org_eclipse_rse_ui_remoteSystemsViewPreferencesActions.html">org.eclipse.rse.ui.<b>remoteSystemsViewPreferencesAction</b></A></TD>
<TD>For contributing a fastpath action to jump to your preferences page, from the local pulldown menu of the Remote Systems view.</TD>
</TR>
<TR>
<TD><A href="../reference/extension-points/org_eclipse_rse_ui_compile.html">org.eclipse.rse.ui.<b>compile</b></A></TD>
<TD>For contributing compile commands to the Compile menus and Work With Compile Commands dialog.</TD>
</TR>
<TR>
<TD><A href="../reference/extension-points/org_eclipse_rse_ui_rseConfigDefaults.html">org.eclipse.rse.ui.<b>rseConfigDefaults</b></A></TD>
<TD>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.</TD>
</TR>
</TBODY>
</TABLE>
</body>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<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, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" HREF="../book.css">
<title>Remote System Explorer Extension Points</title>
</head>
<body>
<h1>Remote System Explorer Extension Points</h1>
<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
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 <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
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).
</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
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.
</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
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>
<TABLE border="1">
<TBODY>
<TR>
<TH>Extension Point</TH>
<TH>Description</TH>
</TR>
<TR>
<TD><A href="plugin/systemtype.html">org.eclipse.rse.core.<b>systemType</b></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>subsystemConfiguration</b></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_ui_archivehandlers.html">org.eclipse.rse.core.<b>archivehandlers</b></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.rse.ui.<B>popupMenus</B></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.rse.ui.<b>propertyPages</b></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>
</TR>
<TR>
<TD><A href="../reference/extension-points/org_eclipse_rse_ui_remoteSystemsViewPreferencesActions.html">org.eclipse.rse.ui.<b>remoteSystemsViewPreferencesActions</b></A></TD>
<TD>For contributing a fastpath action to jump to your preferences page, from the local pulldown menu of the Remote Systems view.</TD>
</TR>
<!-- TODODeferred after RSE 1.0
<TR>
<TD><A href="../reference/extension-points/org_eclipse_rse_ui_compile.html">org.eclipse.rse.ui.<b>compile</b></A></TD>
<TD>For contributing compile commands to the Compile menus and Work With Compile Commands dialog.</TD>
</TR>
-->
<TR>
<TD><A href="../reference/extension-points/org_eclipse_rse_ui_rseConfigDefaults.html">org.eclipse.rse.ui.<b>rseConfigDefaults</b></A></TD>
<TD>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.</TD>
</TR>
</TBODY>
</TABLE>
</body>
</html>

View file

@ -34,7 +34,7 @@ there are a series of filtering attributes. These attributes are identical to th
extension point. Providers supply as many as needed to uniquely identify their target objects. Every one of these
values can be scalar or "simple generic", meaning it can start or end with an asterisk for pattern matching:
<ul>
<li><b>subsystemfactoryid</b>. Restrict to remote objects originating from subsystems created by this subsystem factory.
<li><b>subsystemconfigurationid</b>. Restrict to remote objects originating from subsystems created by this subsystem factory.
<li><b>typecategoryfilter</b>. Restrict to remote objects originating from subsystems created by a subsystem factory that specified this value for their category attribute
<li><b>namefilter</b>. Restrict to remote objects matching this simple generic name
<li><b>typefilter</b>. Restrict to remote objects matching this simple type filter. The "type" of any remote object is subsystem-determined.

View file

@ -30,7 +30,7 @@ object via its ID.<li><b>vendor</b>. Your company name, shown in properties dial
<li><b>icon</b>. The icon displayed in the Remote Systems view for each subsystem created by this subsystem configuration.
<li><b>iconlive</b>. The icon used when the subsystem is physically connected to its remote system.
<li><b>name</b>. The name displayed in the Remote Systems view for each subsystem created by this subsystem configuration.
<li><b>systemtypes</b>. A semi-colon separated list of system types which this subsystem configuration supports. When a user creates a
<li><b>systemTypes</b>. A semi-colon separated list of system types which this subsystem configuration supports. When a user creates a
connection, this configuration will only be asked to create a subsystem for connections to systems of these types. The default is all
system types.
<li><b>category</b>. A name used to categorize this subsystem's functionality. Used by the <A href="popup.html">popupMenus</A>

View file

@ -80,7 +80,7 @@ add the line highlighted <a href="rseSamplesResources3.html">here</a>.
&lt;extension point=&quot;org.eclipse.rse.ui.subsystemConfiguration&quot;&gt;
&lt;configuration
id=&quot;samples.subsystems.factory&quot;
systemtypes=&quot;Linux;Unix;Windows&quot;
systemTypes=&quot;Linux;Unix;Windows&quot;
name=&quot;Teams&quot;
class=&quot;samples.subsystems.DeveloperSubSystemConfiguration&quot;
category=&quot;users&quot;

View file

@ -15,7 +15,7 @@ extend the RSE:
<ul>
<li><a href="tutorial/popup.html">Creating a remote resource pop-up menu action</a> using the <a href="plugin/popup.html">org.eclipse.rse.core.popupMenus</a> extension point.
<li><a href="tutorial/propertypage.html">Creating a remote resource property page</a> using the <a href="plugin/propertypage.html">org.eclipse.rse.core.propertyPages</a> extension point.
<li><a href="tutorial/subsystem.html">Creating a subsystem configuration</a> for working with remote resources, using the <a href="plugin/subsystem.html">org.eclipse.rse.core.subsystemconfiguration</a> extension point.
<li><a href="tutorial/subsystem.html">Creating a subsystem configuration</a> for working with remote resources, using the <a href="plugin/subsystem.html">org.eclipse.rse.core.subsystemConfiguration</a> extension point.
</ul>
<p>The source code for all tutorials is available in the RSE-examples package, which
can be obtained from the DSDP <a href="http://download.eclipse.org/dsdp/tm/downloads">

View file

@ -13,7 +13,9 @@
<ul>
<li><a href="org_eclipse_rse_core_systemTypes.html">org.eclipse.rse.core.systemTypes</a></li>
<li><a href="org_eclipse_rse_ui_archivehandlers.html">org.eclipse.rse.ui.archivehandlers</a></li>
<!-- TODODeferred after RSE 1.0
<li><a href="org_eclipse_rse_ui_compile.html">org.eclipse.rse.ui.compile</a></li>
-->
<li><a href="org_eclipse_rse_ui_dynamicPopupMenuExtensions.html">org.eclipse.rse.ui.dynamicPopupMenuExtensions</a></li>
<li><a href="org_eclipse_rse_ui_keystoreProviders.html">org.eclipse.rse.ui.keystoreProviders</a></li>
<li><a href="org_eclipse_rse_ui_mountPathMappers.html">org.eclipse.rse.ui.mountPathMappers</a></li>

View file

@ -8,7 +8,9 @@
<topic label="Extension Points Reference">
<topic label="org.eclipse.rse.core.systemTypes" href="reference/extension-points/org_eclipse_rse_core_systemTypes.html" />
<topic label="org.eclipse.rse.ui.archivehandlers" href="reference/extension-points/org_eclipse_rse_ui_archivehandlers.html" />
<!-- TODODeferred after RSE 1.0
<topic label="org.eclipse.rse.ui.compile" href="reference/extension-points/org_eclipse_rse_ui_compile.html" />
-->
<topic label="org.eclipse.rse.ui.dynamicPopupMenuExtensions" href="reference/extension-points/org_eclipse_rse_ui_dynamicPopupMenuExtensions.html" />
<topic label="org.eclipse.rse.ui.keystoreProviders" href="reference/extension-points/org_eclipse_rse_ui_keystoreProviders.html" />
<topic label="org.eclipse.rse.ui.mountPathMappers" href="reference/extension-points/org_eclipse_rse_ui_mountPathMappers.html" />
@ -17,7 +19,7 @@
<topic label="org.eclipse.rse.ui.persistenceProviders" href="reference/extension-points/org_eclipse_rse_ui_persistenceProviders.html" />
<topic label="org.eclipse.rse.ui.popupMenus" href="reference/extension-points/org_eclipse_rse_ui_popupMenus.html" />
<topic label="org.eclipse.rse.ui.propertyPages" href="reference/extension-points/org_eclipse_rse_ui_propertyPages.html" />
<topic label="org.eclipse.rse.ui.remoteSystemsViewPreferencesAction" href="reference/extension-points/org_eclipse_rse_ui_remoteSystemsViewPreferencesAction.html" />
<topic label="org.eclipse.rse.ui.remoteSystemsViewPreferencesActions" href="reference/extension-points/org_eclipse_rse_ui_remoteSystemsViewPreferencesActions.html" />
<topic label="org.eclipse.rse.ui.rseConfigDefaults" href="reference/extension-points/org_eclipse_rse_ui_rseConfigDefaults.html" />
<topic label="org.eclipse.rse.ui.subsystemConfiguration" href="reference/extension-points/org_eclipse_rse_ui_subsystemConfiguration.html" />
<anchor id="rse-extension-points-ref" />

View file

@ -38,7 +38,7 @@ Contributors:
point="org.eclipse.rse.ui.popupMenus">
<objectContribution
adaptable="false"
subsystemfactoryCategory="files"
subsystemconfigurationCategory="files"
typefilter="folder"
id="org.eclipse.rse.eclipse.filesystem.createproject.">
<visibility>

View file

@ -24,7 +24,7 @@ Contributors:
<extension
point="org.eclipse.rse.ui.subsystemConfiguration">
<factory
systemtypes="Local"
systemTypes="Local"
name="%Factory.LocalProcesses"
iconlive="icons/full/obj16/activeprocess.gif"
icon="icons/full/obj16/activeprocess.gif"