mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-08-04 06:45:43 +02:00
Code Issues Wiki Activity

Remove Useractions from Core feature

Browse source
This commit is contained in:
Martin Oberhuber 2007-05-04 14:16:55 +00:00
parent ed6158f594
commit 300237b585
3 changed files with 50 additions and 52 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -64,12 +64,12 @@ Here are the extension points that are defined by the RSE:
<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> <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>
<TR> <TR>
<TD><A href="plugin/popup.html">org.eclipse.rse.ui.<B>popupMenus</B></A></TD> <TD><A href="plugin/popup.html">org.eclipse.ui.<B>popupMenus</B></A></TD>
<TD>For defining actions, which appear in the pop-up menu of remote objects <TD>For defining actions, which appear in the pop-up menu of remote objects
listed in the Remote Systems view.</TD> listed in the Remote Systems view.</TD>
</TR> </TR>
<TR> <TR>
<TD><A href="plugin/propertypage.html">org.eclipse.rse.ui.<b>propertyPages</b></A></TD> <TD><A href="plugin/propertypage.html">org.eclipse.ui.<b>propertyPages</b></A></TD>
<TD>For defining property pages, which appear in the Properties dialog when <TD>For defining property pages, which appear in the Properties dialog when
users select the Properties action from the pop-up menu of remote users select the Properties action from the pop-up menu of remote
objects listed in the Remote Systems view.</TD> objects listed in the Remote Systems view.</TD>

91
rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_overview.html
View file

@ -1,44 +1,49 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html> <html>
<head> <head>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > <meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2006. 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-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css"> <meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"> <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
<title>RSE Overview</title> <title>RSE Overview</title>
<link rel="stylesheet" type="text/css" href="../book.css"> <link rel="stylesheet" type="text/css" href="../book.css">
</head> </head>
<body> <body>
<h1>RSE Overview</h1> <h1>RSE Overview</h1>
<p> <p>
The perspective for managing connections is the <A href="rse.gif"><B>Remote The perspective for managing connections is the <A href="rse.gif"><B>Remote
System Explorer</B></A> (<b>RSE</b>), and the primary tree-view within it is the System Explorer</B></A> (<b>RSE</b>), and the primary tree-view within it is the
<A href="view_RS.gif"><B>Remote Systems</B></A> view. We assume you are already familiar with the RSE perspective, <A href="view_RS.gif"><B>Remote Systems</B></A> view. We assume you are already familiar with the RSE perspective,
or will familiarize yourself with it, and you are now interested in learning how to extend it. We also assume that you or will familiarize yourself with it, and you are now interested in learning how to extend it. We also assume that you
already understand the concepts of plug-ins, extension points, and the workbench UI. You do not need already understand the concepts of plug-ins, extension points, and the workbench UI. You do not need
to be familiar with workspace resources, as the RSE does not use these to realize the artifacts it to be familiar with workspace resources, as the RSE does not use these to realize the artifacts it
shows to the user. shows to the user.
</p> </p>
<p>A user can extend the Remote System Explorer by adding their own <p>A user can extend the Remote System Explorer by adding their own
<A href="Artifacts.html#filters">filters</A>, <A href="Artifacts.html#filters">filters</A>.
<A href="Artifacts.html#useractions">user actions</A>, and <!--
<A href="Artifacts.html#compilecmds">compile commands</A>. <A href="Artifacts.html#useractions">user actions</A>, and
They may also customize the RSE by setting <A href="Artifacts.html#compilecmds">compile commands</A>.
<A href="Artifacts.html#preferences">preferences</A>.</p> -->
<p> They may also customize the RSE by setting
As a programmer, you can extend the Remote System Explorer by using <A href="Artifacts.html#preferences">preferences</A>.</p>
<A href="../reference/extension-points/index.html">RSE-unique extension points</A> to <p>
add property pages to remote objects, add actions to the pop-up menus for remote objects, and As a programmer, you can extend the Remote System Explorer by using
even create your own subsystems that appear when a connection is expanded. The full Eclipse application <A href="../reference/extension-points/index.html">RSE-unique extension points</A> to
programming interface (API) set is add actions to the pop-up menus for remote objects, create your own
at your disposal for these, as well as the API set supplied by the Remote System Explorer. Furthermore, system types or subsystems that appear when a connection is expanded,
you can use existing Eclipse extension points to author menu items, tool bar actions, pop-up menu actions, or even contribute new persistence schemes for storing RSE data. The full Eclipse application
and more for non-remote objects in the Remote System Explorer. programming interface (API) set is
</p> at your disposal for these, as well as the API set supplied by the Remote System Explorer. Furthermore,
<p> you can use
This guide explains all underlying <a href="../guide/plugin/other.html">Eclipse Platform extension points</a>
artifacts and model of the Remote System Explorer, the RSE extension points, and highlights the to add property pages, author menu items, tool bar actions,
important APIs available for your use. pop-up menu actions, and more for objects in the Remote System Explorer.
</p> </p>
</body> <p>
This guide explains all underlying
artifacts and model of the Remote System Explorer, the RSE extension points, and highlights the
important APIs available for your use.
</p>
</body>
</html> </html>

7
rse/features/org.eclipse.rse.core-feature/feature.xml
View file

@ -133,11 +133,4 @@
version="0.0.0" version="0.0.0"
unpack="false"/> unpack="false"/>
<plugin
id="org.eclipse.rse.useractions"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
</feature> </feature>