diff options
Diffstat (limited to 'rse/doc')
280 files changed, 0 insertions, 13342 deletions
diff --git a/rse/doc/org.eclipse.dstore.doc.isv/.classpath b/rse/doc/org.eclipse.dstore.doc.isv/.classpath deleted file mode 100755 index 3f74547ab..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/.classpath +++ /dev/null @@ -1,6 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
- <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
- <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
- <classpathentry kind="output" path="bin"/>
-</classpath>
diff --git a/rse/doc/org.eclipse.dstore.doc.isv/.cvsignore b/rse/doc/org.eclipse.dstore.doc.isv/.cvsignore deleted file mode 100755 index 891527ed8..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/.cvsignore +++ /dev/null @@ -1,7 +0,0 @@ -bin -index -build.xml -javadoc.link.location -temp.bin.log -temp.options.txt -temp.convert.txt diff --git a/rse/doc/org.eclipse.dstore.doc.isv/.project b/rse/doc/org.eclipse.dstore.doc.isv/.project deleted file mode 100755 index b79ee8ec5..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>org.eclipse.dstore.doc.isv</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- <buildCommand>
- <name>org.eclipse.pde.ManifestBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- <buildCommand>
- <name>org.eclipse.pde.SchemaBuilder</name>
- <arguments>
- </arguments>
- </buildCommand>
- </buildSpec>
- <natures>
- <nature>org.eclipse.pde.PluginNature</nature>
- </natures>
-</projectDescription>
diff --git a/rse/doc/org.eclipse.dstore.doc.isv/META-INF/MANIFEST.MF b/rse/doc/org.eclipse.dstore.doc.isv/META-INF/MANIFEST.MF deleted file mode 100755 index 793d4eb70..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/META-INF/MANIFEST.MF +++ /dev/null @@ -1,8 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.dstore.doc.isv; singleton:=true -Bundle-Version: 1.0.0.qualifier -Bundle-Localization: plugin -Eclipse-LazyStart: false -Bundle-Vendor: %providerName diff --git a/rse/doc/org.eclipse.dstore.doc.isv/aaa-how-to-add-things.txt b/rse/doc/org.eclipse.dstore.doc.isv/aaa-how-to-add-things.txt deleted file mode 100755 index d73e72b8e..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/aaa-how-to-add-things.txt +++ /dev/null @@ -1,29 +0,0 @@ -Last revised July 27, 2006 -(This file is for information only; it is not included in the release.) - -See also - http://wiki.eclipse.org/index.php/How_to_add_things_to_the_Eclipse_doc -with the following exceptions: -- platformOptions.txt -> options.txt -- overview-platform.html -> /reference/misc/overview-rse.html - -To add new plug-ins you need to make changes in several places in -this doc plug-in: - -1) options.txt -- the plug-in's source folder(s) must be included on the -sourcepath -- code of required plug-ins must be added on the -classpath (the JAR(s)for non-JARed plug-ins and <plugin>/@dot for JARed plug-ins -- the API package names must be included in the (alphabetical) package list at the end of the file -- note that the @sep@ token is replaced during build by the appropriate separator character for the build platform. - -2) buildDoc.xml -- add a line in convertSchemaToHtml target to handle a new plug-ins extension point schemas - -Adding new extension points: - -1) reference/extension-points/index.html -- add a line for each extension point - -2) topics_Reference.xml -- add a line for each extension point -- add a line for each API package
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/about.html b/rse/doc/org.eclipse.dstore.doc.isv/about.html deleted file mode 100755 index 460233046..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/about.html +++ /dev/null @@ -1,28 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/> -<title>About</title> -</head> -<body lang="EN-US"> -<h2>About This Content</h2> - -<p>June 2, 2006</p> -<h3>License</h3> - -<p>The Eclipse Foundation makes available all content in this plug-in ("Content"). Unless otherwise -indicated below, the Content is provided to you under the terms and conditions of the -Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available -at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>. -For purposes of the EPL, "Program" will mean the Content.</p> - -<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is -being redistributed by another party ("Redistributor") and different terms and conditions may -apply to your use of any object code in the Content. Check the Redistributor's license that was -provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise -indicated below, the terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p> - -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/book.css b/rse/doc/org.eclipse.dstore.doc.isv/book.css deleted file mode 100755 index 157414c6c..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/book.css +++ /dev/null @@ -1 +0,0 @@ -@import "../PRODUCT_PLUGIN/book.css";
diff --git a/rse/doc/org.eclipse.dstore.doc.isv/build.properties b/rse/doc/org.eclipse.dstore.doc.isv/build.properties deleted file mode 100755 index 8788dc44d..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/build.properties +++ /dev/null @@ -1,22 +0,0 @@ -############################################################################### -# Copyright (c) 2000, 2006 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### -bin.includes = META-INF/,\ - about.html,\ - book.css,\ - notices.html,\ - plugin.properties,\ - plugin.xml,\ - toc.html,\ - toc.xml,\ - guide/,\ - index/,\ - reference/ -customBuildCallbacks = customBuildCallbacks.xml diff --git a/rse/doc/org.eclipse.dstore.doc.isv/buildDoc.xml b/rse/doc/org.eclipse.dstore.doc.isv/buildDoc.xml deleted file mode 100755 index 4701988a4..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/buildDoc.xml +++ /dev/null @@ -1,140 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<project name="RSE DStore ISV Doc Build" default="all" basedir="."> - - <property name="javadoc.link.location" value="${basedir}/javadoc.link.location"/> - - <target name="init"> - <available file="${basedir}/index" property="index.present" /> - <path id="path_bootclasspath"> - <fileset dir="${java.home}/lib"> - <include name="*.jar"/> - </fileset> - </path> - <property name="bootclasspath" refid="path_bootclasspath"/> - <condition property="safeBaseLocation" - value="${baseLocation}" - else="${eclipse.home}"> - <isset property="baseLocation"/> - </condition> - <delete dir="${javadoc.link.location}" /> - </target> - - <target name="computeClasspath" unless="javadoc.classpath"> - <!-- Construct the javadoc classpath and store it in a property. --> - <echo level="info" message="Computing classpath ..."/> - - <!-- Add platform dependencies required by your plug-in here. - Note that this pattern expects Eclipse to have - been installed into the platform directory structure, as is - the case during the build. --> - <patternset id="platform.classpath.pattern"> - <include name="**/org.eclipse.core*.jar"/> - <include name="**/org.eclipse.core*/**/*.jar"/> - <include name="**/org.eclipse.ui*.jar"/> - <include name="**/org.eclipse.ui*/**/*.jar"/> - <include name="**/org.eclipse.osgi*.jar"/> - <include name="**/org.eclipse.osgi*/**/*.jar"/> - <include name="**/org.eclipse.equinox*.jar"/> - <include name="**/org.eclipse.equinox*/**/*.jar"/> - <include name="**/org.eclipse.jface*.jar"/> - <include name="**/org.eclipse.jface*/**/*.jar"/> - <include name="**/org.junit*.jar"/> - <include name="**/org.junit*/**/*.jar"/> - <include name="**/com.ibm.icu*.jar"/> - </patternset> - - <pathconvert property="javadoc.classpath"> - <path> - <fileset dir="${safeBaseLocation}"> - <patternset refid="platform.classpath.pattern"/> - </fileset> - </path> - </pathconvert> - <echo level="info" message="Done computing classpath."/> - <echo level="debug" message="Bootclasspath is: ${bootclasspath}"/> - <echo level="debug" message="Classpath is: ${javadoc.classpath}"/> - </target> - - <target name="extractLinks"> - <mkdir dir="${javadoc.link.location}"/> - - <patternset id="package.list"> - <include name="**/package-list"/> - </patternset> - - <!-- We only need the package-list files out of these --> - <unzip dest="${javadoc.link.location}/platform/"> - <patternset refid="package.list"/> - <fileset dir="${safeBaseLocation}/plugins"> - <include name="org.eclipse.platform.doc.isv*.jar"/> - </fileset> - </unzip> - </target> - - <target name="all" depends="init" unless="index.present"> - <antcall target="convertSchemaToHtml" /> - <antcall target="generateJavadoc" /> - <antcall target="build.index" /> - </target> - - <target name="build.index" description="Builds search index for the plug-in: org.eclipse.dstore.doc.isv" if="eclipse.running"> - <help.buildHelpIndex manifest="${basedir}/plugin.xml" destination="${basedir}" /> - </target> - - <target name="convertSchemaToHtml" if="eclipse.running"> - <property name="dest" value="reference/extension-points" /> - <!-- - <record name="${basedir}/temp.convert.txt" action="start" /> - <pde.convertSchemaToHTML manifest="../org.eclipse.dstore.core/plugin.xml" destination="${dest}" /> - <record name="${basedir}/temp.convert.txt" action="stop" /> - --> - </target> - - <target name="getJavadocPath"> - <available file="${java.home}/../bin/javadoc.exe" property="javadoc" value="${java.home}/../bin/javadoc.exe" /> - <available file="${java.home}/../bin/javadoc" property="javadoc" value="${java.home}/../bin/javadoc" /> - <available file="/usr/bin/javadoc" property="javadoc" value="/usr/bin/javadoc" /> - </target> - - <target name="generateJavadoc" depends="getJavadocPath,extractLinks,computeClasspath" if="javadoc"> - <property name="optionsFile" value="temp.options.txt" /> - <copy file="options.txt" tofile="${optionsFile}" overwrite="true" /> - - <condition property="argsListDelimiter" value=":"> - <os family="unix" /> - </condition> - <condition property="argsListDelimiter" value=";"> - <os family="windows" /> - </condition> - - <replaceregexp file="${basedir}/${optionsFile}" flags="g" match="(\r\n?|\n);" replace="${argsListDelimiter}" /> - <replace file="${basedir}/${optionsFile}" token="@rt@" value="${bootclasspath}${argsListDelimiter}${javadoc.classpath}" /> - <replace file="${basedir}/${optionsFile}" token="@baseLocation@" value="${safeBaseLocation}" /> - <replace file="${basedir}/${optionsFile}" token="@javadoc.link.location@" value="${javadoc.link.location}" /> - - <!--scrub isv plugin directories of any preexisting api doc content--> - <delete dir="reference/api" /> - <mkdir dir="reference/api" /> - - <echo message="sep = ${argsListDelimiter}"/> - <echo message="javadoc = ${javadoc}"/> - <exec dir="." executable="${javadoc}" output="temp.bin.log"> - <arg line="@${basedir}/${optionsFile} -J-Xmx1000M" /> - </exec> - </target> - -</project> - - - - - - - - - - - - - - diff --git a/rse/doc/org.eclipse.dstore.doc.isv/customBuildCallbacks.xml b/rse/doc/org.eclipse.dstore.doc.isv/customBuildCallbacks.xml deleted file mode 100644 index e457715e4..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/customBuildCallbacks.xml +++ /dev/null @@ -1,157 +0,0 @@ -<!-- ===================================================================== --> -<!-- Custom targets called from a project's generated build.xml --> -<!-- Set customBuildCallbacks=<path/to/this/file> in your build.properties.--> -<!-- ===================================================================== --> -<project name="Build specific targets and properties" default="noDefault"> - - <!-- ===================================================================== --> - <!-- Default target --> - <!-- ===================================================================== --> - <target name="noDefault"> - <echo message="This file must be called with explicit targets" /> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the target build.jars --> - <!-- Available parameters : --> - <!-- build.result.folder - folder to contain the build results --> - <!-- ===================================================================== --> - <target name="pre.build.jars"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target build.jars --> - <!-- Available parameters : --> - <!-- build.result.folder - folder to contain the build results --> - <!-- ===================================================================== --> - <target name="post.build.jars"> - <ant antfile="buildDoc.xml" /> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the target build.sources --> - <!-- Available parameters : --> - <!-- build.result.folder - folder to contain the build results --> - <!-- ===================================================================== --> - <target name="pre.build.sources"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target build.sources --> - <!-- Available parameters : --> - <!-- build.result.folder - folder to contain the build results --> - <!-- ===================================================================== --> - <target name="post.build.sources"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the compilation target <name> --> - <!-- Substitute "name" with the name of the compilation target, eg @dot --> - <!-- Available parameters : --> - <!-- source.foldern : n = 1 ... N, the source folders --> - <!-- target.folder : where the results of the compilation go --> - <!-- <name>.classpath : name = name of the compilation target. A --> - <!-- reference to the classpath structure. --> - <!-- ===================================================================== --> - <!-- - <target name="pre.compileTarget.jar"> - </target> - --> - - <!-- ===================================================================== --> - <!-- Steps to do after compilation but before jaring --> - <!-- Substitute "name" with the name of the compilation target, eg @dot --> - <!-- Available parameters : --> - <!-- source.foldern : n = 1 ... N, the source folders --> - <!-- target.folder : where the results of the compilation go --> - <!-- <name>.classpath : name = name of the compilation target. A --> - <!-- reference to the classpath structure. --> - <!-- ===================================================================== --> - <!-- - <target name="post.compile.compileTarget.jar"> - </target> - --> - - <!-- ===================================================================== --> - <!-- Steps to do after the compilation target <name> --> - <!-- Substitute "name" with the name of the compilation target, eg @dot --> - <!-- Available parameters : --> - <!-- jar.location - the location of the compilation results --> - <!-- <name>.classpath : name = name of the compilation target. A --> - <!-- reference to the classpath structure. --> - <!-- ===================================================================== --> - <!-- - <target name="post.compileTarget.jar"> - </target> - --> - - <!-- ===================================================================== --> - <!-- Steps to do before the target gather.bin.parts --> - <!-- Available parameters : --> - <!-- base.dir - root of the project --> - <!-- build.result.folder - folder containing the build results --> - <!-- target.folder - destination folder --> - <!-- ===================================================================== --> - <target name="pre.gather.bin.parts"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target gather.bin.parts --> - <!-- Available parameters : --> - <!-- base.dir - root of the project --> - <!-- build.result.folder - folder containing the build results --> - <!-- target.folder - destination folder --> - <!-- ===================================================================== --> - <target name="post.gather.bin.parts"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the target gather.sources --> - <!-- Available parameters : --> - <!-- destination.temp.folder - destination folder --> - <!-- ===================================================================== --> - <target name="pre.gather.sources"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target gather.sources --> - <!-- Available parameters : --> - <!-- destination.temp.folder - destination folder --> - <!-- ===================================================================== --> - <target name="post.gather.sources"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the target gather.logs --> - <!-- Available parameters : --> - <!-- destination.temp.folder - destination folder --> - <!-- ===================================================================== --> - <target name="pre.gather.logs"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target gather.logs --> - <!-- Available parameters : --> - <!-- destination.temp.folder - destination folder --> - <!-- ===================================================================== --> - <target name="post.gather.logs"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the target clean --> - <!-- Available parameters : --> - <!-- destination.temp.folder - destination folder --> - <!-- ===================================================================== --> - <target name="pre.clean"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target clean --> - <!-- Available parameters : --> - <!-- plugin.destination - final destination of the build --> - <!-- build.result.folder - results of the compilation --> - <!-- temp.folder - temporary folder --> - <!-- ===================================================================== --> - <target name="post.clean"> - </target> -</project>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/Artifacts.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/Artifacts.html deleted file mode 100755 index 3b35774b0..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/Artifacts.html +++ /dev/null @@ -1,64 +0,0 @@ -<!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 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > -<title>RSE Artifacts</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body> -<h1>DataStore Artifacts</h1> -<p>With the DataStore, you interface the following artifacts:</p> -<ul> -<li><A href="#clientconnection">Client Connection</A></li> -<li><A href="#datastore">DataStore</A></li> -<li><A href="#dataelement">DataElement</A></li> -<li><A href="#miner">Miner</A></li> -</ul> -<p>All the classes and interfaces mentioned here are defined in the <samp>org.eclipse.dstore.core</samp> plugin. - -<h2><A name="clientconnection">Client Connection</A></h2> -<p> -The <b>ClientConnection</b> class is used for establishing a DataStore connection. This class provides the -means to instantiate a client DataStore and connect to a server DataStore on a specified host running under a -specified port. The connection to the server DataStore may either be made directly or a startup -negotiation may be made with a remote daemon before connecting to the server. This class also provides the means -for disconnecting from the DataStore. -</p> - -<h2><A name="datastore">DataStore</A></h2> -<p> -The <b>DataStore</b> class is the heart of the DataStore communications framework. An instance of a DataStore contains a tree -of <a href="#dataelement">DataElements</a>. This tree can be referred to as the <i>DataStore repository</i> because -it consists of all the schema information and data content used. Any type of object or relationship defined, command definition or -piece of data that needs to be communicated between the client and server are stored in the <i>DataStore repository</i>. -The DataStore class can be used for finding, creating and deleting DataElements and for communicating commands -to <a href="#miner">miner</a>. The DataStore class encapsulates all remote synchronizations between the client and the -server via its <code>command</code> and <code>refresh</code> APIs. -</p> - -<h2><A name="dataelement">DataElement</A></h2> -<p> -The <b>DataElement</b> is the unit of information in a DataStore repository. Each DataElement has a set of attributes that describe -the object it represents and is related to other DataElements by containing other DataElements. DataElements represent both the meaning -of data as well as the data itself. -</p> -<p> -For more information about DataElements, see the section, <a href="DataElements.html">DataElements and the DataStore model</a>. -</p> - -<h2><A name="miner">Miner</A></h2> -<p> -A <b>Miner</b> is an extension point to the DataStore. Miners are classes, residing on the server-side, that implement a common -interface used by the DataStore for communication information between the DataStore and the tools. -</p> -<p> -For more information about Miners, see the section, <a href="Miners.html">Miners</a>. -</p> -</body> -</html> - - - diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/ClientSide.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/ClientSide.html deleted file mode 100755 index c2fb661a7..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/ClientSide.html +++ /dev/null @@ -1,171 +0,0 @@ -<!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 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > -<title>Tutorials</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body bgcolor="#ffffff"> -<h1>Communicating with the Server-side</h1> - -<h2>Connecting to a Local DataStore</h2> -<p> -If you're writing an RSE subsystem to connect to a local standalone DataStore, the following needs -to be done during the connect: -</p> - -<font color='#4444CC'> -<pre> - ... - ClientConnection clientConnection = new ClientConnection(connectionName); - - // initialize the local datastore - clientConnection.localConnect(); - - DataStore dataStore = clientConnection.getDataStore(); - - // specify miners to load - dataStore.addMinersLocation("."); // initializes the default miners - - // initialize miners - dataStore.getSchema(); - dataStore.initMiners(); - ... - -</pre> -</font> - -<h2>Connecting to a Remote DataStore</h2> -<p> -If you're writing an RSE subsystem to connect to a remote DataStore, the only difference -from the local scenario is that <code>connect</code> is called rather than <code>localConnect</code>. -</p> - -<font color='#4444CC'> -<pre> - ... - ClientConnection clientConnection = new ClientConnection(connectionName); - - // prepare connection - clientConnection.setHost(hostName); - clientConnection.setPort(port); - - // connect - clientConnection.connect(ticket); - - DataStore dataStore = clientConnection.getDataStore(); - - // specify miners to load - dataStore.addMinersLocation("."); // initializes the default miners - - // initialize miners - dataStore.getSchema(); - dataStore.initMiners(); - ... - -</pre> -</font> - -<h2>Loading an Additional DataStore Miner</h2> -<p> -If the new miner has been registered via the default minerFile.dat file, then -no further steps are required to load it. Otherwise, after the subsystem is -connected to the remote DataStore, you need to tell the DataStore to load the -miner as follows. -</p> - -<font color='#4444CC'> -<pre> - ... - dataStore.addMinersLocation(location); - dataStore.getSchema(); - ... -</pre> -</font> - -<p> -This tells the host DataStore to instantiate and initialize all miners listed in -the specified minerFile.dat file. -</p> - - -<h2>Sending Commands to a Miner</h2> -<p> -To send a command to a miner, the required <a href="DataElements.html#commanddescriptor">command descriptor</a> must first be obtained -using the method <code>DataStore.localDescriptorQuery</code>. The method <code>DataStore.command</code> is then called with command -descriptor and the subject of the command. For example, a query might need to be called on the miner as shown in the following code segment. -</p> - -<font color='#4444CC'> -<pre> - ... - // the UI model object - MyRemoteObject obj = getMyRemoteObject(); - - // get the corresponding DataElement for this object - DataElement deObj = obj.getDataElement(); - - // get the DataStore from the DataElement - DataStore ds = deObj.getDataStore(); - - // get the query command descriptor for the subject - DataElement queryCmd = ds.localDescriptorQuery(deObj.getDescriptor(), "MY_QUERY_COMMAND"); - - // send the command - DataElement status = ds.command(queryCmd, deObj, true); - ... -</pre> -</font> - -<h2>Receiving Data from a Miner</h2> -<p> -After a command is sent to a miner, you might want to receive information that the miner produced in response to the command. -DataStore commands and responses are sent asynchronously, much like events. On the server, the -<a href="Communications.html#servercommandhandler">Server Command Handler</a> reacts to incoming commands by calling the <code>handleCommand</code> -method on the appropriate miner. For the client, the <a href="Communications.html#clientcommandhandler">Client Command Handler</a> -reacts to incoming responses by firing domain notifications. In order to receive miner responses, asynchronously, -you need to implement a DataStore domain listener. -</p> -<p> -A domain listener implements the IDomainListener interface. An instance of an IDomainListener needs to be added to the DataStore domain listener -list. The following is what a simple domain listener looks like: -</p> - -<font color='#4444CC'> -<pre> - public class MyDomainListener implements IDomainListener - { - public boolean listeningTo(DomainEvent e) - { - // check if we care about this event - ... - } - - public void domainChanged(DomainEvent e) - { - // get the data from this event - ... - } - } -</pre> -</font> - -<p> -A domain listener may either listen for the duration of a DataStore session or may be transient, to be used for -a receiving data from a particular command. For example, after calling <code>DataStore.command</code>, which returns -the status of the command instance, a listener can be added as follows: -</p> -<font color='#4444CC'> -<pre> - ... - MyDomainListener listener = new MyDomainListener(shell); - `ds.getDomainNotifier().addDomainListener(listener); - listener.setStatus(status); - ... -</pre> -</font> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/Communications.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/Communications.html deleted file mode 100755 index 3cad8e804..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/Communications.html +++ /dev/null @@ -1,159 +0,0 @@ -<!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 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > -<title>RSE Model</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body> -<h1>DataStore Communications</h1> -<p> -Communication in the DataStore is asynchronous and symmetric. Commands sent and results received are all represented in the same form, -<a href="DataElements.html">DataElements</a> and the underlying means of transmitting this information is basically the same for each. -When a command is issued, it gets queued and then later routed to the appropriate <b>miner</b> where it gets executed. -A miner returns results by updating the DataStore repository with information. Like commands, these -results are queued and then later notifications are sent out to any listener that requires the results. -</p> -<p> -The asynchronous routing of data and commands between a client and the tools is made possible by threads, called <i>handlers</i>. There are two -types of handlers - a <a href="#commandhandlers">Command Handler</a> and an <a href="#updatehandlers">Update Handler</a>. Each handler thread contains a queue -of data that needs to be transmitted and each periodically communicates the data contained in it's queue. -</p> - -<h2><a name="commandhandlers">Command Handlers</a></h2> -<p> -The job of the Command Handler is to route commands to the miners. There are two types of command handlers. -</p> - -<h3><a name="clientcommandhandler">Client Command Handler</a></h3> -<p> -The <b>Client Command Handler</b> is a command handler responsible for transmitting its queue of DataStore commands across a network to -the server DataStore. This handler encapsulates the communication of DataStore client data to a DataStore server. The Client Command Handler -interfaces the DataStore communication layer, where its queue of commands gets serialized into XML before being sent over a TCP/IP socket -to the server. -</p> - -<h3><a name="servercommandhandler">Server Command Handler</a></h3> -The <b>Server Command Handler</b> is a command handler responsible for directly routing the DataStore commands in its queue to the appropriate -miner(s) depending on the command. - -<h2><a name="updatehandlers">Update Handlers</a></h2> -<p> -The job of the Update Handler is to notify the client that some results have been received or changed. There are two types of -update handlers. -</p> - -<h3><a name="clientupdatehandler">Client Update Handler</a></h3> -<p> -The <b>Client Update Handler</b> is an update handler responsible for sending out domain notifications for each unit of data -contained in its queue. -</p> - -<h3><a name="serverupdatehandler">Server Update Handler</a></h3> -<p> -The <b>Server Update Handler</b> is an update handler responsible for transmitting its queue of DataStore objects across a network to -the client DataStore. This handler encapsulates the communication of DataStore server data to a DataStore client. The Server Update Handler -interfaces the DataStore communication layer, where its queue of data gets serialized into XML before being sent over a TCP/IP socket -to the client. -</p> - -<p> -Communication between a client and tools may either occur locally and remotely depending on how the -user chooses to connect to the DataStore. The client interface and the server tooling are the same regardless of -whether the DataStore is standalone or client/server based. The communication differences are encapsulated by -the DataStore handlers. -</p> - -<h2>Standalone Local DataStore</h2> -<p> -Locally, the DataStore may be used standalone such that all communication through the DataStore goes directly to between the <b>miners</b> -and the client, all running within the same process. In this case, there is only a single DataStore and no communication goes -over the network. For its handlers, the local DataStore uses a <b>Client Update Handler</b> and a <b>Server Command Handler</b>. -</p> - -<img src="images/local.jpg" alt="Local DataStore Eclipse" border="0"> - -<p> -In the above dialog, the path of commands to the tools is shown with solid lines, while the path of data to client is shown with dotted lines. - -<ol> -<li> -In RSE, a subsystem calls a DataStore command API to issue a command. -</li> -<li> -The command is then queued in the <b>Server Command Handler</b>. -</li> -<li> -The Server Command Handler gets the command from the queue, determines which miner should run it, and passes the command into that miner. -</li> -<li>The miner then executes the command and produces results by calling DataStore object creation methods. When the resulting objects are created, -the DataStore queues them in the <b>Client Update Handler</b>. -</li> -<li> -The Client Update Handler gets the data from the queue and sends out a domain notification for each data object in the queue. -</li> -<li> -A domain listener for the RSE subsystem receives the notification and then uses the result data to update the UI. -</li> -</ol> -</p> - -<h2>Client/Server DataStore</h2> -<p> -In the remote case, a DataStore client is part of the Eclipse process, while the DataStore server is run -in a separate process on a remote host. Information is transferred between the two DataStore repositories over -a TCP/IP socket. Any data that is created or changed on either the client or the server is asynchronously -propagated over to the other side via serialization/deserialization of the delta. - -Like in the standalone case, the client DataStore uses a <b>Client Update Handler</b>, but instead of using -a Server Command Handler it uses a <b>Client Command Handler</b>. The server DataStore uses a <b>Server Update Handler</b> -and a <b>Server Command Handler</b>. -</p> - -<img src="images/remote.jpg" alt="Remote DataStore Eclipse" border="0"> - -<ol> -<li> -In RSE, a subsystem calls a DataStore command API to issue a command. -</li> -<li> -The command is then queued in the <b>Client Comamnd Handler</b>. -</li> -<li> -The Client Command Handler gets the command from the queue and, via the communication layer, transmits it to the server DataStore. -The communication layer on the client serializes the DataStore respository objects that make up the command and sends that -serialization over a socket to the server. -</li> -<li> -The communication layer on the server deserializes the socket data and creates DataStore objects in the DataStore repository. -Those command objects are added it to the <b>Server Command Handler</b> queue. -</li> -<li> -The Server Command Handler gets the command from the queue, determines which miner should run it, and passes the command into that miner. -</li> -<li> -The miner then executes the command and produces results by calling DataStore object creation methods. When the resulting objects are created, -the DataStore queues them in the <b>Server Update Handler</b>. -</li> -<li> -The Server Update Handler gets the results from the queue and transmits them, via the DataStore communicate layer, to the client DataStore. -The communication layer on the server serializes the DataStore objects from the queue and sends that serialization over a socket -to the client. -</li> -<li> -The communication layer on the client deserializes the socket data and creates DataStore objects in the DataStore respository. -Those results are added to the <b>Client Update Handler</b> queue. -</li> -<li> -The Client Update Handler gets the data from the queue and sends out a domain notification for each data object in the queue. -</li> -<li> -A domain listener for the RSE subsystem receives the notification and then uses the result data to update the UI. -</li> -</ol> -</p> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/DataElements.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/DataElements.html deleted file mode 100755 index 50eb1468e..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/DataElements.html +++ /dev/null @@ -1,206 +0,0 @@ -<!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 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > -<title>RSE Model</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body> -<h1><a name="dataelements">DataElements</a></h1> -<p> -All information in the DataStore repository is stored in the form of <b>DataElements</b>. DataElements are objects -that have attributes and may contain other DataElements. The attributes of a DataElement are stored as an array of -strings. A particular attribute is retrieved by calling <code>getAttribute(</code><i>attribute index</i><code>)</code>. -A particular attribute is set by calling <code>setAttribute(</code><i>attribute index</i><code>, </code><i>attribute value</i><code>)</code>. -The attribute indices that can be used are as follows: -<table> -<tr><td><b>Attribute</b></td><td><b>Description</b></td></tr> -<tr><td><code>A_TYPE</code></td><td>Attribute indicating the type of object. The type can be used to indicate the type of an instance of data, a descriptor, a relationship or a commnad.</td></tr> -<tr><td><code>A_NAME</code></td><td>Attribute indicating the name of object.</td></tr> -<tr><td><code>A_VALUE</code></td><td>Attribute indicating the more information about that object</td></tr> -<tr><td><code>A_SOURCE</code></td><td>Attribute indicating source information about an object, if applicable</td></tr> -<tr><td><code>A_REF_TYPE</code></td><td>Attribute indicating whether the object is a normal object ("value"), a spirit ("spirit"), or a reference to another DataElement ("reference"). In the DataStore, a reference to another DataElement is represented with a DataElement. For more information on spirit elements, see <a href="MemoryManagement.html">Memory Management in DataStore</a> </td></tr> -<tr><td><code>A_ID</code></td><td>The unique ID of a DataElement.</td></tr>. -</table> -</p> -<p> -Rather than representing different types of objects as different classes, the type attribute of a DataElement -indicates its type. There are two general categories of DataElements. There are schema elements, <A href="#descriptors">descriptors</a>, and instances of -those schema elements, <a href="#instances">instances</a>. -</p> - -<h2><a name="descriptors">Descriptors</a></h2> -<p> -A descriptor is a DataElement that describes some type of object. The <code>A_TYPE</code> attribute of a descriptor indicates what type of -descriptor it is. The <code>A_NAME</code> attribute of a descriptor identifies the type that the descriptor describes. -</p> -<p> -A descriptor may be of one of the following types: -</p> -<table> -<tr><td><code>T_OBJECT_DESCRIPTOR</code></td><td>Describes a type of object</td></tr> -<tr><td><code>T_RELATION_DESCRIPTOR</code></td><td>Describes a type of relationship that may exist between two DataElements.</td></tr> -<tr><td><code>T_COMMAND_DESCRIPTOR</code></td><td>Describes a type of command</td></tr> -</table> - -<h3><a name="objectdescriptors">Object Descriptors</a></h3> -<p> -<b>Object descriptors</b> describe the different types of data that can be represented in the DataStore repository. Object descriptors -can describe types of object instances as well as other types of object descriptors. Each object descriptor is related to other object, -relationship and command descriptors. -</p> - -<h3><a name="relationdescriptors">Relation Descriptors</a></h3> -<p> -<b>Relation descriptors</b> describe the different types of relationships that can be represented in the DataStore repository. Relation -descriptors describe types of relationships between object instances, object descriptors, command instances and command descriptors. -</p> - -<h3><a name="commanddescriptors">Command Descriptors</a></h3> -<p> -<b>Command descriptors</b> describe the different types of commands that can be executed on an object in the DataStore repository. -In the DataStore schema, object descriptors are related to command descriptors to indicate that an object instance of a certain type can -have the described command run on it. Command descriptors are always contained by the object descriptors they are associated with. The -<code>A_SOURCE</code> attribute of a command descriptor indicates which miner(s) may execute an instance of such a command. -</p> - -<p> -These three types of objects are used to define the DataStore schema. Instances of relation descriptors are used to define -relationships between descriptors in the schema. -</p> - - -<h2><a name="instances">Instances</a></h2> -<p> -An instance object is a DataElement that is an instance of a descriptor. An instance may either by an object, a -relation or a command. An instance uses its descriptor's <code>A_NAME</code> attribute as its <code>A_TYPE</code> attribute. -</p> - -<h3><a name="objects">Objects</a></h3> -<p> -<b>Objects</b> are instances of <b>object descriptors</b>. Objects are used to the represent the external or internal -entities that are being interacted with. An instance object can be related in a certain way to another type of -instance object if its object descriptor has the same kind of relationship to the other object's object descriptor. -An instance object may be associated with a particular command if its object descriptor is associated with the command descriptor -for that command. -</p> - -<h3><a name="relations">Relations</a></h3> -<p> -<b>Relations</b> are instances of <b>relation descriptors</b>. A relation is really a typed reference to another object. Relations -may exist from one object to another if the schema indicates that the object descriptor for the first object may have a relationship -of that type to the other object's descriptor. Relations are used to describe the relationship between two instances, the -relationship between two descriptors and the relationship between an instance and a descriptor. A relation is able to reference -another element by storing the other element's <code>A_ID</code> attribute in its <code>A_SOURCE</code> attribute. If a relation object -needs to be dereferenced, it uses this attribute to query the DataStore for the object being referenced. -</p> -<p> -A relation is typically represented by having an instance object DataElement contain a relation DataElement. -There are two types of relationships between elements that are implicit. These are the <i>contains</i> and -the <i>parent of</i> relationships. If an element is directly contained within another element, the -relationship between those two elements is implied to be <i>contains/parent of</i> relationships. -</p> - -<h3><a name="commands">Commands</a></h3> -<p> -<b>Commands</b> are instances of <b>command descriptors</b>. A command is always associated with an instance object such that -the command is to be performed on that object. The object associated with a command is referred to as the <i>subject</i> of -the command. Only a command that has a command descriptor that is related to the object descriptor of the subject may be -constructed. A command object is constructed when the DataStore method <code>command()</code> is called. The command is -created with a reference to the subject, an optional set of arguments, also instance objects, and a status object instance, used -to indicate the state of the command. The tree of elements for a command is communicated, via the DataStore comm layer, to -the appropriate miner(s), where it is interpreted and executed. -</p> -<p> -The structure of a command looks like the following: -</p> -<ul> -<li>Command - <ul> - <li>subject - a reference to the instance that this command applies to</li> - <li>arg 1 - an optional argument represented as a DataElement</li> - <li>...</li> - <li>arg n - an optional argument represented as a DataElement</li> - <li>status - element that represents the current status of a command</li> - </ul> -</li> -</ul> - -<p> -As an example, suppose the DataStore is being used for browsing a filesystem. The filesystem entities and how to interact -with the filesystem needs to be defined in the schema. The following descriptors could be used to describe this. -</p> - -<ul> -<li>Object Descriptors - <ul> - <li>"generic file object" - describes a generic file system object</li> - <li>"file" - describes a file object</li> - <li>"folder" - describes a folder object</li> - </ul> -</li> -<li>Relation Descriptors - <ul> - <li>"contains" - represents the containment relationship between two objects</li> - <li>"abstracts" - represents a derives relationship between two object descriptors</li> - <li>"abstracted by" - represents an inherits relationship between two object descriptors</li> - </ul> -</li> -<li>Command Descriptors - <ul> - <li>"query" - a command to list the contents of a folder</li> - <li>"rename" - a command to rename a file or folder</li> - <li>"delete" - a command to delete a file or folder</li> - <li>"create" - a command to create a new file or folder from an existing folder</li> - </ul> -</li> -</ul> - -<p> -Now that all the required descriptors are defined, relations between descriptors are needed. Note that the -symbol "->" implies a "contains" relationship and "IO()" implies an instance of a specified descriptor. -</p> - -<ul> -<li>"generic file object" - <ul> - <li>->"rename"</li> - <li>->"delete"</li> - <li>->IO("abstracts")->"folder"</li> - <li>->IO("abstracts")->"file"</li> - </ul> -</li> -<li>"folder" - <ul> - <li>->"create"</li> - <li>->"query"</li> - <li>->IO("abstracted by")->"generic file object"</li> - <li>->IO("contains")->"generic file object"</li> - </ul> -</li> -<li>"file" - <ul> - <li>->IO("abstracted by")->"generic file object"</li> - </ul> -</li> -</ul> - -<p> -DataStore schemas are created by the DataStore <b>miners</b>. Each tool contributes it's -own schema to the DataStore schema, referencing descriptors of other schemas, such -that one tool can contribute to another tool. All the command descriptors that are -contributed by a miner are expected to be handled by the contributing miner. Whenever -a miner creates a new command descriptor, the <code>A_SOURCE</code> attribute indicates -to the DataStore that an instance of that command should be routed to that miner when -it's issued. -<p> - -<p> -See the section, <a href="Miners.html">Miners</a> to find out how miners contribute schemas -and execute commands. -</p> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/Extending.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/Extending.html deleted file mode 100755 index a136e4b6d..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/Extending.html +++ /dev/null @@ -1,18 +0,0 @@ -<!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 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > -<title>Tutorials</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body bgcolor="#ffffff"> -<h1>Extending and Using the DataStore</h1> -<p> -This section describes the basic steps required for extending the server DataStore with -a DataStore miner and how to interact with the miners from an RSE subsystem. -</p> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/MemoryManagement.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/MemoryManagement.html deleted file mode 100644 index 3d4874181..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/MemoryManagement.html +++ /dev/null @@ -1,68 +0,0 @@ -<!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 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > -<title>RSE DataStore Memory Management</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body> -<h1><a name="dataelements">Memory Management in DataStore</a></h1> -<p> -Since RSE version 7.0 a substantial design change has been made to the DataStore that significantly reduces the memory footprint of the -DataElements in high-use, long up-time situations. A problem that was identified was that in the DataStore, DataElements were -rarely being destroyed - only when the files they represented were themselves deleted. When directories in the file system were explored, -DataElements were being created to represent the files in the directories, but these DataElements were cached and never -removed from the cache. Therefore, the number of DataElements in the DataStore was always increasing. With no opportunity -to clear the cache or remove elements, the memory usage of the server continued to grow boundlessly. -</p> -<h2><a name="spirit">A solution - Spirit DataElements</a></h2> -<p> -The solution to the problem of an ever-growing set of DataElements was simple - provide a mechanism of removing "old" -DataElements and thus shrinking the set. Since server memory real-estate comes at a much higher premium, the focus here -is on server-side memory reduction. The assumption then, is that DataElements in the DataStore will always remain in -memory on the client, but that in the mirror-image DataStore that resides on the server, DataElements can be removed. -</p> -<p> -Formerly, the RSE ran under the assumption that the client and server DataStores mirrored each other. The new -implementation has a server DataStore tree that is only a subset of all the elements in the client tree (because -some elements get removed.) In order to accommodate this, a new boolean member variable was added to the DataElement -class called "isSpirit". When this variable is set to true it means different things on the client and server. On the -server, a "spirit" DataElement means the element is treated in much the same way as a "deleted" element. At the first -opportunity, the element is purged from the DataStore and garbage collected by the JVM - freeing up memory. On the client, -a "spirit" element means that that particular DataElement's counterpart has been made a spirit; thus the client "knows" -that its twin element on the server side has either been deleted, or is about to be deleted. -</p> -<h2><a name="disconnecting">Disconnecting "old" DataElements:</a></h2> -<p> -How is it determined when to mark a given DataElement as a spirit? It was decided that the decision to this would be -left to clients of the DataStore (the miners), rather than to the DataStore itself. This was done for the purposes of -granularity: some individual miners may not want DataElements to be ever purged, some might want only specific elements, -etc. As an example, the UniversalFileSystemMiner employs the FileClassifier to classify files returned from a directory -query, and after each file has been classified, the DataStore's disconnectObject() method is called on the DataElement -representing that file, setting the stage for its becoming a spirit. -</p> -<h2><a name="queue">Controlling the queue of DataElements:</a></h2> -<p> -A new class, the DataElementRemover, running in its own thread, maintains a queue of objects that were passed into -DataStore's disconnectObject() method; each object is stored in the queue along with the time it was added. The -DataElementRemover is configurable by two command-line options: -DSPIRIT_EXPIRY_TIME=x and -DSPIRIT_INTERVAL_TIME=y; -where x and y are integers representing a number of seconds. Every y seconds, the queue checks its elements and "makes -spirit" all those that are older than x seconds. The DataElement is then refreshed, and the change propagated to the -client. On the server side, the DataElement is deleted at the first opportunity. -</p> -<h2><a name="feature">Turning on the feature:</a></h2> -<p> -On the client side, this feature is always "on". It is the server which is configured to do or not to do the spirit -DataElement behaviour. This way, backwards compatibility is maintained - if a new client connects to an old server, or a -server with spirit turned off, the client detects this and operates as before. If an old client connects to a new server -with spirit turned on, the server detects that the client does not have spirit capability and behaves as it did before. -</p> -<p> -To turn on the spirit feature on the server side, one needs to include the command-line option -DDSTORE_SPIRIT_ON=true. -The server scripts have been packaged in order to do this by default. -</p> -</body> -</html> diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/Miners.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/Miners.html deleted file mode 100755 index 525a9d793..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/Miners.html +++ /dev/null @@ -1,142 +0,0 @@ -<!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 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > -<title>RSE Model</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body> -<h1>Miners</h1> -<p> -<b>Miners</b> are remote tooling extensions to the DataStore. Each miner describes the model -that it works with as well as the commands associated with the model that it implements. Each -miner is responsible for extending the DataStore schema and providing implementations for -commands that it defines. -</p> -<p> -All miners are derived from the abstract class <code>Miner</code>. To write a miner, the -following APIs need to be implemented: -</p> -<pre> - public abstract void extendSchema(DataElement schemaRoot); - public abstract DataElement handleCommand(DataElement theCommand); -</pre> -<p> -The first method, <code>extendSchema</code>, is implemented by a miner to contribute the types of objects, relationships and commands that -it deals with. The second method, <code>handleCommand</code>, is implemented by a miner so that it can execute the commands it defines. -</p> - -<h2>Extending the Schema</h2> -<p> -A miner extends the DataStore schema by populating the <i>schemaRoot</i> with <a href="DataElements.html#descriptors">descriptors</a>. -The DataStore repository tree is structured so that there is a single node where schema descriptors reside. All -<a href="DataElements.html#objectdescriptors">object descriptors</a> and <a href="DataElements.html#relationdescriptors">relation descriptors</a> -are created under this schema root. <a href="DataElements.html#commanddescriptors">Command descriptors</a> are created under the -object descriptors that they apply to. Each miner contributes to this global DataStore schema, so each may also extend or leverage the -information from another miner's schema. -</p> -<p> -A miner implements <code>extendSchema(DataElement)</code> to add new descriptors to the DataStore schema. If a miner creates representations -of objects that are not already represented by some other miner's schema, then it needs to define descriptors for those new types of objects. -Sometimes new relationship types also need to be defined by a miner for its particular model. In order for a miner to be interacted with, -via <code>handleCommand</code>, it needs to define command descriptors for object descriptors in the schema. The code below illustrates the -typical structure of an <code>extendSchema</code> implementation: -</p> - -<font color='#4444CC'> -<pre> - public void extendSchema(DataElement schemaRoot) - { - // create object descriptors - DataElement myObjectType1 = createObjectDescriptor(schemaRoot, "my object type 1"); - DataElmeent myObjectType2 = createObjectDescriptor(schemaRoot, "my object type 2"); - DataElement myObjectContainerType = createObjectDescriptor(schemaRoot, "my object container"); - - // create relation descriptors - DataElement myRelationType = createRelationDescriptor(schemaRoot, "my relation type"); - - // create command descriptors - createCommandDescriptor(myObjectType1, "My Command 1", MY_COMMAND_1); - createCommandDescriptor(myObjectType2, "My Command 2", MY_COMMAND_2); - createCommandDescriptor(myObjectContainerType, "Query", MY_QUERY); - - // establish relationships between object types - createReference(myObjectType1, myObjectType2, myRelationType); // myObjectType1 instances can be associated with myObjectType2 instances by myRelationType - createReference(myObjectContainerType, myObjectType1); // myObjectContainerType instances can contain myObjectType1 instances - createReference(myObjectContainerType, myObjectType2); // myObjectContainerType instances can contain myObjectType2 instances - - ... - } -</pre> -</font> - -<p> -The DataStore does not enforce that instance element trees are structured in the manner that the schema describes so the -establishing of relationships between object types, as done in this example, is unnecessary as a miner knows its own -model, since it defined it. But by convention, it is a good thing to describe a model with those relationships explicitly stated -because other miners or client tools may want to leverage or extend the model for their own purposes. -</p> - - -<h2>Handling Commands</h2> -<p> -The <code>handleCommand</code> method is called by the <a href="Communications.html#servercommandhandler">Server Command Handler</a> -if the descriptor for a command instance is associated with a particular miner. When this is called, it is up to the miner implementation -to interpret and execute the command. -</p> -<p> -A <a href="DataElements.html#commands">Command instance</a> is a tree of <a href="DataElements.html">DataElements</a> representing the -command, the subject of the command, additional arguments to the command and the status of the command. The way this is normally interpretted -by a miner to mean <i>perform the specified command on the subject using the specified arguments. Change the status to be "done" when the -operation is complete.</i>. -</p> -<p> -The base miner class provides APIs to assist a miner implementation in extracting information from -a command tree. The method <code>getCommandName(DataElement)</code> is used to extract the -name of the command, <code>getCommandStatus(DataElement)</code> returns the status element of -the command, and <code>getCommandArgument(DataElement, int)</code> returns an argument at the -specified index. The first argument is always the subject. The code below illustrates -the typical structure of a <code>handleCommand</code> implementation. -</p> - -<font color='#4444CC'> -<pre> - public DataElement handleCommand(DataElement theElement) - { - String name = getCommandName(theElement); - DataElement status = getCommandStatus(theElement); - DataElement subject = getCommandArgument(theElement, 0); - - if (name.equals(MY_COMMAND_1)) - { - handleMyCommand1(subject, arg1,...,argn, status); - } - ... - status.setAttribute(DE.A_NAME, "done"); - _dataStore.refresh(status); - } -</pre> -</font> -<p> -The results of a command may be returned in a variety of ways, depending on its -purpose. One thing that is always returned is the status object. -</p> -<p> -Think of the status object as the return value of a method. The status object needs to be set to "done" -whenever a command is complete but it may also optionally contain results in the form -of DataElements. If a command is requesting transient information about something, then -the status object could be populated with the results. -</p> -<p> -Each miner has read and write access to the entire DataStore tree. If desired a miner -can modify that tree as a result of a command. For example, a miner used for browsing -a file system might populate the subject, a folder object, with other folder and file -objects, rather than transiently via the status object. In this way, a miner caches -data and expands the data available to the DataStore repository in response to user -requests. -</p> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/ServerSide.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/ServerSide.html deleted file mode 100755 index 5ec50b7b9..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/ServerSide.html +++ /dev/null @@ -1,36 +0,0 @@ -<!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 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > -<title>Tutorials</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body bgcolor="#ffffff"> -<h1>Extending the Server-side</h1> -<p> -This section describes the basic steps needed to extend the server side tooling using <b>Miners</b>. -</p> -<ol> -<li> -Write a new <a href="Miners.html">DataStore miner</a> by extending the <b>Miner</b> class. -</li> -<li> -Put the compiled miner class on the host, preferably in jar form -</li> -<li> -Register the new miner so that it gets loaded when the server DataStore is connected to. This may be done -by adding the miner's qualified classname to the file <i>minerFile.dat</i>. Alternatively, an additional <i>minerFile.dat</i> -file can be used to supply the classname. -</li> -<li> -Update the classpaths for the server side so that the new miner class can be loaded by the -DataStore. This will vary depending on how the DataStore server is started up. If a startup -script is used, then you could update the classpath specified in the script or the system classpath -could be updated. -</li> -</ol> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/images/arch.jpg b/rse/doc/org.eclipse.dstore.doc.isv/guide/images/arch.jpg Binary files differdeleted file mode 100755 index c52bd9ff9..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/images/arch.jpg +++ /dev/null diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/images/local.jpg b/rse/doc/org.eclipse.dstore.doc.isv/guide/images/local.jpg Binary files differdeleted file mode 100755 index 806c24f43..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/images/local.jpg +++ /dev/null diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/images/remote.jpg b/rse/doc/org.eclipse.dstore.doc.isv/guide/images/remote.jpg Binary files differdeleted file mode 100755 index 0829df309..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/images/remote.jpg +++ /dev/null diff --git a/rse/doc/org.eclipse.dstore.doc.isv/guide/overview.html b/rse/doc/org.eclipse.dstore.doc.isv/guide/overview.html deleted file mode 100755 index 3f2aa1a07..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/guide/overview.html +++ /dev/null @@ -1,67 +0,0 @@ -<!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 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > -<title>Remote System Explorer Overview</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body bgcolor="#ffffff"> -<h1>DataStore Overview</h1> -<p> -The RSE uses the concept of <b>subsystems</b> as a common abstraction for remote tooling. Subsystems provide -public interfaces that are called when some remote tool or resource needs to be communicated with. As long as -the appropriate public interfaces are implemented, the means of communicating with these remote tools and resources -is up to the developer of the subsystem. Whatever that might be, some kind of communication layer is required -to access tools on the host. One such means that is used by existing RSE Subsystems and can be reused is the -DataStore framework. -</p> -<p> -The <b>DataStore</b> communications framework is used to provide remote access and tooling for the Remote Systems Explorer. -It is a communications layer, in-memory data repository and a pluggable tooling framework. While Eclipse provides -the ability for local tools to plug into the Eclipse workbench, DataStore provides the ability to integrate -remote tools into the Remote Systems Explorer. When implementing subsystem APIs, a particular implementation -may provide remote function by leveraging DataStore. -</p> - -<img src="images/arch.jpg" alt="DataStore and it's relationship to RSE and Eclipse" border="0"> - -<p> -In an RSE subsystem, the goal of the DataStore is to provide the bridge to tools and resources on the host. -To interact with a remote tool, a DataStore client communicates over a network with a DataStore server. Data and -commands are transferred between the client and server via the DataStore communication layer. Information -that is communicated between each side is kept in memory with the DataStore repository. Both the client and server DataStores -have this repository and it is the responsibility of the DataStore communication layer to keep the contents -of each of these repositories in sync. All the DataStore data on the server side is replicated to the client and -and vice versa. -</p> -<p> -The DataStore framework is generic in the sense that it can be used to facilitate any kind of remote tooling. There are -no specialized APIs or artifacts that are geered towards a particular use. How DataStore is used is determined by the -tool extensions, <a href="Miners.html">Miners</a>. <a href="Miners.html">Miners</a> are typically either adapters to -tools on the host or are tools themselves. These extensions determine the meaning of data used to represent objects, -relationships and the commands that can be issued on the represented objects. <a href="Miners.html">Miners</a> shape the -DataStore by contributing <a href="Schemas.html">schemas</a> to the pool of information in a DataStore repository. -Because the client and server DataStore repositories are synchronized, the DataStore clients -have access to the miner <a href="Schemas.html">schemas</a> and, using that information, they are able to communicate with the tools on the host. -Because the server has access to those miner <a href="Schemas.html">schemas</a>, each <a href="Miners.html">Miners</a> may also communicate with -other <a href="Miners.html">Miners</a> on the host in the same way a client can. -</p> -<p> -A Filesystem miner can shape the DataStore by contributing a <a href="Schemas.html">schema</a> that -describes file systems and how they should be interacted with. The <a href="Schemas.html">schema</a> could describe -files, folders, properties of files and relationships between them as well as commands for querying folders or renaming files. -An RSE subsystem, can then provide browsing capabilities to a remote file system by sending commands -via the DataStore client to the Filesystem Miner on the host. Another <a href="Miners.html">miner</a> can -contribute its own <a href="Schemas.html">schema</a> or extend the existing Filesystem Miner <a href="Schemas.html">schema</a> -to leverage or contribute to the existing file system tool. -</p> -<p> -This guide explains all underlying -artifacts and model of the DataStore, its relationship to RSE, and highlights the -important APIs available for your use. -</p> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/notices.html b/rse/doc/org.eclipse.dstore.doc.isv/notices.html deleted file mode 100755 index 6c70b9c62..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/notices.html +++ /dev/null @@ -1,22 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 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">
- <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
- <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2006.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/options.txt b/rse/doc/org.eclipse.dstore.doc.isv/options.txt deleted file mode 100755 index fcb8f7dbd..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/options.txt +++ /dev/null @@ -1,25 +0,0 @@ --charset "iso-8859-1" --sourcepath "../org.eclipse.dstore.core/src -;../org.eclipse.dstore.extra/src" --d reference/api --classpath @rt@ --breakiterator --use --splitIndex --windowtitle "Remote System Explorer DataStore API Specification" --doctitle "Remote System Explorer DataStore API Specification" --header "<b>Remote System Explorer DataStore</b><br>Release 1.0" --bottom '<font size="-1"><p><a href="{@docRoot}/../misc/api-usage-rules.html">Guidelines for using DataStore APIs</a>.</p></font>' --link http://java.sun.com/j2se/1.4.2/docs/api --linkoffline ./../../../org.eclipse.platform.doc.isv/reference/api @javadoc.link.location@/platform/reference/api/ --link http://bundles.osgi.org/javadoc/r4 - -org.eclipse.dstore.core -org.eclipse.dstore.core.client -org.eclipse.dstore.core.java -org.eclipse.dstore.core.miners.miner -org.eclipse.dstore.core.model -org.eclipse.dstore.core.server -org.eclipse.dstore.core.util -org.eclipse.dstore.core.util.ssl -org.eclipse.dstore.extra
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/plugin.properties b/rse/doc/org.eclipse.dstore.doc.isv/plugin.properties deleted file mode 100755 index b9113ccc8..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/plugin.properties +++ /dev/null @@ -1,14 +0,0 @@ -############################################################################### -# Copyright (c) 2000, 2006 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### - -# NLS_MESSAGEFORMAT_VAR -pluginName=RSE DStore ISV Documentation -providerName=Eclipse.org diff --git a/rse/doc/org.eclipse.dstore.doc.isv/plugin.xml b/rse/doc/org.eclipse.dstore.doc.isv/plugin.xml deleted file mode 100755 index 51854ca97..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/plugin.xml +++ /dev/null @@ -1,9 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<plugin> - - <extension point="org.eclipse.help.toc"> - <toc file="toc.xml" primary="true"/> - <index path="index/"/> - </extension> - -</plugin> diff --git a/rse/doc/org.eclipse.dstore.doc.isv/reference/.cvsignore b/rse/doc/org.eclipse.dstore.doc.isv/reference/.cvsignore deleted file mode 100644 index eedd89b45..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/reference/.cvsignore +++ /dev/null @@ -1 +0,0 @@ -api diff --git a/rse/doc/org.eclipse.dstore.doc.isv/reference/placeholder.txt b/rse/doc/org.eclipse.dstore.doc.isv/reference/placeholder.txt deleted file mode 100644 index 89b1c1c77..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/reference/placeholder.txt +++ /dev/null @@ -1 +0,0 @@ -A nearly empty file used to force the creation of the containing folder.
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/toc.html b/rse/doc/org.eclipse.dstore.doc.isv/toc.html deleted file mode 100755 index a410f833c..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/toc.html +++ /dev/null @@ -1,18 +0,0 @@ -<!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">
- <LINK REL="STYLESHEET" HREF="book.css" TYPE="text/css">
- <title>RSE DataStore developer information</title>
-</head>
-
-<body>
-<h1>Using the RSE DataStore for Remote Communications</h1>
-This section provides information for tool developers who wish to
-add server-side tooling capabilities. Using the RSE DataStore tooling
-communication framework, server-side extensions can be written. The Remote System Explorer can be
-extended to interface the new server-side extensions.
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.dstore.doc.isv/toc.xml b/rse/doc/org.eclipse.dstore.doc.isv/toc.xml deleted file mode 100755 index 66c07c020..000000000 --- a/rse/doc/org.eclipse.dstore.doc.isv/toc.xml +++ /dev/null @@ -1,30 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-
-<toc label="RSE DStore Developer Guide">
- <topic label="Guide">
- <topic label="DataStore Overview" href="guide/overview.html">
- <topic label="DataStore Artifacts" href="guide/Artifacts.html" />
- <topic label="DataStore Communications" href="guide/Communications.html" />
- <topic label="DataElements and the DataStore Model" href="guide/DataElements.html" />
- <topic label="Memory Management of DataElements" href="guide/MemoryManagement.html" />
- <topic label="Miners" href="guide/Miners.html" />
- </topic>
- <topic label="Extending and Using the DataStore" href="guide/Extending.html">
- <topic label="Extending the Server-side" href="guide/ServerSide.html" />
- <topic label="Communicating with the Server-side" href="guide/ClientSide.html" />
- </topic>
- <anchor id="guide_additions"/>
- </topic>
- <topic label="Reference">
- <topic label="DataStore API Reference">
- <topic label="org.eclipse.dstore.core.model" href="reference/api/org/eclipse/dstore/core/model/package-summary.html" />
- <topic label="org.eclipse.dstore.core.client" href="reference/api/org/eclipse/dstore/core/client/package-summary.html" />
- <topic label="org.eclipse.dstore.core.server" href="reference/api/org/eclipse/dstore/core/server/package-summary.html" />
- <topic label="org.eclipse.dstore.core.util" href="reference/api/org/eclipse/dstore/core/util/package-summary.html" />
- <topic label="org.eclipse.dstore.core.miners.miner" href="reference/api/org/eclipse/dstore/core/miners/miner/package-summary.html" />
- </topic>
- <anchor id="reference_additions"/>
- </topic>
- <topic label="Legal" href="notices.html"/>
-</toc>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/.classpath b/rse/doc/org.eclipse.rse.doc.isv/.classpath deleted file mode 100755 index b68aa52df..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/.classpath +++ /dev/null @@ -1,6 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
- <classpathentry kind="con" path="org.eclipse.rse.launching.JRE_CONTAINER"/>
- <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
- <classpathentry kind="output" path="bin"/>
-</classpath>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/.cvsignore b/rse/doc/org.eclipse.rse.doc.isv/.cvsignore deleted file mode 100755 index 0700bef2a..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/.cvsignore +++ /dev/null @@ -1,7 +0,0 @@ -bin -index -build.xml -javadoc.link.location -temp.bin.log -temp.convert.txt -temp.options.txt diff --git a/rse/doc/org.eclipse.rse.doc.isv/.project b/rse/doc/org.eclipse.rse.doc.isv/.project deleted file mode 100755 index dcc4d40c8..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/.project +++ /dev/null @@ -1,11 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
- <name>org.eclipse.rse.doc.isv</name>
- <comment></comment>
- <projects>
- </projects>
- <buildSpec>
- </buildSpec>
- <natures>
- </natures>
-</projectDescription>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/META-INF/MANIFEST.MF b/rse/doc/org.eclipse.rse.doc.isv/META-INF/MANIFEST.MF deleted file mode 100755 index 06aeef52a..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/META-INF/MANIFEST.MF +++ /dev/null @@ -1,8 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.rse.doc.isv; singleton:=true -Bundle-Version: 1.0.0.qualifier -Bundle-Localization: plugin -Eclipse-LazyStart: false -Bundle-Vendor: %providerName diff --git a/rse/doc/org.eclipse.rse.doc.isv/aaa-how-to-add-things.txt b/rse/doc/org.eclipse.rse.doc.isv/aaa-how-to-add-things.txt deleted file mode 100755 index d73e72b8e..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/aaa-how-to-add-things.txt +++ /dev/null @@ -1,29 +0,0 @@ -Last revised July 27, 2006 -(This file is for information only; it is not included in the release.) - -See also - http://wiki.eclipse.org/index.php/How_to_add_things_to_the_Eclipse_doc -with the following exceptions: -- platformOptions.txt -> options.txt -- overview-platform.html -> /reference/misc/overview-rse.html - -To add new plug-ins you need to make changes in several places in -this doc plug-in: - -1) options.txt -- the plug-in's source folder(s) must be included on the -sourcepath -- code of required plug-ins must be added on the -classpath (the JAR(s)for non-JARed plug-ins and <plugin>/@dot for JARed plug-ins -- the API package names must be included in the (alphabetical) package list at the end of the file -- note that the @sep@ token is replaced during build by the appropriate separator character for the build platform. - -2) buildDoc.xml -- add a line in convertSchemaToHtml target to handle a new plug-ins extension point schemas - -Adding new extension points: - -1) reference/extension-points/index.html -- add a line for each extension point - -2) topics_Reference.xml -- add a line for each extension point -- add a line for each API package
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/about.html b/rse/doc/org.eclipse.rse.doc.isv/about.html deleted file mode 100755 index 460233046..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/about.html +++ /dev/null @@ -1,28 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/> -<title>About</title> -</head> -<body lang="EN-US"> -<h2>About This Content</h2> - -<p>June 2, 2006</p> -<h3>License</h3> - -<p>The Eclipse Foundation makes available all content in this plug-in ("Content"). Unless otherwise -indicated below, the Content is provided to you under the terms and conditions of the -Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available -at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>. -For purposes of the EPL, "Program" will mean the Content.</p> - -<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is -being redistributed by another party ("Redistributor") and different terms and conditions may -apply to your use of any object code in the Content. Check the Redistributor's license that was -provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise -indicated below, the terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p> - -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/book.css b/rse/doc/org.eclipse.rse.doc.isv/book.css deleted file mode 100755 index bd2fe14b0..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/book.css +++ /dev/null @@ -1,112 +0,0 @@ -P.Code {
- display: block;
- text-align: left;
- text-indent: 0.00pt;
- margin-top: 0.000000pt;
- margin-bottom: 0.000000pt;
- margin-right: 0.000000pt;
- margin-left: 15pt;
- font-size: 10.000000pt;
- font-weight: normal;
- font-style: normal;
- color: #4444CC;
- text-decoration: none;
- vertical-align: baseline;
- text-transform: none;
- font-family: "Courier New", Courier, monospace;
-}
-H6.CaptionFigColumn {
- display: block;
- text-align: left;
- text-indent: 0.000000pt;
- margin-top: 3.000000pt;
- margin-bottom: 11.000000pt;
- margin-right: 0.000000pt;
- margin-left: 0.000000pt;
- font-size: 9.000000pt;
- font-weight: bold;
- font-style: Italic;
- color: #000000;
- text-decoration: none;
- vertical-align: baseline;
- text-transform: none;
-}
-P.Note {
- display: block;
- text-align: left;
- text-indent: 0pt;
- margin-top: 19.500000pt;
- margin-bottom: 19.500000pt;
- margin-right: 0.000000pt;
- margin-left: 30pt;
- font-size: 11.000000pt;
- font-weight: normal;
- font-style: Italic;
- color: #000000;
- text-decoration: none;
- vertical-align: baseline;
- text-transform: none;
-}
-EM.UILabel {
- font-weight: Bold;
- font-style: normal;
- text-decoration: none;
- vertical-align: baseline;
- text-transform: none;
-}
-EM.CodeName {
- font-weight: Bold;
- font-style: normal;
- text-decoration: none;
- vertical-align: baseline;
- text-transform: none;
- font-family: "Courier New", Courier, monospace;
-}
-
-body, html { border: 0px }
-
-
-/* following font face declarations need to be removed for DBCS */
-
-body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-family: Arial, Helvetica, sans-serif; color: #000000}
-pre { font-family: "Courier New", Courier, monospace;}
-
-/* end font face declarations */
-
-/* following font size declarations should be OK for DBCS */
-body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-size: 10pt; }
-pre { font-size: 10pt}
-
-/* end font size declarations */
-
-body { background: #FFFFFF; margin-bottom: 1em }
-h1 { font-size: 18pt; margin-top: 5; margin-bottom: 1 }
-h2 { font-size: 14pt; margin-top: 25; margin-bottom: 3 }
-h3 { font-size: 11pt; margin-top: 20; margin-bottom: 3 }
-h4 { font-size: 10pt; margin-top: 20; margin-bottom: 3; font-style: italic }
-p { margin-top: 10px; margin-bottom: 10px }
-pre { margin-left: 6; font-size: 9pt; color: #4444CC }
-a:link { color: #0000FF }
-a:hover { color: #000080 }
-a:visited { text-decoration: underline }
-ul { margin-top: 10px; margin-bottom: 10px; }
-li { margin-top: 5px; margin-bottom: 5px; }
-li p { margin-top: 5px; margin-bottom: 5px; }
-ol { margin-top: 10px; margin-bottom: 10px; }
-dl { margin-top: 10px; margin-bottom: 10px; }
-dt { margin-top: 5px; margin-bottom: 5px; font-weight: bold; }
-dd { margin-top: 5px; margin-bottom: 5px; }
-strong { font-weight: bold}
-em { font-style: italic}
-var { font-style: italic}
-div.revision { border-left-style: solid; border-left-width: thin;
- border-left-color: #7B68EE; padding-left:5 }
-th { font-weight: bold }
-
-a.command-link {
-}
-a.command-link img {
- border-width: 0px;
- border-style: none;
- vertical-align: middle;
-}
diff --git a/rse/doc/org.eclipse.rse.doc.isv/build.properties b/rse/doc/org.eclipse.rse.doc.isv/build.properties deleted file mode 100755 index b34ce515a..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/build.properties +++ /dev/null @@ -1,29 +0,0 @@ -############################################################################### -# Copyright (c) 2000, 2006 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### -bin.includes = META-INF/,\ - about.html,\ - book.css,\ - notices.html,\ - plugin.properties,\ - plugin.xml,\ - schema.css,\ - toc.xml,\ - topics_Guide.xml,\ - topics_Questions.xml,\ - topics_Reference.xml,\ - topics_Samples.xml,\ - guide/,\ - icons/,\ - index/,\ - questions/,\ - reference/,\ - samples/ -customBuildCallbacks = customBuildCallbacks.xml diff --git a/rse/doc/org.eclipse.rse.doc.isv/buildDoc.xml b/rse/doc/org.eclipse.rse.doc.isv/buildDoc.xml deleted file mode 100755 index 616b047d8..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/buildDoc.xml +++ /dev/null @@ -1,152 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<project name="RSE ISV Doc Build" default="all" basedir="."> - - <property name="javadoc.link.location" value="${basedir}/javadoc.link.location"/> - - <target name="init"> - <available file="${basedir}/index" property="index.present" /> - <path id="path_bootclasspath"> - <fileset dir="${java.home}/lib"> - <include name="*.jar"/> - </fileset> - </path> - <property name="bootclasspath" refid="path_bootclasspath"/> - <condition property="safeBaseLocation" - value="${baseLocation}" - else="${eclipse.home}"> - <isset property="baseLocation"/> - </condition> - <delete dir="${javadoc.link.location}" /> - </target> - - <target name="computeClasspath" unless="javadoc.classpath"> - <!-- Construct the javadoc classpath and store it in a property. --> - <echo level="info" message="Computing classpath ..."/> - - <!-- Add platform dependencies required by your plug-in here. - Note that this pattern expects Eclipse to have - been installed into the platform directory structure, as is - the case during the build. --> - <patternset id="platform.classpath.pattern"> - <include name="**/org.eclipse.core*.jar"/> - <include name="**/org.eclipse.core*/**/*.jar"/> - <include name="**/org.eclipse.compare*.jar"/> - <include name="**/org.eclipse.debug.core*.jar"/> - <include name="**/org.eclipse.debug.ui*.jar"/> - <include name="**/org.eclipse.search*.jar"/> - <include name="**/org.eclipse.swt*.jar"/> - <include name="**/org.eclipse.swt*/**/*.jar"/> - <include name="**/org.eclipse.ui*.jar"/> - <include name="**/org.eclipse.ui*/**/*.jar"/> - <include name="**/org.eclipse.update*.jar"/> - <include name="**/org.eclipse.update*/**/*.jar"/> - <include name="**/org.eclipse.osgi*.jar"/> - <include name="**/org.eclipse.osgi*/**/*.jar"/> - <include name="**/org.eclipse.equinox*.jar"/> - <include name="**/org.eclipse.equinox*/**/*.jar"/> - <include name="**/org.eclipse.jface*.jar"/> - <include name="**/org.eclipse.jface*/**/*.jar"/> - <include name="**/org.eclipse.text*.jar"/> - <include name="**/org.eclipse.text*/**/*.jar"/> - <include name="**/org.eclipse.team*.jar"/> - <include name="**/org.eclipse.team*/**/*.jar"/> - <include name="**/org.junit*.jar"/> - <include name="**/org.junit*/**/*.jar"/> - <include name="**/com.ibm.icu*.jar"/> - <include name="**/com.jcraft.jsch*.jar"/> - </patternset> - - <pathconvert property="javadoc.classpath"> - <path> - <fileset dir="${safeBaseLocation}"> - <patternset refid="platform.classpath.pattern"/> - </fileset> - </path> - </pathconvert> - <echo level="info" message="Done computing classpath."/> - <echo level="debug" message="Bootclasspath is: ${bootclasspath}"/> - <echo level="debug" message="Classpath is: ${javadoc.classpath}"/> - </target> - - <target name="extractLinks"> - <mkdir dir="${javadoc.link.location}"/> - - <patternset id="package.list"> - <include name="**/package-list"/> - </patternset> - - <!-- We only need the package-list files out of these --> - <unzip dest="${javadoc.link.location}/platform/"> - <patternset refid="package.list"/> - <fileset dir="${safeBaseLocation}/plugins"> - <include name="org.eclipse.platform.doc.isv*.jar"/> - </fileset> - </unzip> - </target> - - <target name="all" depends="init" unless="index.present"> - <antcall target="convertSchemaToHtml" /> - <antcall target="generateJavadoc" /> - <antcall target="build.index" /> - </target> - - <target name="build.index" description="Builds search index for the plug-in: org.eclipse.rse.doc.isv" if="eclipse.running"> - <help.buildHelpIndex manifest="${basedir}/plugin.xml" destination="${basedir}" /> - </target> - - <target name="convertSchemaToHtml" if="eclipse.running"> - <property name="dest" value="reference/extension-points" /> - <record name="${basedir}/temp.convert.txt" action="start" /> - <pde.convertSchemaToHTML manifest="../org.eclipse.rse.core/plugin.xml" destination="${dest}" /> - <pde.convertSchemaToHTML manifest="../org.eclipse.rse.ui/plugin.xml" destination="${dest}" /> - <record name="${basedir}/temp.convert.txt" action="stop" /> - </target> - - <target name="getJavadocPath"> - <available file="${java.home}/../bin/javadoc.exe" property="javadoc" value="${java.home}/../bin/javadoc.exe" /> - <available file="${java.home}/../bin/javadoc" property="javadoc" value="${java.home}/../bin/javadoc" /> - <available file="/usr/bin/javadoc" property="javadoc" value="/usr/bin/javadoc" /> - </target> - - <target name="generateJavadoc" depends="getJavadocPath,extractLinks,computeClasspath" if="javadoc"> - <property name="optionsFile" value="temp.options.txt" /> - <copy file="options.txt" tofile="${optionsFile}" overwrite="true" /> - - <condition property="argsListDelimiter" value=":"> - <os family="unix" /> - </condition> - <condition property="argsListDelimiter" value=";"> - <os family="windows" /> - </condition> - - <replaceregexp file="${basedir}/${optionsFile}" flags="g" match="(\r\n?|\n);" replace="${argsListDelimiter}" /> - <replace file="${basedir}/${optionsFile}" token="@rt@" value="${bootclasspath}${argsListDelimiter}${javadoc.classpath}" /> - <replace file="${basedir}/${optionsFile}" token="@baseLocation@" value="${safeBaseLocation}" /> - <replace file="${basedir}/${optionsFile}" token="@javadoc.link.location@" value="${javadoc.link.location}" /> - - <!--scrub isv plugin directories of any preexisting api doc content--> - <delete dir="reference/api" /> - <mkdir dir="reference/api" /> - - <echo message="sep = ${argsListDelimiter}"/> - <echo message="javadoc = ${javadoc}"/> - <exec dir="." executable="${javadoc}" output="temp.bin.log"> - <arg line="@${basedir}/${optionsFile} -J-Xmx1000M" /> - </exec> - </target> - -</project> - - - - - - - - - - - - - - diff --git a/rse/doc/org.eclipse.rse.doc.isv/customBuildCallbacks.xml b/rse/doc/org.eclipse.rse.doc.isv/customBuildCallbacks.xml deleted file mode 100644 index 7e14739e6..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/customBuildCallbacks.xml +++ /dev/null @@ -1,157 +0,0 @@ -<!-- ===================================================================== --> -<!-- Custom targets called from a project's generated build.xml --> -<!-- Set customBuildCallbacks=<path/to/this/file> in your build.properties.--> -<!-- ===================================================================== --> -<project name="Build specific targets and properties" default="noDefault"> - - <!-- ===================================================================== --> - <!-- Default target --> - <!-- ===================================================================== --> - <target name="noDefault"> - <echo message="This file must be called with explicit targets" /> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the target build.jars --> - <!-- Available parameters : --> - <!-- build.result.folder - folder to contain the build results --> - <!-- ===================================================================== --> - <target name="pre.build.jars"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target build.jars --> - <!-- Available parameters : --> - <!-- build.result.folder - folder to contain the build results --> - <!-- ===================================================================== --> - <target name="post.build.jars"> - <ant antfile="buildDoc.xml" /> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the target build.sources --> - <!-- Available parameters : --> - <!-- build.result.folder - folder to contain the build results --> - <!-- ===================================================================== --> - <target name="pre.build.sources"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target build.sources --> - <!-- Available parameters : --> - <!-- build.result.folder - folder to contain the build results --> - <!-- ===================================================================== --> - <target name="post.build.sources"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the compilation target <name> --> - <!-- Substitute "name" with the name of the compilation target, eg @dot --> - <!-- Available parameters : --> - <!-- source.foldern : n = 1 ... N, the source folders --> - <!-- target.folder : where the results of the compilation go --> - <!-- <name>.classpath : name = name of the compilation target. A --> - <!-- reference to the classpath structure. --> - <!-- ===================================================================== --> - <!-- - <target name="pre.compileTarget.jar"> - </target> - --> - - <!-- ===================================================================== --> - <!-- Steps to do after compilation but before jaring --> - <!-- Substitute "name" with the name of the compilation target, eg @dot --> - <!-- Available parameters : --> - <!-- source.foldern : n = 1 ... N, the source folders --> - <!-- target.folder : where the results of the compilation go --> - <!-- <name>.classpath : name = name of the compilation target. A --> - <!-- reference to the classpath structure. --> - <!-- ===================================================================== --> - <!-- - <target name="post.compile.compileTarget.jar"> - </target> - --> - - <!-- ===================================================================== --> - <!-- Steps to do after the compilation target <name> --> - <!-- Substitute "name" with the name of the compilation target, eg @dot --> - <!-- Available parameters : --> - <!-- jar.location - the location of the compilation results --> - <!-- <name>.classpath : name = name of the compilation target. A --> - <!-- reference to the classpath structure. --> - <!-- ===================================================================== --> - <!-- - <target name="post.compileTarget.jar"> - </target> - --> - - <!-- ===================================================================== --> - <!-- Steps to do before the target gather.bin.parts --> - <!-- Available parameters : --> - <!-- base.dir - root of the project --> - <!-- build.result.folder - folder containing the build results --> - <!-- target.folder - destination folder --> - <!-- ===================================================================== --> - <target name="pre.gather.bin.parts"> - - </target> - <!-- ===================================================================== --> - <!-- Steps to do after the target gather.bin.parts --> - <!-- Available parameters : --> - <!-- base.dir - root of the project --> - <!-- build.result.folder - folder containing the build results --> - <!-- target.folder - destination folder --> - <!-- ===================================================================== --> - <target name="post.gather.bin.parts"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the target gather.sources --> - <!-- Available parameters : --> - <!-- destination.temp.folder - destination folder --> - <!-- ===================================================================== --> - <target name="pre.gather.sources"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target gather.sources --> - <!-- Available parameters : --> - <!-- destination.temp.folder - destination folder --> - <!-- ===================================================================== --> - <target name="post.gather.sources"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the target gather.logs --> - <!-- Available parameters : --> - <!-- destination.temp.folder - destination folder --> - <!-- ===================================================================== --> - <target name="pre.gather.logs"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target gather.logs --> - <!-- Available parameters : --> - <!-- destination.temp.folder - destination folder --> - <!-- ===================================================================== --> - <target name="post.gather.logs"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do before the target clean --> - <!-- Available parameters : --> - <!-- destination.temp.folder - destination folder --> - <!-- ===================================================================== --> - <target name="pre.clean"> - </target> - - <!-- ===================================================================== --> - <!-- Steps to do after the target clean --> - <!-- Available parameters : --> - <!-- plugin.destination - final destination of the build --> - <!-- build.result.folder - results of the compilation --> - <!-- temp.folder - temporary folder --> - <!-- ===================================================================== --> - <target name="post.clean"> - </target> -</project>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/Artifacts.html b/rse/doc/org.eclipse.rse.doc.isv/guide/Artifacts.html deleted file mode 100755 index dac67350e..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/Artifacts.html +++ /dev/null @@ -1,209 +0,0 @@ -<!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>RSE Artifacts</title> -</head> - -<body> -<h1>Remote System Explorer Artifacts</h1> -<p>With the RSE, you can create and manipulate the following artifacts, which we introduce here:</p> -<ul> -<li><A href="#Hosts">Hosts</A></li> -<li><A href="#profiles">Profiles</A></li> -<li><A href="#subsystems">Subsystems, created from subsystem configurations</A></li> -<li><A href="#connectorservices">Connector Services, managed by connector service managers</A></li> -<li><A href="#filters">Filters and filter strings</A></li> -<li><A href="#filterpools">Filter pools</A></li> -<li><A href="#Preferences">Preferences</A></li> -<li><A href="#Registry">System Registry</A></li> -</ul> -<p>All the classes and interfaces mentioned here are defined in the <samp>org.eclipse.rse.core</samp> plugin. - -<h2><A name="Hosts">Hosts</A></h2> -<p> -The RSE's <A href="view_RS.gif">Remote Systems view</A> shows all existing <b>Hosts</b> to remote systems. -Hosts are objects that are persisted, containing the information needed to access a particular remote host. -The view contains a prompt to create new Hosts, and pop-up menu actions to rename, copy, delete, and reorder existing Hosts. -</p> -<p>Hosts contain attributes, or data, that is saved between sessions of the workbench. These attributes are -the host name, the remote system's host name and system type, an optional description, and a user Id that is -used by default by each subordinate subsystem, at host time. -Underneath, all Hosts are stored via RSE persistence in an Eclipse project named <CODE>RemoteSystemsConnections</CODE></A>, which -the user can enable for team support, allowing Hosts to be shared by a team. -</p> - -<h2><A name="profiles">Profiles</A></h2> -<p> -To facilitate team-shared and user-unique Hosts, -Hosts are owned by <b>profiles</b>. These are simply <A href="file_profiles.gif">folders in the RemoteSystemsConnections -project</A>, as it turns out, within which all other data including Hosts are scoped. Internally profiles are realized as -SystemProfile objects, managed by the SystemProfileManager. -For each profile there is also a SystemHostPool object -created to manage the Hosts within that profile. There are menu actions for the -user to create and manage profiles. The collective of all Hosts of all <b><I>active</I> profiles</b> are shown in the -Remote Systems view, -and the user can easily decide which profiles are active using the <A href="preference_activeProfiles.gif">local pulldown menu</A> of the Remote Systems view. -The list of profiles currently active is stored locally on each user's workstation, and not shared by teams. -By default, there exists a profile named <code>Team</code>, and a profile with a name unique to this user. When the first -host is created the user is asked to supply this unique name, which defaults to the hostname of their -workstation. Whenever a new host is created, the user is prompted for an active profile to contain the new -host. Both default profiles are active initially, so all Hosts from each are shown. There is a preferences -setting to show the host names qualified by their profile name. After synchronizing the RemoteSystemsConnections -project with a team repository, using the RSE <A href="plugin/view_Team.gif">team view</A>, all profiles of all members of -the team will exist in the user's workspace, and hence -all the Hosts created by all the team members. However, only the two default profiles are active, so the Hosts -in the other profiles are not seen unless the user explicitly makes another profile active. This design allows -for: -</p> -<ol> -<li>Team-shared Hosts (created in the Team profile or any profile all team members make active) -<li>User-private Hosts (created in their own profile or any profile not active by default) -<li>User-roaming, whereby a user uses a different workstation than usual, -and then synchronizes with the team repository and sets their profile to be active. -</ol> -<p> -As an aside, user IDs and passwords are not shared with the team repository, but rather stored only locally per -workstation. -Each subsystem can have a unique user ID, which if not set is inherited from its host, -which in turn if not set is inherited from the -user ID preferences setting for the appropriate system type. -</p> - -<h2><A name="subsystems">Subsystems and subsystem configurations</A></h2> -<p> -When you expand a host, any tools registered with the Remote System Explorer are shown under the host. -These tools are referred to as <b>subsystems</b>. The tool provider registers a <b>subsystem configuration</b> -class via an RSE <A href="plugin/subsystem.html">extension point</A>, and whenever a new host is created, the configuration -is asked to create a new subsystem object for that host. This subsystem is responsible for communicating with the remote host, and -exposing artifacts and actions for working with remote resources. The subsystem configuration can elect not to -supply a subsystem for a given host if it does not support the system type of that host -</p> -<p> -RSE supplies two subsystem configurations that supply common subsystems for all Hosts: -<ol> -<li>Files. The subsystems created by this factory access the folders and files of the remote system, -and allow users to explore and manipulate those folders and files. Editing support for remote source files is also included. For programmers, the subsystems also supply common APIs and user interface actions, wizards, -dialogs, and widgets for easy access to the remote file system for a given host. These APIs are -typically used when coding actions that appear in the pop-up menu for selected remote objects, but might -also be of value when writing any view, editor, or action that needs access to a remote file system. -<li>Commands. The subsystems created by this factory access the command shell of the remote system and -allow users to predefine commands, and subsequently run them remotely. The commands subsystems are hidden -subsystems, not shown when you expand the host. However, they are used by any code needing to run -remote commands. There is also a Remote Commands view supplied that logs all commands and allows users to -randomly enter a command to be run remotely. The commands all execute within the same shell, and users -can launch additional shells for the same host. -</ol> -<h2><A name="systems">Systems and System Managers</A></h2> -<p>While not seen by the user, subsystem objects are required to return a <b>connectorservice</b> object via the -<A href="../reference/api/org/eclipse/rse/core/subsystems/ISubSystem.html#getConnectorService()">getConnectorService()</A> method. -A connectorService object is an object implementing the <A href="../reference/api/org/eclipse/rse/core/subsystems/IConnectorService.html">IConnectorService</A> interface. -A connectorService object manages the live host to the remote system, and supports -lifecycle methods for that host such as -<A href="../reference/api/org/eclipse/rse/core/subsystems/IConnectorService.html#connect(org.eclipse.core.runtime.IProgressMonitor)">connect</A>, -<A href="../reference/api/org/eclipse/rse/core/subsystems/IConnectorService.html#disconnect()">disconnect</A>, and -<A href="../reference/api/org/eclipse/rse/core/subsystems/IConnectorService.html#isConnected()">isConnected</A>. -The communication layer for that host is entirely the programmer's responsibility, and might use sockets, JDBC, HTTP or -SOAP. It is up the provider of the subsystem factory to author their own communication layer; the framework -only dictates the handful of methods in IConnectorService, that the RSE UI depends upon. The framework supplies a base -system class that is easily extended. -</p> -<p>It may be the case that multiple subsystems, each from a different subsystem configuration, share the same live -host for a given host object. To enable this, the framework supplies a base -<b>connector service manager</b> <A href="../reference/api/org/eclipse/rse/core/subsystems/AbstractConnectorServiceManager.html">class</A> -that can be used to manage a single shared connector service object across multiple subsystems. It uses a hashtable to store and -return the connector service objects, keyed by a subsystem interface that all subsystems sharing the same connector service object -are to implement. The subclass of the base connector service manager class supplies that interface. Further, the subclass -must also implement the method for instantiating new instances of the connector service class, when no instance is found -in the hashtable. -</p> -<p> -It is possible to author a subsystem configuration whose subsystems simply use the same connector service object as that used by -the RSE-supplied subsystems. You might do this if the subsystem configuration uses only the RSE-supplied APIs for -accessing remote objects, in which case there is no need for a unique communication layer. By sharing the -same connector service object, it prevents the user from being prompted to signon multiple times. To do this, simply access -any RSE-supplied subsystem for a given host, and ask for its -<A href="../reference/api/org/eclipse/rse/core/subsystems/ISubSystem.html#getConnectorServiceManager()">connector service manager</A> -in your own subsystem's <A href="../reference/api/org/eclipse/rse/core/subsystems/AbstractConnectorService.html#getConnectorServiceManager()">getConnectorServiceManager</A> method. -</p> - -<h2><A name="filters">Filters</A></h2> -<p> -When a subsystem is expanded, users usually see <b>filters</b>. Since subsystems typically list remote artifacts, -it is typical that a mechanism is needed to allow users to define which artifacts they wish to see, with some -form of filtering criteria. Filters are this mechanism. The filter support is fully supplied by the RSE framework. -A filter is simply a <A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilter.html">ISystemFilter</A> -object containing a name and a collection of <b>filter strings</b>. Filter strings are just strings, which -the subsystem is required to interpret. When a user expands a filter, the owning subsystem is asked to resolve -the filter strings within the filter. The subsystem typically interprets each filter string as some form of -filtering pattern, and returns a list of remote artifacts matching one or more of the filter string patterns in -the filter. For example, file subsystems expect each filter string to represent a folder, and a file name pattern. Then, all files in the folder, matching the name pattern, are returned. The subsystem supplies the user interface the -you use to create and change filter strings, so it is responsible for defining what the filter strings -look like and for subsequently resolving those filter strings on a filter expansion. A default user interface for -the filter string prompt is supplied, but it is a simple entry field. -</p> -<p> -It is possible to author a subsystem that does not support filters, if this is desired. -</p> - -<h2><A name="filterpools">Filter Pools</A></h2> -<p> -Subsystems do not actually "own" filters. Since each host has unique subsystems, if each subsystem owned its -own filters then filters could not be shared across Hosts, which is sometimes desirable. Instead, filters are -actually contained within <b>filter pools</b>. Filter pools are simply -<A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilterPool.html">ISystemFilterPool</A> -objects which have a name and a collection of filters. -Filter pools are owned by subsystem configurations, per profile. That is, each subsystem configuration will contain filter pools -scoped by profile. Each such configuration plus profile grouping is known internally as a -<A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilterPoolManager.html">filter pool manager</A>. -Subsystems contain <A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilterPoolReference.html">references</A> -to filter pools. By default, each subsystem configuration automatically creates one filter pool -for each profile, named the "xxx Filter Pool", where "xxx" is the name of the profile. Subsystems contain references to -filter pools, so that as the filters in the pool are created, changed, deleted or re-ordered, those changes are automatically -reflected in every subsystem (and hence host) that references that filter pool. By default, subsystems are given a -reference to the default filter pool in their host's profile (for their parent subsystem configuration, so file filters -are not used in command subsystems, for example). -</p> -<p> -By default, users do not see filter pools. Instead, filters are created in the default filter pool referenced by this subsystem. -As a result, users will see the same list of filters for every host. However, users can use a preference setting to see -filter pools. In this case, when a subsystem is expanded, the users see the filter pools referenced by this subsystem. -Only then when a filter pool is expanded will the user see the filters within that filter pool. In this mode, users also -see new actions to create filter pools and to add and remove references to filter pools within a subsystem. Whenever filters -are changed by the user, this change is reflected in all subsystems that reference the parent filter pool. This design -of filter pools owned by profiles, and subsystems that reference filter pools, facilitates filter sharing: -<ol> -<li>Users can share filters across Hosts, by adding references to their parent filter pool in various subsystems.<li>Users can have filters unique to a host, by placing them in a filter pool not referenced by other subsystems. -<li>Users can have both shared and host-unique filters in a single host, by having both shared and private references -to filter pools.<li>Teams can share filters by asking each user to add a reference to the same filter pool in their Hosts. For example, -this is the default case for the default filter pool. -<li>Users can create filters that are not shared by the team, by creating their own filter pools and not asking others to -reference it. -</ol> -</p> -<h2><A name="preferences">Preferences</A></h2> -<p> -Many of the default characteristics of the Remote System Explorer view and perspective are configurable by each user -by way of the <A href="preferences.gif">Remote Systems node</A> of the <b>Preferences</b> window, accessible from the Window pull-down of the main menu. -Furthermore, many of these preferences are directly accessible from the <A - href="view_pulldown.gif">pull-down menu of the title bar for the Remote -Systems view</A>. These preferences, like all preferences, are unique to each user and not shared by the team, although they can -be exported and imported. -</p> - -<h2><A name="Registry">System Registry</A></h2> -<p>The programmatic front door to all the artifacts in the RSE is the -<b>System Registry</b>, which is an object implementing -<A href="../reference/api/org/eclipse/rse/core/model/ISystemRegistry.html">ISystemRegistry</A>. -This is a singleton object that you -can access by calling the static method -<A href="../reference/api/org/eclipse/rse/model/SystemStartHere.html#getSystemRegistry()">getSystemRegistry()</A> in the -<A href="../reference/api/org/eclipse/rse/model/SystemStartHere.html">SystemStartHere</A> -class in the <samp>org.eclipse.rse.ui</samp> plugin. -</p> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/Extensions.html b/rse/doc/org.eclipse.rse.doc.isv/guide/Extensions.html deleted file mode 100755 index 8606142ef..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/Extensions.html +++ /dev/null @@ -1,99 +0,0 @@ -<!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>systemTypes</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.ui.<b>subsystemConfigurations</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> - --> - </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>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/Model.html b/rse/doc/org.eclipse.rse.doc.isv/guide/Model.html deleted file mode 100755 index 4fd3de51c..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/Model.html +++ /dev/null @@ -1,56 +0,0 @@ -<!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." > -<title>RSE Model</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body> -<h1>Remote System Explorer Model</h1> -<p>The underlying containment model for the RSE static artifacts is shown here.</p> -<p><img ref="ModelRSE.gif" src="ModelRSE.png"></p> - <p>At runtime, the model takes a slightly different form:</p> - <ul> -<li> -<A href="../reference/api/org/eclipse/rse/core/model/ISystemProfile.html">Profiles</A> are managed by a -<A href="../reference/api/org/eclipse/rse/core/model/ISystemProfileManager.html">profile manager</A>, and contain: -</li> -<ul> -<li><A href="../reference/api/org/eclipse/rse/core/model/ISystemHostPool.html">Host Pools</A>, one per profile, which contain</li> -<ul> -<li><A href="../reference/api/org/eclipse/rse/core/model/IHost.html">Hosts</A></li> -</ul> -<li><A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilterPool.html">Filter pools</A>, keyed by Subsystem Configuration, and managed by a <A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilterPoolManager.html">filter pool manager</A> -which contain</li> -<ul> -<li><A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilter.html">Filters</A>, which contain</li> -<ul> -<li><A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilterString.html">Filter strings</A></li> -</ul> -</ul> -<!-- -<li><A href="../reference/api/org/eclipse/rse/ui/uda/ISystemUDActionElement.html">User actions</A>, keyed by Subsystem Configuration, which contain</li> -<ul> -<li><i>References</i> to <A href="../reference/api/org/eclipse/rse/ui/uda/ISystemUDTypeElement.html">named types</A></li> -</ul> -<li><A href="../reference/api/org/eclipse/rse/ui/compile/SystemCompileCommand.html">Compile commands</A></li> ---> -</ul> -<li><A href="../reference/api/org/eclipse/rse/core/subsystems/SubSystemConfiguration.html">Subsystem Configurations</A> contain:</li> -<ul> -<li><A href="../reference/api/org/eclipse/rse/core/subsystems/SubSystem.html">Subsystems</A>, keyed by host, which contain</li> -<ul> -<li><i><A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilterPoolReference.html">References</A></i> -to <A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilterPool.html">filter pools</A>, which are managed by <A href="../reference/api/org/eclipse/rse/core/filters/ISystemFilterPoolManager.html">filter pool managers</A></li> -</ul> -<!-- -<li><A href="../reference/api/org/eclipse/rse/ui/uda/SystemUDTypeElement.html">Named types</A></li> ---> -</ul> -</ul> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/ModelRSE.png b/rse/doc/org.eclipse.rse.doc.isv/guide/ModelRSE.png Binary files differdeleted file mode 100755 index d079e6e26..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/ModelRSE.png +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/actions/uiActionsAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/actions/uiActionsAPI.html deleted file mode 100755 index 841132b66..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/actions/uiActionsAPI.html +++ /dev/null @@ -1,89 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Actions API</title> -<STYLE type="text/css"> -<!-- -TH { - background-color: #e5e5e5 -} ---> -</STYLE> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Actions API</h1> -<p>In Eclipse, we typically launch our dialogs and wizards and menu items from an action, which is -a class that implements the JFace <samp>IAction</samp> interface. The Remote System Explorer offers classes to -help simplify the creation of action classes, especially when used together with the RSE classes for -<a href="../dialogs/uiDialogsAPI.html">dialogs</a> and <a href="../wizards/uiWizardsAPI.html">wizards</a>. -</p> -<p>There are two ways the Remote System Explorer API set can help you when it comes to actions: -<ol> -<li>A set of base action classes from which to base your own action classes. -<li>A set of re-usable actions for specific requirements. -</ol> -</p> - -<h2>RSE-Supplied Base Classes for Actions</h2> -<p>Here are the primary base classes the RSE supplies for actions, all of which are found in the -package <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/package-summary.html"org.eclipse.rse.ui.actions</A></samp> -in the plugin <samp>org.eclipse.rse.ui</samp>:</p> -<TABLE border="1"> - <TBODY> - <TR> - <TH>Class</TH> - <TH>Description</TH> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseAction.html">SystemBaseAction</A></samp></TD> - <TD>This is the base action class for the other classes, and is only used directly for actions that do not - result in a dialog or wizard being presented to the user. It extends the JFace <samp>Action</samp> class, - adding to it support for properties such as the current shell and viewer and selection, as well as - overridable methods for easily enabling/disabling the action based on the selection, and a method for - setting the context help for the action. There are many other useful methods, such - as <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseAction.html#allowOnMultipleSelection(boolean)">allowOnMultipleSelection(boolean)</A></samp> - and <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseAction.html#setContextMenuGroup(java.lang.String)">setContextMenuGroup(String)</A></samp>, to - simplify when the action is enabled and where it appears in a popup menu. - </TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseSubMenuAction.html">SystemBaseSubMenuAction</A></samp></TD> - <TD>This base action class extends <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseAction.html">SystemBaseAction</A></samp>, and is used as the parent class when - for popup menu actions that are to cascade. A cascading menu is itself another menu, really, containing actions just like the primary - menu does. So, to create a cascading menu action, you simply subclass this class and override the method - <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseSubMenuAction.html#populateSubMenu(org.eclipse.jface.action.IMenuManager)">populateSubMenu</A></samp>, where - you add all the actions to show in this cascading menu. And yes, one or more of those can themselves be cascading. The RSE views will - automatically call the method <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseSubMenuAction.html#getSubMenu()">getSubMenu</A></samp> when populating the initial popup menu, but your own views will need to do this.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseDialogAction.html">SystemBaseDialogAction</A></samp></TD> - <TD>This base action class extends <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseAction.html">SystemBaseAction</A></samp>, and is used when the action presents the - user with a dialog, preferably a dialog that extends the RSE - <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html">SystemPromptDialog</A></samp> class. To use this class, subclass it and override the methods </TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseWizardAction.html">SystemBaseWizardAction</A></samp></TD> - <TD>This base action class extends <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseAction.html">SystemBaseAction</A></samp>, and is used when the action presents the - user with a wizard, preferably a wizard that extends the RSE <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html">AbstractSystemWizard</A></samp> class.</TD> - </TR> - - </TBODY> -</TABLE> - -<h2>Actions Pre-Supplied by RSE</h2> -<p>You may find some of the actions supplied by the RSE to be immediately re-usable in your own code, saving some -development and test effort. -All these actions can be found in package -<samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/package-summary.html">org.eclipse.rse.ui.actions</A></samp>. -Further, you can find many useful actions related to the selection of remote files or folders, in package -<samp><A href="../../../reference/api/org/eclipse/rse/files/ui/actions/package-summary.html">org.eclipse.rse.files.ui.actions</A></samp>. -</p> - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/browseFolderDialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/browseFolderDialog.gif Binary files differdeleted file mode 100755 index 07af5fc43..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/browseFolderDialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/deleteDialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/deleteDialog.gif Binary files differdeleted file mode 100755 index 2119a5357..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/deleteDialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/dialogSample.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/dialogSample.html deleted file mode 100755 index ba8734dd6..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/dialogSample.html +++ /dev/null @@ -1,265 +0,0 @@ -<!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" HREF="../../../book.css" CHARSET="UTF-8" TYPE="text/css"> -<title>RSE Validator Sample One</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Dialog Sample</h1> -<p>This is an example of a sample<A href="sampleDlg.gif"> dialog</A> written on top of the RSE base dialog class, and with -typical full error checking. -<pre> - -package org.eclipse.rse.samples.ui.frameworks.dialogs; - -import org.eclipse.swt.widgets.*; -import org.eclipse.swt.events.*; - -import org.eclipse.rse.samples.*; - -import org.eclipse.rse.ui.dialogs.SystemPromptDialog; -import org.eclipse.rse.ui.*; -import org.eclipse.rse.ui.widgets.*; -import org.eclipse.rse.ui.messages.*; -import org.eclipse.rse.ui.validators.*; - -/** - * <I>A simple example of using the SystemPromptDialog class as the basis for a new dialog</I>. - */ -public class <B>SampleDialog</B> extends SystemPromptDialog -{ - // <I>gui widgets</I> - private SystemHistoryCombo namePrompt; - private Text yearPrompt, monthPrompt, dayPrompt; - // <I>input</I> - private SampleCustomer inpCust; - // <I>validators</I> - private ISystemValidator nameValidator, yearValidator, monthValidator, dayValidator; - // <I>message</I> - private SystemMessage errorMessage; - - /** - * <I>Constructor for SampleDialog</I>. - */ - public <B>SampleDialog</B>(Shell shell) - { - super(shell, SamplesPlugin.getString("org.eclipse.rse.samples.ui.dialogs.dialog1.title")); - setHelp(SamplesPlugin.HELPPREFIX + "dlg11000"); - nameValidator = new <A href="../validators/validatorSample1.html">SampleNameValidator</A>(); - yearValidator = new <A href="../validators/validatorSample2.html">SampleBirthYearValidator</A>(); - monthValidator = new <A href="../validators/validatorSample3.html">SampleBirthMonthValidator</A>(); - dayValidator = new <A href="../validators/validatorSample4.html">SampleBirthDayValidator</A>(); - } - - /** - * <I>Required parent override.</I> - * <I>This is where we populate the client area</I> - */ - protected Control <B>createInner</B>(Composite parent) - { - int nbrColumns = 2; - Composite parentComposite = SystemWidgetHelpers.createComposite(parent, nbrColumns); - - // <I>add gui widgets</I>... - SystemWidgetHelpers.createLabel(parentComposite, SamplesPlugin.getResourceBundle(), "org.eclipse.rse.samples.ui.dialogs.dialog1.name."); - boolean readonly = false; - namePrompt = SystemWidgetHelpers.createHistoryCombo(parentComposite, null, "name.history.key", readonly, - SamplesPlugin.getResourceBundle(), "org.eclipse.rse.samples.ui.dialogs.dialog1.name.tooltip"); - - addSeparatorLine(parentComposite, nbrColumns); - boolean wantBorder = false; - SystemWidgetHelpers.createLabel(parentComposite, SamplesPlugin.getResourceBundle(), - "org.eclipse.rse.samples.ui.dialogs.dialog1.birthday.verbage.", nbrColumns, wantBorder); - - yearPrompt = SystemWidgetHelpers.createLabeledTextField(parentComposite, null, - SamplesPlugin.getResourceBundle(), "org.eclipse.rse.samples.ui.dialogs.dialog1.birthday.year."); - monthPrompt = SystemWidgetHelpers.createLabeledTextField(parentComposite, null, - SamplesPlugin.getResourceBundle(), "org.eclipse.rse.samples.ui.dialogs.dialog1.birthday.month."); - dayPrompt = SystemWidgetHelpers.createLabeledTextField(parentComposite, null, - SamplesPlugin.getResourceBundle(), "org.eclipse.rse.samples.ui.dialogs.dialog1.birthday.day."); - - // <I>if given an existing object, prefill it</I>... - inpCust = (SampleCustomer)getInputObject(); - if (inpCust != null) - { - namePrompt.setText(inpCust.getName()); - yearPrompt.setText(inpCust.getYear()); - monthPrompt.setText(inpCust.getMonth()); - dayPrompt.setText(inpCust.getDay()); - } - - - // <I>add modify listeners</I>... - namePrompt.addModifyListener( new ModifyListener() - { - public void modifyText(ModifyEvent event) - { - if (validateName()) - validate(namePrompt.getCombo()); - } - } ); - yearPrompt.addModifyListener( new ModifyListener() - { - public void modifyText(ModifyEvent event) - { - if (validateYear()) - validate(yearPrompt); - } - } ); - monthPrompt.addModifyListener( new ModifyListener() - { - public void modifyText(ModifyEvent event) - { - if (validateMonth()) - validate(monthPrompt); - } - } ); - dayPrompt.addModifyListener( new ModifyListener() - { - public void modifyText(ModifyEvent event) - { - if (validateDay()) - validate(monthPrompt); - } - } ); - - // <I>initialize enabled state</I>... - setPageComplete(isPageComplete()); - - return parentComposite; - } - - /** - * <I>Required parent override</I>. - * <I>This is where we return the first input control, to give it focus when the dialog appears</I>. - */ - protected Control <B>getInitialFocusControl</B>() - { - return namePrompt.getCombo(); - } - - /** - * <I>Typical parent override</I>. - * <I>This is where we get control when the user presses OK</I>. - */ - protected boolean <B>processOK</B>() - { - errorMessage = null; - Control controlInError = validate(null); - if (controlInError != null) - controlInError.setFocus(); - else - { - SampleCustomer newCust = inpCust; - if (newCust == null) - newCust = new SampleCustomer(); - newCust.setName(namePrompt.getText().trim()); - newCust.setYear(yearPrompt.getText().trim()); - newCust.setMonth(monthPrompt.getText().trim()); - newCust.setDay(dayPrompt.getText().trim()); - setOutputObject(newCust); - - SystemMessage completionMsg = null; - if (inpCust == null) - completionMsg = SamplesPlugin.getPluginMessage("SPPD1010"); - else - completionMsg = SamplesPlugin.getPluginMessage("SPPD1011"); - completionMsg.makeSubstitution(newCust.getName()); - SystemMessageDialog msgDlg = new SystemMessageDialog(getShell(), completionMsg); - msgDlg.open(); - } - return isPageComplete(); - } - - // --------------------- - // <I>Validation methods</I>... - // --------------------- - /** - * <I>Do full validation of all entry fields, optionally skipping a given one</I>. - * <I>@return first control that is found to contain errors. Can be used to set focus</I>. - */ - protected Control <B>validate</B>(Control controlToSkip) - { - Control controlInError = null; - - if ((controlToSkip != namePrompt.getCombo()) && !validateName()) - controlInError = namePrompt.getCombo(); - if ((controlInError==null) && (controlToSkip != yearPrompt) && !validateYear()) - controlInError = yearPrompt; - if ((controlInError==null) && (controlToSkip != monthPrompt) && !validateMonth()) - controlInError = monthPrompt; - if ((controlInError==null) && (controlToSkip != dayPrompt) && !validateDay()) - controlInError = dayPrompt; - - return controlInError; - } - /** - * <I>Validate the customer name prompt. We only ensure it is not-empty.</I> - */ - protected boolean <B>validateName</B>() - { - String input = namePrompt.getText().trim(); - setErrorMessageAndPageCompletionStatus(nameValidator.validate(input)); - return (errorMessage==null); - } - /** - * <I>Validate the customer birth year prompt</I>. - */ - protected boolean <B>validateYear</B>() - { - String input = yearPrompt.getText().trim(); - setErrorMessageAndPageCompletionStatus(yearValidator.validate(input)); - return (errorMessage==null); - } - /** - * <I>Validate the customer birth month prompt</I>. - */ - protected boolean <B>validateMonth</B>() - { - String input = monthPrompt.getText().trim(); - setErrorMessageAndPageCompletionStatus(monthValidator.validate(input)); - return (errorMessage==null); - } - /** - * <I>Validate the customer birth day prompt</I>. - */ - protected boolean <B>validateDay</B>() - { - String input = dayPrompt.getText().trim(); - setErrorMessageAndPageCompletionStatus(dayValidator.validate(input)); - return (errorMessage==null); - } - - /** - * <I>A convenience method that issues or clears the error message on the message line</I>, - * <I>and sets the page completion status</I> - */ - protected void <B>setErrorMessageAndPageCompletionStatus</B>(SystemMessage errorMessage) - { - this.errorMessage = errorMessage; - if (errorMessage == null) - clearErrorMessage(); - else - setErrorMessage(errorMessage); - setPageComplete(isPageComplete()); - } - /** - * <I>Return true if the OK button can be enabled</I>. - */ - protected boolean <B>isPageComplete</B>() - { - return ((errorMessage == null) && - (namePrompt.getText().trim().length()>0) && - (yearPrompt.getText().trim().length()>0) && - (monthPrompt.getText().trim().length()>0) && - (dayPrompt.getText().trim().length()>0)); - } -}</pre> - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/renameManyDialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/renameManyDialog.gif Binary files differdeleted file mode 100755 index cfeb0c6cd..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/renameManyDialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/renameOneDialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/renameOneDialog.gif Binary files differdeleted file mode 100755 index cc6256c23..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/renameOneDialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/sampleDlg.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/sampleDlg.gif Binary files differdeleted file mode 100755 index 0d55573b3..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/sampleDlg.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/selectTypesDialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/selectTypesDialog.gif Binary files differdeleted file mode 100755 index be5361af4..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/selectTypesDialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/simpleSelectDialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/simpleSelectDialog.gif Binary files differdeleted file mode 100755 index b9bfca608..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/simpleSelectDialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/uiDialogsAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/uiDialogsAPI.html deleted file mode 100755 index 92f7cb30d..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/dialogs/uiDialogsAPI.html +++ /dev/null @@ -1,180 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Dialogs API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Dialogs API</h1> -<p>There are two ways the Remote System Explorer API set can help you when it comes to dialogs: -<ol> -<li>A base dialog class from which to base your own dialog classes. -<li>A set of re-usable dialogs for specific requirements. -</ol> -</p> - -<h2>RSE-Supplied Base Class for Dialogs</h2> -<p>Dialogs are secondary windows that prompt the user for information or display information to the user. They are typically -<i>modal</i>, meaning the rest of the application (in this case eclipse) is disabled while the dialog is showing. -Eclipse supplies a raw dialog class in SWT, as well as more robust dialog class in JFace. The RSE supplies its own -class, -<samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html">SystemPromptDialog</A></samp> -in package -<samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/package-summary.html">org.eclipse.rse.ui.dialogs</A></samp> -, that extends -the JFace dialog class and adds to it the following capabilities inherited by all classes which extend it: -</p> -<ul> -<li>Support for an optional visual message line at the bottom, on which messages can be displayed to the user. These can be either -<samp>SystemMessage</samp> objects, or simple string messages. <samp><A - href="../messages/uiMessageAPI.html#SystemMessage">SystemMessage</A></samp> objects are preferred, as using these enables a button -beside the message line which users can press to see the details for the message. This is supported via the <samp><A - href="../messages/uiMessageAPI.html#ISystemMessageLine">ISystemMessageLine</A></samp> -interface, and so offers a consistent programming interface with the RSE property page and wizard page classes. -<li>Support of automatic assignment of mnemonics for input-capable widgets such as buttons. This saves tremendous development -effort if your user interface is translated as the assignment of unique mnemonics can be difficult after translation. -<li>Built-in support for a number of typical push buttons at the bottom of the dialog: OK, Cancel, Browse, Test, Add and -Details. You control via setters which buttons to show, and you can affect their label and tooltip text, although the -default labels and tips are already translated for you. To program what happens when pressed, override the appropriate -<samp>processXXX()</samp> method, such as <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#processOK()">processOK()</A></samp>. By default, you get OK and Cancel buttons. -<li>Support for an optional built-in progress monitor at the bottom of the dialog, just like what eclipse offers for wizards. -<li>Support of a simple <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#wasCancelled()">wasCancelled()</A></samp> method to easily test if the dialog was cancelled or not. -<li>Support for methods to set an input object, and retrieving an output object, making it easy to pass in data and -get back data. Your calling code sets the input object, your subclass code sets the output object (typically in -its <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#processOK()">processOK()</A></samp> method) and your calling code gets the output object, -if <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#wasCancelled()">wasCancelled()</A></samp> returns false. -<li>Support of a <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#setPageComplete(boolean)">setPageComplete(boolean)</A></samp> method, consistent with wizard pages, to enable/disable the OK button. -This is typically called by your keystroke and button validators. That is, if an error is detected as input is entered, a message -is issued to the message line and the OK button is disabled. -<li>Support of a simple <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#setHelp(java.lang.String)">setHelp(String helpId)</A></samp> method to set the dialog's popup help. -<li>A simple way to toggle the cursor between busy and normal, using -<samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#setBusyCursor(boolean)">setBusyCursor(boolean)</A></samp> -<li>Helper methods for adding <A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#addFillerLine(org.eclipse.swt.widgets.Composite, int)">filler lines</A> -and <A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#addSeparatorLine(org.eclipse.swt.widgets.Composite, int)">separator lines</A>. -</ul> -<p>To create your own dialog:</p> -<ol> -<li>Subclass <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html">SystemPromptDialog</A></samp>, picking the appropriate constructor, the simplest -of which simply requires the shell of the parent window and the title string for this dialog. -<li>If buttons beyond OK and Cancel are desired, in your own constructor call the appropriate <samp>setShowXXXButton(true)</samp> methods to enable -these buttons, and override the appropriate <samp>processXXX()</samp> methods to process these buttons when pressed by the user. -<li>If a progress monitor is desired, in your own constructor call <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#setNeedsProgressMonitor(boolean)">setNeedsProgressMonitor(true)</A></samp>. Later, to run -a long-running operation that displays the progress monitor, use <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#getProgressMonitor()">getProgressMonitor()</A></samp>. -<li>Override the <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#createInner(org.eclipse.swt.widgets.Composite)">createInner(Composite)</A></samp> method to populate the client area of the dialog with SWT widgets. Typically -you create your composite with a GridLayout layout, populate it, and return it. To ease this programming burden, use the many -static helper methods in <samp><A href="../../../reference/api/org/eclipse/rse/ui/SystemWidgetHelpers.html">SystemWidgetHelpers</A></samp>. -<li>Override the <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#getInitialFocusControl()">getInitialFocusControl()</A></samp> method to supply the control to get initial focus when the dialog is displayed. -<li>Override the <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#processOK()">processOK()</A></samp> method to supply the processing for when OK is pressed. You typically first validate -the user input, and then return true if there are no errors found. -<li>To allow the caller to get user-entered information out of the dialog, either supply getter methods, -or call <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#setOutputObject(java.lang.Object)">setOuputObject(Object)</A></samp> -in your processOK logic so that your caller can code <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html#getOutputObject()">getOutputObject()</A></samp>. -</ol> -<P>One of the more difficult efforts in building a dialog with multiple entry fields, is the code to do the validation of those entry fields. A common strategy is to add modify listeners to the entry fields, and for each one validate the data as it typed. If the validation fails, a message is issued. If the validation succeeds, then the other fields on the dialog are validated. At the end of the validation, the OK button is enabled or disabled depending on the error message status, and whether the required information has been supplied. The RSE can help with this effort, somewhat, through the use of re-usable <A - href="../validators/uiValidatorsAPI.html">validators</A> for various types of input.<BR> -<BR> -Follow this <A href="dialogSample.html">link</A> for an example of a fully-formed dialog class written on top of this RSE base class, complete with -error checking.</P> - -<p>Typically, after creating your dialog, you will create an action to invoke it. The RSE can help with this too, via the -supplied <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseDialogAction.html">SystemBaseDialogAction</A></samp> base class. - -<h2>Dialogs Pre-Supplied by RSE</h2> -<p>You may find some of the dialogs supplied by the RSE to be immediately re-usable in your own code, saving some -development and test effort. All these dialogs are in package <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/package-summary.html">org.eclipse.rse.ui.dialogs</A></samp>: -</p> - - -<TABLE border="1"> - <TBODY> - <TR> - <TH>Class</TH> - <TH>Description</TH> - <TH>Sample</TH> - <TH>Action</TH> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemRenameDialog.html">SystemRenameDialog</A></samp></TD> - <TD>Rename multiple items. Provides a table listing the old names and new names, which are editable. If your input objects - do not adapt to <samp><A href="../../../reference/api/org/eclipse/rse/ui/view/ISystemViewElementAdapter.html">ISystemViewElementAdapter</A></samp> - or <samp><A href="../../../reference/api/org/eclipse/rse/ui/view/ISystemRemoteElementAdapter.html">ISystemRemoteElementAdapter</A></samp>, - you should call <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemRenameDialog.html#setNameValidator(org.eclipse.rse.ui.validators.ISystemValidator)">setNameValidator</A></samp> to specify a validator that ensures the new name is correct, and your - input objects should also either be IResource objects or implement - <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/ISystemTypedObject.html">ISystemTypedObject</A></samp>. - </TD> - <TD align="center"><A href="renameManyDialog.gif">Sample image</A></TD> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemCommonRenameAction.html">SystemCommonRenameAction</A></samp></TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemRenameSingleDialog.html">SystemRenameSingleDialog</A></samp></TD> - <TD>Rename a single item. Provides a simple entry field for the new name. If your input object - does not adapt to <samp><A href="../../../reference/api/org/eclipse/rse/ui/view/ISystemViewElementAdapter.html">ISystemViewElementAdapter</A></samp> or - <samp><A href="../../../reference/api/org/eclipse/rse/ui/view/ISystemRemoteElementAdapter.html">ISystemRemoteElementAdapter</A></samp>, - you should call <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemRenameSingleDialog.html#setNameValidator(org.eclipse.rse.ui.validators.ISystemValidator)">setNameValidator</A></samp> to specify a validator that ensures the new name is correct, and your - input object should also either be an IResource object or implement <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/ISystemTypedObject.html">ISystemTypedObject</A></samp>. - </TD> - <TD align="center"><A href="renameOneDialog.gif">Sample image</A></TD> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemCommonRenameAction.html">SystemCommonRenameAction</A></samp></TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemDeleteDialog.html">SystemDeleteDialog</A></samp></TD> - <TD>Confirm delete of one or more items. Provides a table listing the names of input objects. If your input objects - do not adapt to <samp><A href="../../../reference/api/org/eclipse/rse/ui/view/ISystemViewElementAdapter.html">ISystemViewElementAdapter</A></samp> or - <samp><A href="../../../reference/api/org/eclipse/rse/ui/view/ISystemRemoteElementAdapter.html">ISystemRemoteElementAdapter</A></samp>, - your input objects should either be IResource objects or implement <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/ISystemTypedObject.html">ISystemTypedObject</A></samp>. - </TD> - <TD align="center"><A href="deleteDialog.gif">Sample image</A></TD> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemCommonDeleteAction.html">SystemCommonDeleteAction</A></samp></TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemSelectFileTypesDialog.html">SystemSelectFileTypesDialog</A></samp></TD> - <TD>Presents a dialog listing all the file types defined in the eclipse File Associations preferences page, and - allows the user to select one or more of these types, or enter additional types not defined in eclipse.</TD> - <TD align="center"><A href="selectTypesDialog.gif">Sample image</A></TD> - <TD><samp></samp></TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemSimpleSelectDialog.html">SystemSimpleSelectDialog</A></samp></TD> - <TD>Eclipse has a CheckboxTreeViewer that is designed to allow the user to select multiple items from a hierarchical model. - This is a nice viewer, but very difficult to program to, as you have to handle reflecting the state of the selected children - for each parent node yourself. This dialog makes that trivial. The trick is to create wrappers of your model objects using - <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemSimpleContentElement.html">SystemSimpleContentElement</A></samp>, maintaining the parent/child hierarchy, and pass the root element to the dialog. The rest is - done for you, and the result is the selected state set for those elements selected by the user. Note this can also be used - as a simple flat list checkbox selection dialog, just by passing a non-visible root with a flat list of children.</TD> - <TD align="center"><A href="simpleSelectDialog.gif">Sample image</A></TD> - <TD>None</TD> - </TR> - - </TBODY> -</TABLE> - <P><BR>While the dialogs can be instantiated directly, it is perhaps best to use them by instantiating their action class, and calling the run method on it. -The action classes are all in <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/package-summary.html">org.eclipse.rse.ui.actions</A></samp> package. -</P> - <p>In addition to these universal dialogs, there are dialogs specific to the Files subsystem supplied by IBM. These enable selection of remote files or folders. They can be found in the <a href="../../../reference/api/org/eclipse/rse/files/ui/dialogs/package-summary.html"><samp>org.eclipse.rse.files.ui.dialogs</samp></a> package.</p> - <TABLE border="1"> - <TBODY> - <TR> - <TH>Class</TH> - <TH>Description</TH> - <TH>Sample</TH> - <TH>Action</TH> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/files/ui/dialogs/SystemSelectRemoteFileOrFolderDialog.html">SystemSelectRemoteFileOrFolderDialog</A></samp></TD> - <TD>Allows users to select a remote file, or folder (configurable) using a dialog similar to what is used in Eclipse for local file or - folder selection. Can be configured to allow user to select from any existing connection, or to be scoped to a particular connection, - or even a particular folder in a particular connection. - </TD> - <TD align="center"><A href="browseFolderDialog.gif">Sample image</A></TD> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/files/ui/actions/SystemSelectRemoteFileAction.html">SystemSelectRemoteFileAction</A></samp> or - <samp><A href="../../../reference/api/org/eclipse/rse/files/ui/actions/SystemSelectRemoteFolderAction.html">SystemSelectRemoteFolderAction</A></samp></TD> - </TR> - </TBODY> -</TABLE> - <P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/logger/logPreferences.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/logger/logPreferences.gif Binary files differdeleted file mode 100755 index 9d465a218..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/logger/logPreferences.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/logger/uiLoggerAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/logger/uiLoggerAPI.html deleted file mode 100755 index 4160df436..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/logger/uiLoggerAPI.html +++ /dev/null @@ -1,81 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Logger API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Logger API</h1> -<p>To use the RSE logging framework, you must first decide if you want your own log file, -or want to use the common RSE log file. -</p> - -<h2>Using Your Own Log File</h2> -<p> -The log file support is encapsulated in a separate plugin, <b><samp>org.eclipse.rse.logging</samp></b>, which -defines the primary <samp><A href="../../../reference/api/org/eclipse/rse/logging/Logger.html">org.eclipse.rse.logging.Logger</a></samp> class that manages the log file. -This log file support offers the ability to log the following types of log messages:</p> -<ul> -<li><b>Error</b>. These are serious errors detected by your programming logic. -<li><b>Warning</b>. These are warning situations detected by your programming logic. -<li><b>Information</b>. These are informational messages you want to capture to help with problem determination. -<li><b>Debug</b>. These are trace statements typically only enabled in development drivers. -</ul> - -<p>To define your own logging file, in your plugin class:</p> -<ol> -<li>Define a static variable to hold the Logger instance, as in:<br> -<code>protected static Logger log = null;</code> -<li>Instantiate the Logger object, in your plugin class constructor, as in:<br> - <code>if (log == null) log = LoggerFactory.getLogger(this);</code> -<li>For convenience, offer fastpaths to the logXXX methods in your Logger instance: -<pre> - public static void <b>logInfo</b>(String message) - { - log.logInfo(message); - } - public static void <b>logWarning</b>(String message) - { - log.logWarning(message); - } - public static void <b>logError</b>(String message) - { - log.logError(message, null); - } - public static void <b>logError</b>(String message, Throwable exception) - { - log.logError(message, exception); - } - public static void <b>logDebugMessage</b>(String prefix, String message) - { - log.logDebugMessage(prefix, message); - } -</pre> -<li>In the <samp>shutdown</samp> method of your plugin class, close the log file: -<code>LoggerFactory.freeLogger(this); </code> -</ol> -<p>Typically your code will write a healthy number of messages to the log file, to help you determine -what went wrong in an error situation in production. However, since this can result in a large number of -messages in the log file, it is recommended that you offer the user's a preference page in which they -can specify the types of messages to record in the log file, which should default to error messages only. -In the event of a problem, they can then turn on a more verbose logging option and re-produce the problem, -sending the log file to you for additional information. For example, for the Remote System Explorer, this -preference page is supplied:</p> -<P><IMG border="0" src="logPreferences.gif"></P> - -<h2>Using The Common RSE Log File</h2> -<p>To log your messages to the common RSE log file in <samp>.metadata\plugins\org.eclipse.rse.ui</samp>, -either base your plugin class on the <samp>org.eclipse.rse.core.SystemBasePlugin</samp> class and use -the inherited logging methods, or instead of instantiating your own <samp>Logging</samp> object, re-use the -RSE-supplied logging object by calling <samp>getDefault().getLog()</samp> in the <samp>org.eclipse.rse.ui.RSEUIPlugin</samp> -class. -</p> - - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/massagers/uiMassagersAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/massagers/uiMassagersAPI.html deleted file mode 100755 index 38216f1c0..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/massagers/uiMassagersAPI.html +++ /dev/null @@ -1,54 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Massagers API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Massagers API</h1> -<p>In addition to <a href="../validators/uiValidatorsAPI.html">validating</a> what a user types, we often need -to transform it prior to saving. For example, we may need to fold it to uppercase or lowercase. The RSE abstracts -and encapsulates this concept into massagers which can be re-used. A few are pre-supplied by RSE. -</p> - -<h2>RSE Massager Interfaces</h2> -<p>The <samp><A href="../../../reference/api/org/eclipse/rse/ui/ISystemMassager.html">ISystemMassager</A></samp> interface is in package -<samp><A href="../../../reference/api/org/eclipse/rse/ui/package-summary.html">org.eclipse.rse.ui</A></samp>. -It is a very simple interface with one method: -<samp><A href="../../../reference/api/org/eclipse/rse/ui/ISystemMassager.html#massage(java.lang.String)">public String massage(String text)</A></samp>. -Given input text, return the massaged text. While simple, by encapsulating this operation into an interface, -you will be able to write re-usable dialogs that take a massager as input. Further, tricky massaging can be -built as a re-usable object. -</p> - -<h2>RSE-Supplied Massagers</h2> -<p>The RSE supplies the following massagers in package <samp><A href="../../../reference/api/org/eclipse/rse/ui/package-summary.html">org.eclipse.rse.ui</A></samp>: -</p> -<BR> -<TABLE border="1"> - <TBODY> - <TR> - <TH>Massager Class</TH> - <TH>Description</TH> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/MassagerFoldCase.html">MassagerFoldCase</A></samp></TD> - <TD>Simply folds the text to uppercase or lowercase</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/MassagerFoldCaseOutsideQuotes.html">MassagerFoldCaseOutsideQuotes</A></samp></TD> - <TD>Folds the text to uppercase or lowercase, except parts of the text that are surrounded by quotes or any given delimiter characters</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/MassagerFoldCaseUnlessQuoted.html">MassagerFoldCaseUnlessQuoted</A></samp></TD> - <TD>Folds the text to uppercase or lowercase, unless the whole text is surrounded by quotes or any given delimiter character</TD> - </TR> - </TBODY> -</TABLE> -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgDialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgDialog.gif Binary files differdeleted file mode 100755 index 7098dd018..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgDialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgLine_dialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgLine_dialog.gif Binary files differdeleted file mode 100755 index 846ba78ae..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgLine_dialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgLine_properties.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgLine_properties.gif Binary files differdeleted file mode 100755 index f293841e6..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgLine_properties.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgLine_wizard.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgLine_wizard.gif Binary files differdeleted file mode 100755 index 9b9d58300..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgLine_wizard.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgSample_msgDlg.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgSample_msgDlg.gif Binary files differdeleted file mode 100755 index 36829fe99..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgSample_msgDlg.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgSample_msgline.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgSample_msgline.gif Binary files differdeleted file mode 100755 index 970377d5b..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/msgSample_msgline.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/sampleMessageFile.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/sampleMessageFile.html deleted file mode 100755 index 5888bfc06..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/sampleMessageFile.html +++ /dev/null @@ -1,81 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>Sample Message File</title> -</head> - -<body bgcolor="#ffffff"> -<h1>Sample Message File</h1> -<p>This is an example of a simple message file, say in <samp>sampleMessages.xml</samp>, which has defined messages for only a single component. -<pre> - -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE MessageFile SYSTEM "../org.eclipse.rse.ui/messageFile.dtd"> -<!-- <I>This is an exammple of a message file used by SystemMessage and SystemMessageDialog</I> --> -<MessageFile Version="1.0"> - <Component Name="Samples Plugin" Abbr="<B>SPP</B>"> - <Subcomponent Name="Dialogs" Abbr="<B>D</B>"> - <!-- Component 'D' for dialog sample messages --> - <MessageList> -<A name="SPPD1000"></A> <Message ID="<B>1000</B>" Indicator="E"> - <LevelOne>You must enter a name</LevelOne> - <LevelTwo>You have left the customer name empty. Specify a name.</LevelTwo> - </Message> -<A name="SPPD1001"></A> <Message ID="<B>1001</B>" Indicator="E"> - <LevelOne>You must enter a birth year</LevelOne> - <LevelTwo>You have left the birth year empty. Specify a year.</LevelTwo> - </Message> -<A name="SPPD1002"></A> <Message ID="<B>1002</B>" Indicator="E"> - <LevelOne>%1 is not a valid year</LevelOne> - <LevelTwo>The birth year specified is not within the valid range of %2 to %3.</LevelTwo> - </Message> -<A name="SPPD1003"></A> <Message ID="<B>1003</B>" Indicator="E"> - <LevelOne>Year %1 is out of range</LevelOne> - <LevelTwo>The value you specified for the birth year is not a valid number.</LevelTwo> - </Message> -<A name="SPPD1004"></A> <Message ID="<B>1004</B>" Indicator="E"> - <LevelOne>You must enter a birth month</LevelOne> - <LevelTwo>You have left the birth month empty. Specify a month.</LevelTwo> - </Message> -<A name="SPPD1005"></A> <Message ID="<B>1005</B>" Indicator="E"> - <LevelOne>%1 is not a valid month</LevelOne> - <LevelTwo>The value you specified for the birth month is not a valid number.</LevelTwo> - </Message> -<A name="SPPD1006"></A> <Message ID="<B>1006</B>" Indicator="E"> - <LevelOne>Month %1 is out of range</LevelOne> - <LevelTwo>The birth month specified is not within the valid range of %2 to %3.</LevelTwo> - </Message> -<A name="SPPD1007"></A> <Message ID="<B>1007</B>" Indicator="E"> - <LevelOne>You must enter a birth day</LevelOne> - <LevelTwo>You have left the birth day empty. Specify a day.</LevelTwo> - </Message> -<A name="SPPD1008"></A> <Message ID="<B>1008</B>" Indicator="E"> - <LevelOne>%1 is not a valid day</LevelOne> - <LevelTwo>The value you specified for the birth day is not a valid number.</LevelTwo> - </Message> -<A name="SPPD1009"></A> <Message ID="<B>1009</B>" Indicator="E"> - <LevelOne>Day %1 is out of range</LevelOne> - <LevelTwo>The birth day specified is not within the valid range of %2 to %3.</LevelTwo> - </Message> -<A name="SPPD1010"></A> <Message ID="<B>1010</B>" Indicator="I"> - <LevelOne>Customer %1 created successfully. Re-run to see update mode.</LevelOne> - <LevelTwo>The customer was created. Re-running the same sample action will show the dialog in update mode.</LevelTwo> - </Message> -<A name="SPPD1011"></A> <Message ID="<B>1011</B>" Indicator="I"> - <LevelOne>Customer %1 updated successfully.</LevelOne> - <LevelTwo>Congratulations!</LevelTwo> - </Message> - </MessageList> - </Subcomponent> - </Component> -</MessageFile> -</pre> - - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/uiMessageAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/uiMessageAPI.html deleted file mode 100755 index 8018d11cc..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/uiMessageAPI.html +++ /dev/null @@ -1,154 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Message API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Message API</h1> -<p>To work with messages, which are defined in an xml <a href="uiMessageFile.html">message file</a>, -you use: -</p> -<ul> -<li>Static methods in the -<samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html"org.eclipse.rse.core.SystemBasePlugin</A></samp> -class to load the message file and extract messages from it. -<li>Classes in the -<samp><A href="../../../reference/api/org/eclipse/rse/ui/messages/package-summary.html">org.eclipse.rse.ui.messages</A></samp> -package to do variable substitution, and display the messages to the user. -</ul> - -<h2>Methods for Parsing the Message File</h2> -<p>Once you have defined your message file, you must update your plugin class to load it at startup time. -To do this, simply call the static method -<samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#loadMessageFile(org.eclipse.core.runtime.IPluginDescriptor, java.lang.String)">loadMessageFile</a></samp> -in the RSE-supplied <samp><a href="../plugin/uiPluginAPI.html">SystemBasePlugin</a></samp> class. -<BR> -<BR> -After the message file is loaded into memory, you can extract messages from it by calling the static method -<samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getMessage(org.eclipse.rse.ui.messages.SystemMessageFile, java.lang.String)">getMessage</a></samp> -from the same <samp><a href="../plugin/uiPluginAPI.html">SystemBasePlugin</a></samp> class. -</p> - -<h2>Classes for Displaying Messages</h2> -<p>The following classes are all defined in the <samp><A href="../../../reference/api/org/eclipse/rse/ui/messages/package-summary.html">org.eclipse.rse.ui.messages</a></samp> package. </p> - -<h3><A name="SystemMessageFile"></A>The <samp>SystemMessageFile</samp> Class</h3> -<p>The <samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#loadMessageFile(org.eclipse.core.runtime.IPluginDescriptor, java.lang.String)">loadMessageFile</a></samp> method in <samp>SystemBasePlugin</samp>, returns an instance of -<samp><A href="../../../reference/api/org/eclipse/rse/services/clientserver/messages/SystemMessageFile.html">SystemMessageFile</a></samp>, -representing the parsed message file. It is methods in this which return individual messages. -<h3><A name="SystemMessage"></A>The <samp>SystemMessage</samp> Class</h3> -The <samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getMessage(org.eclipse.rse.ui.messages.SystemMessageFile, java.lang.String)">getMessage</a></samp> method in <samp>SystemBasePlugin</samp> returns an instance of -<samp><A href="../../../reference/api/org/eclipse/rse/services/clientserver/messages/SystemMessage.html">SystemMessage</a></samp>, -representing an individual message from the message file. -</p> -<p>To do message <i>variable substitution</i>, call the appropriate overload of the <samp>makeSubstitution</samp> method in -the <A href="../../../reference/api/org/eclipse/rse/services/clientserver/messages/SystemMessage.html">message</A> object, passing as many parameters as there are unique substitution variables in the message. -</p> -<p>To get the first level message text, call <samp><A href="../../../reference/api/org/eclipse/rse/services/clientserver/messages/SystemMessage.html#getLevelOneText()">getLevelOneText</a></samp> on the message object. To get -the second level help, call <samp><A href="../../../reference/api/org/eclipse/rse/services/clientserver/messages/SystemMessage.html#getLevelTwoText()">getLevelTwoText</a></samp>. -</p> - -<h3><A name="SystemMessageDialog"></A>The <samp>SystemMessageDialog</samp> Class</h3> -<p>To display a message in a dialog, instantiate <samp><A href="../../../reference/api/org/eclipse/rse/ui/messages/SystemMessageDialog.html">SystemMessageDialog</a></samp>, passing -in a parent shell and the message object, and then call the appropriate <samp><A href="../../../reference/api/org/eclipse/rse/ui/messages/SystemMessageDialog.html#open()">open</a></samp> method in the dialog object. Here is what the message -dialog looks like, for a message of type Error (the type dictates the error icon): -</p> -<P><IMG border="0" src="msgDialog.gif" width="457" height="190"></P> - -<h3><A name="ISystemMessageLine"></A>The <samp>ISystemMessageLine</samp> Interface</h3> -<p>If you are extending the RSE class <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html">SystemPromptDialog</a></samp> for dialogs, -or <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizardPage.html">AbstractSystemWizardPage</a></samp> for wizard pages -or <samp><A href="../../../reference/api/org/eclipse/rse/ui/propertypages/SystemBasePropertyPage.html">SystemBasePropertyPage</a></samp> for property pages, you can display the message to the -user by calling the <samp><A href="../../../reference/api/org/eclipse/rse/ui/messages/ISystemMessageLine.html#setErrorMessage(org.eclipse.rse.ui.messages.SystemMessage)">setErrorMessage</a></samp> method all these classes support. These classes all implement -the interface <b><samp><A href="../../../reference/api/org/eclipse/rse/ui/messages/ISystemMessageLine.html">ISystemMessageLine</a></samp></b>, which also includes the method <samp>clearErrorMessage</samp>. For non-error -messages, use <samp><A href="../../../reference/api/org/eclipse/rse/ui/messages/ISystemMessageLine.html#setMessage(org.eclipse.rse.ui.messages.SystemMessage)">setMessage</a></samp> -and <samp><A href="../../../reference/api/org/eclipse/rse/ui/messages/ISystemMessageLine.html#clearMessage()">clearMessage</a></samp>.</p> -<p> -Here is what a system message issued in a <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemPromptDialog.html">SystemPromptDialog</a></samp> dialog looks like:</p> -<P><IMG border="0" src="msgLine_dialog.gif" width="264" height="125"></P> -<p>The user can select the question mark icon on the right to see the full message dialog, and hence access the second level help for the message. -<p>Here is what a system message issued in an <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizardPage.html">AbstractSystemWizardPage</a></samp> looks like:</p> -<P><IMG border="0" src="msgLine_wizard.gif" width="439" height="98"></P> -<p>If the user clicks the mouse on the message or icon, they will see the full message dialog for the message.</p> - -<p>Here is what a system message issued in a <samp><A href="../../../reference/api/org/eclipse/rse/ui/propertypages/SystemBasePropertyPage.html">SystemBasePropertyPage</a></samp> looks like:</p> -<P><IMG border="0" src="msgLine_properties.gif" width="491" height="75"></P> -<p>Again, if the user clicks the mouse on the message or icon, they will see the full message dialog for the message.</p> - -<h2>Classes for Displaying Message Exceptions</h2> -<p>The following class is defined in the <samp><A href="../../../reference/api/org/eclipse/rse/services/clientserver/messages/package-summary.html">org.eclipse.rse.services.clientserver.messages</a></samp> package. - -<h3>The <samp>SystemMessageDialog</samp> Class</h3> -<p>Many of the RSE APIs throw <samp><A href="../../../reference/api/org/eclipse/rse/services/clientserver/messages/SystemMessageException.html">org.eclipse.rse.services.clientserver.messages.SystemMessageException</a></samp>, which -encapsulates a system message object. To get the encapsulated message, call <samp><A href="../../../reference/api/org/eclipse/rse/services/clientserver/messages/SystemMessageException.html#getSystemMessage()">getSystemMessage()</a></samp>. -To display the message in an RSE message dialog box, simply call <samp><A href="../../../reference/api/org/eclipse/rse/services/clientserver/messages/SystemMessageException.html#displayMessage()">displayMessage()</a></samp> on the exception object. -To get the first-level text, call <samp>getMessage()</samp>, or <samp>getSystemMessage().getLevelOneText()</samp> -</p> - -<h1>Message Example</h1> -<h2>Declaring the Messages</h2> -<p>Declare the messages via the <samp>Message</samp> tag in a <a href="uiMessageFile.html">message file</a>, such as <samp>sampleMessages.xml</samp> -<pre><?xml version="1.0" encoding='UTF-8'?> -<!DOCTYPE MessageFile SYSTEM "../org.eclipse.rse.ui/messageFile.dtd"> -<!-- This is an exammple of a message file used by SystemMessage and SystemMessageDialog --> -<MessageFile Version="1.0"> - <Component Name="Samples Plugin" Abbr="<B>SPP</B>"> - <Subcomponent Name="Dialogs" Abbr="<B>D</B>"> - <!-- Component 'D' for dialog sample messages --> - <MessageList> - <Message ID="<B>1003</B>" Indicator="E"> - <LevelOne>%1 is not a valid year</LevelOne> - <LevelTwo>The birth year specified is not within the valid range of %2 to %3.</LevelTwo> - </Message> - <!-- <I>repeat Message elements as needed</I> --> - </MessageList> - </Subcomponent> - </Component> -</MessageFile> -</pre> - -<h2>Processing the Message File</h2> -In your plugin class, declare a message file static variable, load the message file in the constructor, and -supply a static method for retrieving a message from the file. -<pre>import org.eclipse.rse.ui.messages.*; // <I>for message file classes</I> -import org.eclipse.rse.core.*; // <I>for SystemBasePlugin</I> -<B>...</B> -private static SystemMessageFile messageFile = null; -<B>...</B> -messageFile = SystemBasePlugin.loadMessageFile(descriptor, "sampleMessages.xml"); // <I>in constructor</I> -<B>...</B> - -/** - * <I>Retrieve a message from this plugin's message file</I> - * <I>@param msgId - the ID of the message to retrieve. This is the concatenation of the</I> - * <I>message's component abbreviation, subcomponent abbreviation, and message ID as declared</I> - * <I>in the message xml file.</I> - */ -<A name="getPluginMessage"></A>public static SystemMessage <B>getPluginMessage</B>(String msgId) -{ - return SystemBasePlugin.getMessage(messageFile, msgId); -}</pre> - -<h2>Retrieving the Message</h2> -<pre>SystemMessage errorMessage = SamplesPlugin.getPluginMessage("SPPD1003"); -errorMessage.makeSubstitution(input, "1900", "2003");</pre> - -<h2>Displaying the Message</h2> -<h3>On a Message Line</h3> -<pre>setErrorMessage(errorMessage);</pre> - -<P><IMG border="0" src="msgSample_msgline.gif" width="227" height="208"></P> -<h3>In a Message Dialog</h3> -<pre>SystemMessageDialog msgDlg = new SystemMessageDialog(shell, errorMessage);</br>msgDlg.open(); // <I>to open with details not showing</I> -//msgDlg.openWithDetails(); // <I>to open with details already showing</I> </pre> - -<P><IMG border="0" src="msgSample_msgDlg.gif" width="457" height="190"></P> -<P><BR> -</P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/uiMessageFile.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/uiMessageFile.html deleted file mode 100755 index af83cab09..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/uiMessageFile.html +++ /dev/null @@ -1,79 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css">
-<title>RSE Message File</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>RSE Message File</h1>
-<p>To exploit the message framework in RSE, you start by create an message file, named
-say <samp>mymessages.xml</samp>, which looks something like this:
-<pre>
-<?xml version="1.0" encoding='UTF-8'?>
-<!-- This is a sample message file -->
-<MessageFile Version="1.0">
- <Component Name="ACME Tools" Abbr="ACME">
- <Subcomponent Name="General" Abbr="G">
- <MessageList>
- <Message ID="1001" Indicator="E">
- <LevelOne>You made a mistake</LevelOne>
- <LevelTwo>Fix your mistake, then re-attempt the operation.</LevelTwo>
- </Message>
- </MessageList>
- </Subcomponent>
- </Component>
-</MessageFile>
-</pre>
-
-<h2>RSE Message File Elements</h2>
-<p>Typically, this file is created in plugin project's root folder.</p>
-<p>The important elements in this file are:
-</p><TABLE border="1">
- <TBODY>
- <TR>
- <TH>Element</TH>
- <TH>Description</TH>
- </TR>
- <TR>
- <TD>MessageFile</TD>
- <TD>The overall element for the file. There is only one of these tags.</TD>
- </TR>
- <TR>
- <TD>Component</TD>
- <TD>Identifies a course-grained component within your plugin. You can specify multiple component tags. It is up to you to decide<BR>how many components to divide your plugin into. The abbreviation (Abbr) of the component constitutes the first part of the message ID for messages defined in this component, aiding in servicing when an error message is reported.
- </TD>
- </TR>
- <TR>
- <TD>Subcomponent</TD>
- <TD>Identifies a fine-grained subcomponent within a component. The abbreviation (Abbr) of the subcomponent is appended to the component's abbreviation when the message ID is created for messages in this subcomponent. It is up to you to decide how many subcomponents to divide your component into, and what to name them.</TD>
- </TR>
- <TR>
- <TD>MessageList</TD>
- <TD>Simply encapsulates the list of Message elements for this subcomponent.</TD>
- </TR>
- <TR>
- <TD>Message</TD>
- <TD>Defines a message. <BR>
- The <b>ID</b> attribute can be anything you like, but following a naming or numbering convention is a good idea. The ID is appended to the component and subcomponent abbreviations to form the message ID the user will see.
- <BR>The <b>Indicator</b> attribute identifies the severity of the message: <b>I</b> for Information, <b>E</b> for Error, <b>W</b> for Warning, <b>U</b> for Unexpected, and <b>Q</b> for Question. This affects the icon that will be used for this message, and the buttons allowed on the message dialog.
- </TD>
- </TR>
- <TR>
- <TD>LevelOne</TD>
- <TD>The first-level message the user will initially see. Use %n for substitution variables, where n is a positive integer incrementing up from 1.</TD>
- </TR>
- <TR>
- <TD>LevelTwo</TD>
- <TD>The second-level help for the message, the user will only see if they ask to see it. Use %n for substitution variables. Any variable used here and in the LevelOne text will be consistently substituted with the same value.</TD>
- </TR>
- </TBODY>
-</TABLE>
-
-<h2>RSE Message File Sample</h2>
-<p>This is a bigger <A href="sampleMessageFile.html">sample</A>.</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/uiMessagesCore.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/uiMessagesCore.html deleted file mode 100755 index 5f03ed71a..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/messages/uiMessagesCore.html +++ /dev/null @@ -1,1010 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css">
-<TITLE> Message File systemmessages.xml </TITLE>
-<style type="text/css">
-h2 { background-color: #CCCCFF }
-</style>
-</HEAD>
-<BODY>
-<H1>Remote Systems Explorer Messages</H1>
-<br>
-<TABLE BORDER="1" CELLPADDING="3" CELLSPACING="0" WIDTH="100%">
-<TR BGCOLOR="#CCCCFF">
-<TD COLSPAN=2><FONT SIZE="+2">
-<B>Sub-Component Summary</B></FONT></TD>
-</TR>
-<TR BGCOLOR="white">
-<TD ALIGN="right" VALIGN="top" WIDTH="1%">
-<A href=#General>General</A></TD>
-<TD><b>Message prefix</b>=RSEG</TD></TR>
-<TR BGCOLOR="white">
-<TD ALIGN="right" VALIGN="top" WIDTH="1%">
-<A href=#Other>Other</A></TD>
-<TD><b>Message prefix</b>=RSEO</TD></TR>
-<TR BGCOLOR="white">
-<TD ALIGN="right" VALIGN="top" WIDTH="1%">
-<A href=#Files>Files</A></TD>
-<TD><b>Message prefix</b>=RSEF</TD></TR>
-<TR BGCOLOR="white">
-<TD ALIGN="right" VALIGN="top" WIDTH="1%">
-<A href=#Communications>Communications</A></TD>
-<TD><b>Message prefix</b>=RSEC</TD></TR>
-</TABLE>
-<A NAME="General"><!-- --></A><H2>General Messages</H2>
-<H3>RSEG1001</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>Under construction<br>
-<b>LevelTwo: </b>This function is not yet available.<br>
-<H3>RSEG1002</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>This will reload the Remote System Explorer. Are you sure?<br>
-<b>LevelTwo: </b>This action should only be used after receiving files from a team repository. It reloads the RSE from the workspace, incorporating the new files.<br>
-<H3>RSEG1003</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>An unexpected exception has occurred<br>
-<b>LevelTwo: </b>%1<br>
-<H3>RSEG1006</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter name<br>
-<b>LevelTwo: </b>You must enter a name in the field where the cursor is positioned.<br>
-<H3>RSEG1007</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Name in use<br>
-<b>LevelTwo: </b>This name is already used by another resource. Enter a unique name.<br>
-<H3>RSEG1008</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Name not valid<br>
-<b>LevelTwo: </b>The name entered does not have valid syntax<br>
-<H3>RSEG1009</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>You must rename %1<br>
-<b>LevelTwo: </b>You have left the new name the same as the old name. Enter a new name that is different from the old name.<br>
-<H3>RSEG1010</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Name %1 is specified more than once<br>
-<b>LevelTwo: </b>Two or more resources have been renamed to the same new name. Each resource must have a unique name.<br>
-<H3>RSEG1011</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Name %1 not valid<br>
-<b>LevelTwo: </b>The name %1 does not have valid syntax<br>
-<H3>RSEG1012</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter new name<br>
-<b>LevelTwo: </b>You have the new name entry field empty. You must enter a unique new name.<br>
-<H3>RSEG1013</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Expand failed or canceled. Try again.<br>
-<b>LevelTwo: </b>When expanding a node in the tree, and retrieving the resources, either an error occurred or you cancelled the operation. The expand is cancelled.<br>
-<H3>RSEG1014</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter profile name<br>
-<b>LevelTwo: </b>You must enter a name for the profile. Profiles contain all connections, filters and user defined actions. They are shared by the team, but each team member sees only those profiles which are active. Each profile can be private to you, or used by the whole team if all team members make the profile active. The name should reflect this. That is, if the profile is to be private to you, pick a name that is least likely to collide with a name chosen by other team members.<br>
-<H3>RSEG1015</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Profile of that name already exists<br>
-<b>LevelTwo: </b>There is already a profile of that name. Choose a unique name for the profile.<br>
-<H3>RSEG1016</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Not a valid profile name<br>
-<b>LevelTwo: </b>Profiles ultimate are folders in the file system, so profile names must be valid folder names for the workbench. Further, they must not contain pound signs (#) or exceed 100 characters in length. Profile names are not case sensitive, but are case tolerant.<br>
-<H3>RSEG1017</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter number<br>
-<b>LevelTwo: </b>The value %1 you entered is not numeric. Enter only numeric input.<br>
-<H3>RSEG1018</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Name not valid as folder name<br>
-<b>LevelTwo: </b>The name must be a valid folder name within the workbench and the underlying file system.<br>
-<H3>RSEG1019</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Name not valid as file name<br>
-<b>LevelTwo: </b>The name must be a valid file name within the workbench and the underlying file system.<br>
-<H3>RSEG1020</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter system type<br>
-<b>LevelTwo: </b>You must select a system type. The system type is the type of the operating system of the remote sytem.<br>
-<H3>RSEG1021</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter connection name<br>
-<b>LevelTwo: </b>You must enter a connection name. This name is arbitrary, but must be unique to the selected profile.<br>
-<H3>RSEG1022</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Connection name is not unique for its profile<br>
-<b>LevelTwo: </b>Connection names must be unique to the profile that contains the connection. Specify a name not already in use.<br>
-<H3>RSEG1023</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Not a valid connection name<br>
-<b>LevelTwo: </b>The connection name is not syntactically valid. The name must be a valid folder name within the workbench and the underlying file system.<br>
-<H3>RSEG1024</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter host name or ip address<br>
-<b>LevelTwo: </b>You must specify a host name or TCP/IP address for the remote system.<br>
-<H3>RSEG1025</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter user ID<br>
-<b>LevelTwo: </b>You must specify a user ID to be used to connect to the system.<br>
-<H3>RSEG1026</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Not a valid user ID<br>
-<b>LevelTwo: </b>The user ID entered is not syntactically valid. The only restriction for a user ID is that it not use the characters '=' or ';'.<br>
-<H3>RSEG1027</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter port number<br>
-<b>LevelTwo: </b>You must specify a port number that is used to connect with the server-side communication layer.<br>
-<H3>RSEG1028</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Not a valid port number<br>
-<b>LevelTwo: </b>The value you entered is not a valid port number. It must be a positive integer.<br>
-<H3>RSEG1029</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter value<br>
-<b>LevelTwo: </b>You must enter a value in the field where the cursor is.<br>
-<H3>RSEG1030</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Entry is not unique<br>
-<b>LevelTwo: </b>The value you entered is already in use. Specify a value that is not already in use.<br>
-<H3>RSEG1031</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Syntax is not valid<br>
-<b>LevelTwo: </b>The syntax of the value at the cursor position is not valid.<br>
-<H3>RSEG1032</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter path<br>
-<b>LevelTwo: </b>You must specify a file system path.<br>
-<H3>RSEG1033</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Path is not unique<br>
-<b>LevelTwo: </b>The path you specified is already in use.<br>
-<H3>RSEG1034</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Path syntax is not valid<br>
-<b>LevelTwo: </b>The syntax of the path you specified is not valid. Enter a file system path that is valid for the remote operating system.<br>
-<H3>RSEG1035</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter password<br>
-<b>LevelTwo: </b>You must specify your password.<br>
-<H3>RSEG1036</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Password has expired<br>
-<b>LevelTwo: </b>Your password has expired, and must be reset before continuing.<br>
-<H3>RSEG1037</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter filter pool name<br>
-<b>LevelTwo: </b>You must specify a name for your filter pool. Filter pool names are arbitrary, but typically reflect the contents of the filters, such as "Release 1" or "Accounts Payable".<br>
-<H3>RSEG1038</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter pool name already exists in this profile<br>
-<b>LevelTwo: </b>A filter pool with this name already exists in the profile.<br>
-<H3>RSEG1039</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter pool name not valid<br>
-<b>LevelTwo: </b>The filter pool name you specified is not a valid name. The name must be a valid folder name in the workbench, and must not contain the pound sign '#'. It must also not exceed 50 characters in length.<br>
-<H3>RSEG1040</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Profile name %1 is reserved<br>
-<b>LevelTwo: </b>The given profile name is reserved by IBM. Specify another name for the profile.<br>
-<H3>RSEG1042</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter filter name<br>
-<b>LevelTwo: </b>You must specify a name for your filter. You can specify any name you like. Choose a name that tells others the contents of this filter. For example, "Source Files for Release 1".<br>
-<H3>RSEG1043</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter name already exists in this filter pool<br>
-<b>LevelTwo: </b>The filter name you specified is in use. You must specify a name unique for the parent filter pool.<br>
-<H3>RSEG1044</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter name not valid<br>
-<b>LevelTwo: </b>The filter name you specified is not a valid name. The name must be a valid file name in the workbench, and must not contain the pound sign '#'. It must also not exceed 100 characters in length.<br>
-<H3>RSEG1045</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter filtering information<br>
-<b>LevelTwo: </b>You must specify filtering information<br>
-<H3>RSEG1046</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter string already exists<br>
-<b>LevelTwo: </b>You specified a filter string which already exists in this filter. Having duplicate filter strings will result in duplicate resources in the expanded filter. Specify unique filter strings, preferably which result in unique resources. For example, don't specify both ABC* and A*.<br>
-<H3>RSEG1047</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter string not valid<br>
-<b>LevelTwo: </b>The filter string you specified is not syntactically correct.<br>
-<H3>RSEG1048</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Duplicate filter string '%1'.<br>
-<b>LevelTwo: </b>You have defined the same filter string twice or more. This will result in multiple copies of the same resource, when this filter is expanded. Delete the redundant filter strings.<br>
-<H3>RSEG1049</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter string '%1' already exists in filter %2<br>
-<b>LevelTwo: </b>This filter string cannot be copied or moved to the target filter. The same filter string already exists there<br>
-<H3>RSEG1050</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>Save to disk failed with an unexpected exception<br>
-<b>LevelTwo: </b>%1<br>
-<H3>RSEG1051</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>Restore of data failed with unexpected exception<br>
-<b>LevelTwo: </b>%1<br>
-<H3>RSEG1052</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>Delete selected resources?<br>
-<b>LevelTwo: </b>This is a permanent deletion of the selected resources and cannot be undone<br>
-<H3>RSEG1053</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>Delete profile '%1'?<br>
-<b>LevelTwo: </b>Do you want to delete this profile, including all of its connections, filters and user actions? Select Yes to delete, or No to cancel the delete request<br>
-<H3>RSEG1054</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Connecting to %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1055</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Connecting to %1 at port %2<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1056</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>Connect to %1 failed with an unexpected exception<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEG1057</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Connect failed. Host %1 not found or not responding<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1058</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Connect to %1 was cancelled<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1059</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Disconnecting from %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1060</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Disconnecting from %1 at port %2<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1061</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>Disconnect from %1 failed with exception<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEG1062</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Disconnect from %1 was cancelled<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1063</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>Unexpected error deleting %1<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEG1064</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>Unexpected error renaming %1<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEG1065</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Unexpected error moving %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1066</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>Operation failed with exception '%1'<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1067</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Operation cancelled.<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1068</H3>
-<b>Severity: </b>Warning<br>
-<b>LevelOne: </b>Warning. Profile '%1' should be made active. Active connection '%2' contains a reference to it.<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1069</H3>
-<b>Severity: </b>Warning<br>
-<b>LevelOne: </b>Warning. Profile '%1' should be active. Active connection '%2' contains a reference to it.<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1070</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Resolving %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1071</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Running %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1072</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying '%1' to '%2'<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1073</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying connection %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1074</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying connections<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1075</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying filter pools<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1076</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying filter pool %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1077</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying filters<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1078</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying filter %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1079</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying filter strings<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1080</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying filter string %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1081</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying subsystems<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1082</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Filter pool(s) successfully copied to '%1'. You must create a new filter pool reference to see it (them).<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1083</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Moving '%1' to '%2'<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1084</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Moving connection %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1085</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Moving connections<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1086</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Moving filter pools<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1087</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Moving filter pool %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1088</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Moving filters<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1089</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Moving filter %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1090</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Moving filter strings<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1091</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Moving filter string %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1092</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Filter pool(s) successfully moved to '%1'. You must create a new filter pool reference to see it (them).<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1093</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Setting %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1094</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Setting properties<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1095</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Querying %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1096</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Querying properties<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1097</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Running %1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1098</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Expand failed. Try again<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1099</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Expand cancelled. Try again<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1100</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Empty list<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1101</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>List cancelled<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1102</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Filter created successfully. Expand this again to create another<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1103</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Connection %1 not found<br>
-<b>LevelTwo: </b>No connection named %1 currently exists<br>
-<H3>RSEG1104</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Profile %1 not found<br>
-<b>LevelTwo: </b>No profile named %1 currently exists<br>
-<H3>RSEG1105</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Folder %1 not found on host %2<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1106</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>File %1 not found on host %2<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1107</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>File or folder %1 not found on host %2<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1108</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Connection created successfully. Expand this again to create another<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1109</H3>
-<b>Severity: </b>Warning<br>
-<b>LevelOne: </b>Connection busy<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1110</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Command interrupted<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1111</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Unable to run command<br>
-<b>LevelTwo: </b>Possible causes: connection has been deleted, connection has been renamed, or connection has been disconnected<br>
-<H3>RSEG1112</H3>
-<b>Severity: </b>Warning<br>
-<b>LevelOne: </b>Command cancelled<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1115</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying...<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1116</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Moving...<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1117</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Copying %1...<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1118</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Moving %1...<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1130</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>Permanently delete selected remote resource(s)?<br>
-<b>LevelTwo: </b>This is a permanent deletion of the selected remote resources from disk. This action cannot be undone<br>
-<H3>RSEG1140</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>Error occurred while loading the user-defined action information from file: %1<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEG1141</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>The xml file '%1' appears to be corrupted. It has been replaced<br>
-<b>LevelTwo: </b>Expected root tag to be named '%2'. The corrupted file has been renamed to '%3' and a new file created for you<br>
-<H3>RSEG1150</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Unable to perform action as the underlying file system folder is in use<br>
-<b>LevelTwo: </b>The file system folder %1 is in use by another task and cannot be removed or modified<br>
-<H3>RSEG1151</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Unable to perform action as the underlying file system file is in use<br>
-<b>LevelTwo: </b>The file system file %1 is in use by another task and cannot be removed or modified<br>
-<H3>RSEG1160</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>Filter pool %1 created. Create a reference to it in the selected subsystem?<br>
-<b>LevelTwo: </b>New filter pools are not accessible until a reference is added to them in a subsystem. Select Yes to add a reference to the new filter pool in selected subsystem %2<br>
-<H3>RSEG1161</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter update failed: %1<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEG1162</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter rename failed: %1<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEG1170</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter numeric value<br>
-<b>LevelTwo: </b>You must enter a numeric value<br>
-<H3>RSEG1171</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Value %1 not numeric<br>
-<b>LevelTwo: </b>The value specified is not a valid number<br>
-<H3>RSEG1172</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Value %1 not in range<br>
-<b>LevelTwo: </b>The value specified is not within the valid range of %2 to %3<br>
-<H3>RSEG1180</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter action name<br>
-<b>LevelTwo: </b>You must enter a name for this action<br>
-<H3>RSEG1181</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Action name is not unique<br>
-<b>LevelTwo: </b>There is already an action with the given name in the selected profile. Specify a name that is not already in use<br>
-<H3>RSEG1182</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Action name is not valid<br>
-<b>LevelTwo: </b>The given name is not a valid action name<br>
-<H3>RSEG1183</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter comment<br>
-<b>LevelTwo: </b>You must enter a comment for this action<br>
-<H3>RSEG1184</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Action comment is not valid<br>
-<b>LevelTwo: </b>The given comment has syntactical errors<br>
-<H3>RSEG1185</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter command<br>
-<b>LevelTwo: </b>You must enter a command for this action<br>
-<H3>RSEG1186</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Action command is not valid<br>
-<b>LevelTwo: </b>The given command has syntactical errors<br>
-<H3>RSEG1187</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter type name<br>
-<b>LevelTwo: </b>You must enter a name for this collection of resource types<br>
-<H3>RSEG1188</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Type name %1 in use<br>
-<b>LevelTwo: </b>There is already a named type with the given name. Specify a name that is not already in use<br>
-<H3>RSEG1189</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Type name %1 is not valid<br>
-<b>LevelTwo: </b>The given name is not valid for a named type. It must not contain blanks<br>
-<H3>RSEG1190</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Specify one or more resource types<br>
-<b>LevelTwo: </b>You must specify one or more simple or generic resource types to constitute this named type<br>
-<H3>RSEG1191</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Types not valid<br>
-<b>LevelTwo: </b>Syntactical errors were found in the list of resource types<br>
-<H3>RSEG1192</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter source type<br>
-<b>LevelTwo: </b>You must enter a source type<br>
-<H3>RSEG1193</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Source type "%1" not valid<br>
-<b>LevelTwo: </b>The source type you entered is not valid.<br>
-<H3>RSEG1194</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Source type "%1" already exists<br>
-<b>LevelTwo: </b>The source type you entered has already been specified. Specify a unique source type.<br>
-<H3>RSEG1195</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter a label for this compile command<br>
-<b>LevelTwo: </b>You must enter a label for this compile command, that will be shown in menus and lists<br>
-<H3>RSEG1196</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Compile command label "%1" is in use<br>
-<b>LevelTwo: </b>There is already a compile command with the given label. Specify a label that is not already in use<br>
-<H3>RSEG1197</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Compile command label "%1" is not valid<br>
-<b>LevelTwo: </b>The given label is not a valid compile label<br>
-<H3>RSEG1198</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter command string for this compile command<br>
-<b>LevelTwo: </b>You must enter a command string for this compile command. This is what is run when this compile command is selected.<br>
-<H3>RSEG1199</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Compile command string "%1" is not valid<br>
-<b>LevelTwo: </b>The given string is not a valid command.<br>
-<H3>RSEG1201</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>Changes pending. Save changes?<br>
-<b>LevelTwo: </b>You have changes pending. Select Yes to save those changes. Select No to discard those changes<br>
-<H3>RSEG1202</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>Changes pending. Continue?<br>
-<b>LevelTwo: </b>You have changes pending. Select Yes to discard those changes. Select No to cancel the operation so you can first save your changes<br>
-<H3>RSEG1220</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Host name '%1' not found or valid<br>
-<b>LevelTwo: </b>A remote system of host name '%1' was found. If you are working disconnected, de-select the checkbox to verify the host name<br>
-<H3>RSEG1221</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Verifying host name...<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1230</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>Delete selected user actions?<br>
-<b>LevelTwo: </b>This is a permanent deletion of the selected actions and cannot be undone.Select Yes to delete and No to cancel the delete action<br>
-<H3>RSEG1231</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>Delete selected types?<br>
-<b>LevelTwo: </b>This is a permanent deletion of the selected types and cannot be undone.Select Yes to delete and No to cancel the delete action<br>
-<H3>RSEG1240</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>There is an error on another page<br>
-<b>LevelTwo: </b>Another page of the wizard has an error that must be corrected before the wizard can be finished<br>
-<H3>RSEG1250</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>The pattern may not be blank<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1251</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Invalid regular expression<br>
-<b>LevelTwo: </b>The value %1 you entered is not a valid regular expression<br>
-<H3>RSEG1255</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>%1 - Running<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1256</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>%1 - Finished<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1260</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>The invocation may not be blank<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1270</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Invalid drag and drop operation<br>
-<b>LevelTwo: </b>The source %1 cannot be transferred into the target %2<br>
-<H3>RSEG1300</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>The FTP service is unavailable on the remote system.<br>
-<b>LevelTwo: </b>The RSE server needs to be installed manually.<br>
-<H3>RSEG1301</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>The Telnet service is unavailable on the remote system.<br>
-<b>LevelTwo: </b>The RSE server needs to be started manually or a system administrator needs to install the RSE daemon.<br>
-<H3>RSEG1302</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Unable to start the RSE server.<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1303</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Unable to install the RSE server.<br>
-<b>LevelTwo: </b><br>
-<H3>RSEG1400</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>This action will take a few minutes. Proceed?<br>
-<b>LevelTwo: </b>This action uncompresses a large number of HTML files from a zip file. It will take awhile, and require sufficient disk space. Press Yes to continue, No to cancel.<br>
-<H3>RSEG1401</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Classic help already enabled.<br>
-<b>LevelTwo: </b>The HTML files for the CODE and VisualAge RPG help have already been uncompressed.<br>
-<br>
-<hr>
-<A NAME="Other"><!-- --></A><H2>Other Messages</H2>
-<H3>RSEO1000</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>%1<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEO1001</H3>
-<b>Severity: </b>Warning<br>
-<b>LevelOne: </b>%1<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEO1002</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>%1<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEO1003</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>%1<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEO1004</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>%1<br>
-<b>LevelTwo: </b>%2<br>
-<H3>RSEO1005</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>%1: %2<br>
-<b>LevelTwo: </b>%3<br>
-<H3>RSEO1006</H3>
-<b>Severity: </b>Warning<br>
-<b>LevelOne: </b>%1: %2<br>
-<b>LevelTwo: </b>%3<br>
-<H3>RSEO1007</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>%1: %2<br>
-<b>LevelTwo: </b>%3<br>
-<H3>RSEO1008</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>%1: %2<br>
-<b>LevelTwo: </b>%3<br>
-<H3>RSEO1009</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>%1: %2<br>
-<b>LevelTwo: </b>%3<br>
-<H3>RSEO1010</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>%1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEO1011</H3>
-<b>Severity: </b>Warning<br>
-<b>LevelOne: </b>%1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEO1012</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>%1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEO1013</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>%1<br>
-<b>LevelTwo: </b><br>
-<H3>RSEO1014</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>%1<br>
-<b>LevelTwo: </b><br>
-<br>
-<hr>
-<A NAME="Files"><!-- --></A><H2>Files Messages</H2>
-<H3>RSEF1001</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Operation failed. Security violation<br>
-<b>LevelTwo: </b>Message reported from file system: %1<br>
-<H3>RSEF1002</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Operation failed. File system input or output error<br>
-<b>LevelTwo: </b>Message reported from file system: %1<br>
-<H3>RSEF1003</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Folder is not empty. Cannot delete<br>
-<b>LevelTwo: </b>The operation failed. One possible reason is that the folder is not empty<br>
-<H3>RSEF1004</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Folder '%1' not found<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1005</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>Folder '%1' not found. Would you like to create it?<br>
-<b>LevelTwo: </b>The folder you specified does not exist. Select Yes to create it, No to cancel the operation<br>
-<H3>RSEF1006</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>File '%' not found<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1011</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter file name pattern<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1007</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter string '%1' already exists in this filter<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1008</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Filter string name pattern not valid<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1009</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>You must include files or folders or both<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1010</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>No file types specified<br>
-<b>LevelTwo: </b>Either specify one or more file types, or select to subset by file name<br>
-<H3>RSEF1200</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Create a new File<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1201</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Create a new Folder<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1202</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Enter folder name<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1203</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Names cannot begin or end with whitespace.<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1204</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>%1 is an invalid character in a name.<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1205</H3>
-<b>Severity: </b>Information<br>
-<b>LevelOne: </b>Enter file name<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF1300</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Deletion of the object %1 failed<br>
-<b>LevelTwo: </b>Either the object does not exist or you do not have enough authority to delete the object. If this is a folder, the folder may not be empty<br>
-<H3>RSEF1301</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Renaming of the object %1 failed<br>
-<b>LevelTwo: </b>Rename operation failed because, the object to rename does not exist, or the object with new object name already exists, or the user does not have enough authority to rename the object<br>
-<H3>RSEF1302</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>No authority or file name not valid<br>
-<b>LevelTwo: </b>The file could not be created because of one of the following reasons:
- - the user does not have enough authority to create the file
- - the file name is not valid<br>
-<H3>RSEF1303</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>File already exists<br>
-<b>LevelTwo: </b>The new file %1 already exists<br>
-<H3>RSEF1304</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Creation of the folder failed<br>
-<b>LevelTwo: </b>The folder %1 could not be created because of one of the following reasons:
- - the user does not have enough authority to create the folder
- - the folder name is not valid<br>
-<H3>RSEF1305</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>The operation did not complete successfully. See additional messages in the Commands view<br>
-<b>LevelTwo: </b>The operation requested failed. Look in the Commands view to see additional messages indicating the cause of the failure<br>
-<H3>RSEF1306</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Copy of the file or folder %1 failed<br>
-<b>LevelTwo: </b>The file system reported the copy operation failed. You may not have authority to the target folder, or it may be in use<br>
-<H3>RSEF1307</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Move of the file or folder %1 failed<br>
-<b>LevelTwo: </b>The file system reported the move operation failed. You may not have authority to the source folder or file, or you may not have authority to the target folder, or it may be in use<br>
-<H3>RSEF1308</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Target folder cannot equal source folder<br>
-<b>LevelTwo: </b>Attempting to move a file or folder to the same folder as it exists in is equivalent to a rename operation. Use the rename action for this<br>
-<H3>RSEF1309</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Folder already exists<br>
-<b>LevelTwo: </b>The new folder %1 already exists<br>
-<H3>RSEF1310</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>New resource will not be visible due to subsetting. Create it anyway?<br>
-<b>LevelTwo: </b>The name of the resource you are creating does not match the current filter criteria. If you select Yes to create the resource, it will not be visible within the current filter.<br>
-<H3>RSEF1311</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>Resource will not be visible due to subsetting. Rename it anyway?<br>
-<b>LevelTwo: </b>The new name of the resource does not match the current filter criteria. If you select Yes to rename the resource, it will not be visible within the current filter.<br>
-<H3>RSEF5001</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>File %1 on %2 can not be opened. You do not have read access to the file.<br>
-<b>LevelTwo: </b>Change file permissions to ensure you have read access to the file.<br>
-<H3>RSEF5002</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>You do not have write access to file %1 on %2. Do you want to open the file in browse mode?<br>
-<b>LevelTwo: </b>You do not have write permission to the file %1 on %2. You can open the file in browse (read-only) mode. If you want to edit the file, change file permissions to allow write access to the file.<br>
-<H3>RSEF5003</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>File %1 can not be saved on %2. You do not have read access to the file.<br>
-<b>LevelTwo: </b>Change file permissions to ensure you have read access to the file.<br>
-<H3>RSEF5004</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>File %1 can not be saved on %2. You do not have write access to the file.<br>
-<b>LevelTwo: </b>Change file permissions to ensure you have write access to the file.<br>
-<H3>RSEF5005</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>File %1 on %2 was modified since you opened this file or saved the file on the server. Do you want to replace the current contents of the file on the server?<br>
-<b>LevelTwo: </b>The file %1 was changed on the server after it was retrieved from %2 or since the last time the file was saved on the server. Choose Yes to replace the contents of the file. Choose No to leave the file on the server with its current contents.<br>
-<H3>RSEF5006</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>File %1 was not completely saved on %2. The file was saved in the local file system.<br>
-<b>LevelTwo: </b>An error occurred while saving the file on the server. A possible cause is the connection to the server was terminated. The file may only have been saved partially on the server. However, it was saved locally to help you recover. You will be asked to save the local copy to the server the next time you connect.<br>
-<H3>RSEF5007</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>File %1 on %2 may not have been saved completely during an earlier edit session. The file was saved on the local file system. Do you want to replace the file with the local copy now?<br>
-<b>LevelTwo: </b>An error occurred during an earlier attempt to save the file. But a local copy of the file was saved for recovery. Choose Yes to save the local copy on the server. Choose No if recovery is not required.<br>
-<H3>RSEF5008</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>File %1 does not exist on %2. Do you want to create the file?<br>
-<b>LevelTwo: </b>Choose Yes to create the file on the server and save the contents to the file. Choose No if you do not want the file to be created.<br>
-<H3>RSEF5009</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>You are currently editing file %1 on %2. Do you want to open the file in browse mode?<br>
-<b>LevelTwo: </b>You are allowed to edit a file in one editor only. You can, however, open the file in another editor for browsing. Browsing lets you view the file but does not allow you to edit its contents.<br>
-<H3>RSEF5010</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Profile named %1 does not exist.<br>
-<b>LevelTwo: </b>Profile may have been renamed or deleted.<br>
-<H3>RSEF5011</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Connection named %1 does not exist.<br>
-<b>LevelTwo: </b>Connection may have been renamed or deleted.<br>
-<H3>RSEF5012</H3>
-<b>Severity: </b>Question<br>
-<b>LevelOne: </b>File %1 already exists. Do you want to overwrite it?<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF6001</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>File type extension can not be empty.<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF6002</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>File type extension must not contain '*' or '.'<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF7001</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Enter CCSID<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF7002</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>CCSID must be a number between 0 and 65535<br>
-<b>LevelTwo: </b><br>
-<H3>RSEF8001</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>An unknown error occurred.<br>
-<b>LevelTwo: </b>%1<br>
-<H3>RSEF8002</H3>
-<b>Severity: </b>Unexpected<br>
-<b>LevelOne: </b>An unexpected error occurred.<br>
-<b>LevelTwo: </b>%1<br>
-<H3>RSEF8003</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Value is not valid<br>
-<b>LevelTwo: </b>%1<br>
-<H3>RSEF8004</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Input %1 is not valid<br>
-<b>LevelTwo: </b>%1<br>
-<br>
-<hr>
-<A NAME="Communications"><!-- --></A><H2>Communications Messages</H2>
-<H3>RSEC1001</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Connection to %1 could not be established.<br>
-<b>LevelTwo: </b>A socket connection to %1 could not be established. If you are connecting via the communications daemon make sure the daemon is running on the remote system. If you are connecting directly to the communications server make sure the server is started on the remote system.<br>
-<H3>RSEC1002</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Invalid password or user ID<br>
-<b>LevelTwo: </b>Authentication with %1 failed because the password or user ID is not correct.<br>
-<H3>RSEC1003</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>The user ID %1 is not valid<br>
-<b>LevelTwo: </b>The user ID %1 on host %2 is not valid. Change the user ID and try again.<br>
-<H3>RSEC1004</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>The saved password is not correct.<br>
-<b>LevelTwo: </b>The saved password for user ID %1 on host %2 is not correct. Please enter the password and try again.<br>
-<H3>RSEC2001</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Environment variable %1 is already defined<br>
-<b>LevelTwo: </b>An environment variable %1 has already been defined. Change the new environment variable's name and press the Add button.<br>
-<H3>RSEC2002</H3>
-<b>Severity: </b>Warning<br>
-<b>LevelOne: </b>Environment variable must have a name.<br>
-<b>LevelTwo: </b>An attempt was made to define an environment variable with a blank name. Type a value for the environment variable name.<br>
-<H3>RSEC2003</H3>
-<b>Severity: </b>Warning<br>
-<b>LevelOne: </b>Environment variable must have a name.<br>
-<b>LevelTwo: </b>An attempt was made to clear the name of an environment variable. To remove an environment variable, select the variable in the list add press the Remove button.<br>
-<H3>RSEC2004</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Environment variable name contains an invalid character.<br>
-<b>LevelTwo: </b>The environment variable name cannot contain a space or the '=' character.<br>
-<H3>RSEC2101</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Saved password for %1 on %2 already exists.<br>
-<b>LevelTwo: </b>The password for user ID %1 on host %2 is already saved. Enter a different user ID or host name or change the existing saved password.<br>
-<H3>RSEC2102</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>New and verify passwords do not match.<br>
-<b>LevelTwo: </b>The new and verify passwords must match (case sensitive) in order to save the new password. Retype the new and verify passwords and try again.<br>
-<H3>RSEC2103</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>Entry field cannot be blank.<br>
-<b>LevelTwo: </b>The hostname, user ID, system type and password entry fields cannot be blank. Type a value and press the Enter key to save the changes.<br>
-<H3>RSEC2104</H3>
-<b>Severity: </b>Error<br>
-<b>LevelOne: </b>There are no tools installed which support saving password information.<br>
-<b>LevelTwo: </b>The password information preference page is a centralized place for Workbench tools to save password information. Each tool registers and provides its own encryption algorithm. There are no tools installed that have registered with the password information preference page.<br>
-<br>
-</BODY>
-</HTML>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/modelAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/modelAPI.html deleted file mode 100755 index 4e762dfa0..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/modelAPI.html +++ /dev/null @@ -1,23 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>RSE Model API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Model API</h1> -<p>The front door to accessing the elements of the RSE model is the <A href="../../reference/api/org/eclipse/rse/core/model/ISystemRegistry.html">ISystemRegistry</A>, which is a -singleton object accessible via <A href="../../reference/api/org/eclipse/rse/model/SystemStartHere.html#getSystemRegistry()">SystemStartHere.getSystemRegistry()</A>. -</p> -<p>The system registry will get you access to profiles, connections and subsystem factories. -From a <A href="../../reference/api/org/eclipse/rse/core/subsystems/ISubSystemConfiguration.html">subsystem configuration</A> you can access subsystems, filter pools, -user actions and compile commands. -From <A href="../../reference/api/org/eclipse/rse/core/subsystems/ISubSystem.html">ISubSystem</A> you can access remote resources, as well -as filter pools referenced by the subsystem. -</p> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/plugin/uiPluginAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/plugin/uiPluginAPI.html deleted file mode 100755 index 7c9bba5a6..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/plugin/uiPluginAPI.html +++ /dev/null @@ -1,80 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Base Plugin Class</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Base Plugin Class</h1> -<p>You may find it of value to base your own plugin class on the RSE-supplied base plugin class. -If so, there are some methods you are encouraged to create or override in your class. The benefits -of using this as your base class is the inherited methods you can access. -</p> -<h2>Methods required in your plugin subclass</h2> -<p>To use the RSE base plugin class -<samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html">org.eclipse.rse.core.SystemBasePlugin</A></samp>, -you subclass it for your own plugin class, and supply some key static methods of your own: -</p> -<ul> -<li><samp>getDefault()</samp>. Return a singleton instance of your plugin. -<li><samp>getResourceBundle()</samp>. Return the resource bundle for your plugin. This is stored in -a static field, initialized in your constructor by calling the <samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#loadResourceBundle(org.eclipse.core.runtime.IPluginDescriptor, java.lang.String)">loadResourceBundle(...)</A></samp> inherited method. -<li><samp>getString(String key)</samp>. Return a translated string by calling the inherited method -<samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getString(java.util.ResourceBundle, java.lang.String)">getString(ResourceBundle rb, String key)</A></samp>, passing in the static resource bundle field. -<li><samp>getPluginMessageFile()</samp>. Return your RSE message file instance, initialized in your -constructor by calling <samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#loadMessageFile(org.eclipse.core.runtime.IPluginDescriptor, java.lang.String)">loadMessageFile(...)</A></samp>. -<li><samp>getPluginMessage(String msgID)</samp>. Return the -<samp><A href="../../../reference/api/org/eclipse/rse/services/clientserver/messages/SystemMessage.html">SystemMessage</A></samp> for the given ID, by -calling the inherited method -<samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getMessage(org.eclipse.rse.services.clientserver.messages.SystemMessageFile, java.lang.String)">getMessage(getPluginMessageFile(), msgId)</a></samp>. You will call this method often to get message objects. -</ul> -<p>You may also override some RSE-supplied instance methods: -<ul> -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#initializeImageRegistry()">initializeImageRegistry()</A></samp>. Call -<samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#putImageInRegistry(java.lang.String, java.lang.String)">putImageInRegistry(String id, String imageFileName)</A></samp> -to load each of your images. -</ul> -</p> -<p>Of course, there are the usual eclipse-supplied instance methods to override too: -<ul> -<li><samp>initializeDefaultPreferences()</samp>. Good place to call the <samp>initDefaults()</samp> method of your preference pages. Be sure to call <samp>super.initializeDefaultPreferences()</samp>. -<li><samp>startup()</samp>. Good place to register adapters and so forth. Be sure to call <samp>super.startup()</samp> at the beginning. -<li><samp>shutdown()</samp>. Good place to close any open communication layers. Be sure to call <samp>super.shutdown()</samp> at the end. -</ul> -</p> - -<h2>Methods inherited from the RSE base class</h2> -<p>The methods you get access to by using the RSE-supplied base plugin class include:</p> -<ul> -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getPluginId()">getPluginId()</A></samp>. Return this plugin's ID. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getActiveWorkbenchShell()">getActiveWorkbenchShell()</A></samp>. Return the shell of the active workbench window. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getActiveWorkbenchWindow()">getActiveWorkbenchWindow()</A></samp>. Return the active workbench window. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getWorkspaceRoot()">getWorkspaceRoot()</A></samp>. Return the root of the workspace. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getWorkspace()">getWorkspace()</A></samp>. Return the workspace root. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getInstallLocation()">getInstallLocation()</A></samp>. Return the install directory for this plugin. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getIconPath()">getIconPath()</A></samp>. Return the typical path for icons, relative to the plugin's folder: "icons/" -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#putImageInRegistry(java.lang.String, java.lang.String)">putImageInRegistry(String id, String fileName)</A></samp>. Load an image in the image registry, given the ID to retrieve it with, and its filename and path relative to this plugin's folder -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getImage(java.lang.String)">getImage(String id)</A></samp>. Return an Image given the ID with which it was registered in putImageInRegistry. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getImageDescriptor(java.lang.String)">getImageDescriptor(String id)</A></samp>. Return an ImageDescriptor given the ID with which it was registered in putImageInRegistry. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#loadResourceBundle(org.eclipse.core.runtime.IPluginDescriptor, java.lang.String)">loadResourceBundle(IPluginDescriptor descriptor, String fileName)</A></samp>. Load a resource bundle, given its file name, relative to the given plugin's installation folder. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#loadResourceBundle(java.lang.String)">loadResourceBundle(String fileName)</A></samp>. Load a resource bundle, given its file name, relative to this plugin's installation folder. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getString(java.util.ResourceBundle, java.lang.String)">getString(ResourceBundle rb, String id)</A></samp>. Return a translated string from a resource bundle, given its key ID. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getString(java.util.ResourceBundle, java.lang.String, java.lang.String)">getString(ResourceBundle rb, String id, String default)</A></samp>. Return a translated string from a resource bundle, given its key ID. If key not found in the resource bundle, returns the given default string. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#loadMessageFile(org.eclipse.core.runtime.IPluginDescriptor, java.lang.String)">loadMessageFile(IPluginDescriptor descriptor,String fileName)</A></samp>. Parse an RSE-style message file into memory, given the plugin and message file name. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getMessage(org.eclipse.rse.services.clientserver.messages.SystemMessageFile, java.lang.String)">getMessage(SystemMessageFile msgFile, String msgId)</A></samp>. Retrieve a SystemMessage object, given the message file that contains it, and its message ID including component and subcomponent abbreviations. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#scanForDuplicateMessages(org.eclipse.rse.services.clientserver.messages.SystemMessageFile)">scanForDuplicateMessages(SystemMessageFile msgFile)</A></samp>. Scan given message file for duplicate IDs. Typically only called during the development cycle. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#printMessages(org.eclipse.rse.services.clientserver.messages.SystemMessageFile, java.lang.String)">printMessages(SystemMessageFile msgFile, String fullyQualifiedTargetFile)</A></samp>. Generate an HTML file documenting the messages in the given message file, given the fully qualified name of the target HTML file. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#showProgrammerErrorMessage(java.lang.String)">showProgrammerErrorMessage(String msg)</A></samp>. Show a message to the user, when the message file support is not available. -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#logInfo(java.lang.String)">logInfo(String message)</A></samp>. Log an informational message to the RSE's core log file (<samp>.....\.metadata\.plugins\org.eclipse.rse.core\.log</samp>). -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#logWarning(java.lang.String)">logWarning(String message)</A></samp>. Log a warning message to the RSE's core log file (<samp>.....\.metadata\.plugins\org.eclipse.rse.core\.log</samp>). -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#logError(java.lang.String)">logError(String message)</A></samp>. Log an error message to the RSE's core log file (<samp>.....\.metadata\.plugins\org.eclipse.rse.core\.log</samp>). -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#logError(java.lang.String, java.lang.Throwable)">logError(String message, Throwable exception)</A></samp>. Log an error message resulting from an exception to the RSE's core log file (<samp>.....\.metadata\.plugins\org.eclipse.rse.core\.log</samp>). -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#logDebugMessage(java.lang.String, java.lang.String)">logDebugMessage(String prefix, String message)</A></samp>. Log a debug (trace) message to the RSE's core log file (<samp>.....\.metadata\.plugins\org.eclipse.rse.core\.log</samp>). -<li><samp><A href="../../../reference/api/org/eclipse/rse/core/SystemBasePlugin.html#getLogger()">getLogger()</A></samp>.Return the Logger instance for the RSE default logging file (<samp>.....\.metadata\.plugins\org.eclipse.rse.core\.log</samp>). -</ul> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_checkBox.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_checkBox.gif Binary files differdeleted file mode 100755 index 19d23df68..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_checkBox.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_comboBox.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_comboBox.gif Binary files differdeleted file mode 100755 index 853d0082a..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_comboBox.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_keyValue.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_keyValue.gif Binary files differdeleted file mode 100755 index 26caa8048..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_keyValue.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_string.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_string.gif Binary files differdeleted file mode 100755 index f43c0681f..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/fldEditor_string.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/rsePreferences.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/rsePreferences.gif Binary files differdeleted file mode 100755 index cc58177fb..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/rsePreferences.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/uiPreferencesAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/uiPreferencesAPI.html deleted file mode 100755 index 9df581818..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/preferences/uiPreferencesAPI.html +++ /dev/null @@ -1,53 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Preferences API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Preferences API</h1> - -<h2>RSE Preference Pages Category</h2> -<p>All Remote System Explorer preference pages are rooted within the -preferences category <samp>org.eclipse.rse.ui.preferences.RemoteSystemsPreferencePage</samp>, -as shown here:</p> -<P><IMG border="0" src="rsePreferences.gif"></P> - -<h2>RSE Preference Pages Classes</h2> -<p>There is no RSE-supplied base class for preference pages, but we recommend -you extend <samp>FieldEditorPreferencePage</samp> in package <samp>org.eclipse.jface.preference</samp>. -This JFace class allows you to create a preferences page as a sequence of "field -editors" which know how to initialize, load and store their values from their preferences store. -</p> -<p>We also suggest the following when designing your preference pages: -<ol> -<li>A interface for your preferences constants. It should store two constants per preference: the preference store key, and its default value. -<li>Static getter and setter methods in your preference page classes, one per preference, to query or update the preference value in the preferences store. -<li>An <samp>initDefaults(IPreferenceStore store)</samp> method per preferences class, that initializes the preference store value of each preference on that page. -<li>In your plugin class, an override of the <samp>initializeDefaultPreferences(IPreferenceStore store)</samp> method, so it calls your -<samp>initDefaults(store)</samp> method for each preference page class. -</ol> -<p>Should you need to query, or update, any RSE preferences you can do so via -the getters and setters in <samp>org.eclipse.rse.core.SystemPreferencesManager</samp>. -</p> -<p>The RSE supplies a few field editors, complementing what JFace supplies -in <samp>org.eclipse.jface.preference</samp>. The RSE-supplied field editors, and the -RSE-supplied preferences pages, are all found in package <samp><A href="../../../reference/api/org/eclipse/rse/ui/propertypages/package-summary.html">org.eclipse.rse.ui.propertypages</A></samp>: -</p> -<ul> -<li><b><samp><A href="../../../reference/api/org/eclipse/rse/ui/propertypages/SystemBooleanFieldEditor.html">SystemBooleanFieldEditor</A></samp></b>. Extends <samp>BooleanFieldEditor</samp> to add support for tooltip text. -<p><IMG border="0" src="fldEditor_checkBox.gif"></p> -<li><b><samp><A href="../../../reference/api/org/eclipse/rse/ui/propertypages/SystemComboBoxFieldEditor.html">SystemComboBoxFieldEditor</A></samp></b>. Shows a combo box allowing the user to choose from a finite list of discrete possibilities. -<p><IMG border="0" src="fldEditor_comboBox.gif"></p> -<li><b><samp><A href="../../../reference/api/org/eclipse/rse/ui/propertypages/SystemKeyValueFieldEditor.html">SystemKeyValueFieldEditor</A></samp></b>. Shows a list of hard-coded keys, each of which supports a user-specifiable value. -<p><IMG border="0" src="fldEditor_keyValue.gif"></p> -<li><b><samp><A href="../../../reference/api/org/eclipse/rse/ui/propertypages/SystemStringFieldEditor.html">SystemStringFieldEditor</A></samp></b>. For simple string preferences. Unlike the JFace string editor, this supports tooltip text and RSE validators and massagers on the typed text. -<p><IMG border="0" src="fldEditor_string.gif"></p> -</ul> -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/properties/uiPropertiesAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/properties/uiPropertiesAPI.html deleted file mode 100755 index 7c4b5338e..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/properties/uiPropertiesAPI.html +++ /dev/null @@ -1,76 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Properties API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Properties API</h1> -<p>You can supply your own property pages to any node in the Remote Systems tree or table views. -As you author your property page classes, you may find the RSE-supplied base class for property pages -of value. - -<h2>RSE-Supplied Base Class for Property Pages</h2> -<p>The RSE supplies a base class for property pages, -<samp><A href="../../../reference/api/org/eclipse/rse/ui/propertypages/SystemBasePropertyPage.html">org.eclipse.rse.ui.propertypages.SystemBasePropertyPage</A></samp>, -that extends the base eclipse property page <samp>org.eclipse.ui.dialogs.PropertyPage</samp>. The advantages -of using this RSE-supplied class are: -</p> -<ul> -<li>Supports <samp><a href="../messages/uiMessageAPI.html">SystemMessage</A></samp> error messages, allowing the user to click on a message to see its details. -<li>Supports automatic assignment of mnemonics for input-capable fields. -<li>Supports automatic management of the "isValid" property based on current error message status in the message line. This -property is important to set correct, so eclipse knows when to prevent the user from switching focus to other property pages. -</ul> - - -<h2>Property Pages for RSE Non-Remote Resources</h2> -<p>You can simply use the eclipse-supplied extension point <samp>org.eclipse.ui.propertyPages</samp> to -contribute property pages to any of the non-remote artifacts from the RSE model. To use this extension -point, you need to know the class or, preferably, interface that the objects implement, which we describe here: -</p> - -<TABLE border="1" width="100%"> - <TBODY> - <TR> - <TH>RSE Resource</TH> - <TH>Implements Interface</TH> - </TR> - <TR> - <TD>Profile</TD> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/core/model/ISystemProfile.html">org.eclipse.rse.core.model.ISystemProfile</A></samp></TD> - </TR> - <TR> - <TD>Host</TD> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/core/model/IHost.html">org.eclipse.rse.core.model.IHost</A></samp></TD> - </TR> - <TR> - <TD>Subsystem</TD> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/core/subsystems/ISubSystem.html">org.eclipse.rse.core.subsystems.ISubSystem</A></samp></TD> - </TR> - <TR> - <TD>Filter pool reference</TD> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/core/filters/ISystemFilterPoolReference.html">org.eclipse.rse.core.filters.ISystemFilterPoolReference</A></samp></TD> - </TR> - <TR> - <TD>Filter reference</TD> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/core/filters/ISystemFilterReference.html">org.eclipse.rse.core.filters.ISystemFilterReference</A></samp></TD> - </TR> - </TBODY> -</TABLE> -<h2>Property Pages for RSE Remote Resources</h2> -<p>Remote resources have no underlying eclipse resource, and typically all are instances of the same class, -meaning insufficient fidelity in scoping property pages to a remote resource of a particular type. Because of this, -the RSE supplies its <a href="../../../reference/extension-points/org_eclipse_rse_ui_propertyPages.html">propertyPages</a> extension point, for remote resources, which allows for -very explicit scoping of the property page to very specific types of remote resources. -</p> - - - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/resourceAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/resourceAPI.html deleted file mode 100755 index d5043eb7e..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/resourceAPI.html +++ /dev/null @@ -1,33 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>RSE Remote Resource API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Remote Resource API</h1> -<p>RSE supplies subsystems for accessing the file system and for executing commands, for -all system types ("universally"). -</p> -<p> -To programmatically access the files in a remote system -identified by a particular system connection, use the -<A href="../../reference/api/org/eclipse/rse/core/model/ISystemRegistry.html">system registry</A> to get to the -<A href="../../reference/api/org/eclipse/rse/core/model/ISystemRegistry.html#getSubSystemsBySubSystemConfigurationCategory(String, org.eclipse.rse.core.model.IHost)">file subsystem</A> -for that connection, by passing in the file category as a String. This <A href="../../reference/api/org/eclipse/rse/subsystems/files/core/subsystems/IRemoteFileSubSystem.html">file subsystem</A> offers methods for accessing the remote files. -</p> -<p> -Similarly, to programmatically run commands in a remote system -identified by a particular system connection, use the -<A href="../../reference/api/org/eclipse/rse/core/model/ISystemRegistry.html">system registry</A> to get to the -<A href="../../reference/api/org/eclipse/rse/core/model/ISystemRegistry.html#getSubSystemsBySubSystemConfigurationCategory(String, org.eclipse.rse.core.model.IHost)">command subsystem</A> -for that connection, by passing in the command category as a String. This <A href="../../reference/api/org/eclipse/rse/subsystems/shells/core/subsystems/IRemoteCmdSubSystem.html">command subsystem</A> offers methods for running remote commands, -either in a new command shell or an existing command shell. You can also set environment variables -using this subsytem object. -</p> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/uiAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/uiAPI.html deleted file mode 100755 index 313117219..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/uiAPI.html +++ /dev/null @@ -1,125 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>RSE User Interface API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE User Interface API</h1> -<p>The RSE provides a number of classes that can help with programming productivity when authoring -user interface artifacts, such as actions, dialogs, wizards, property pages and preferences pages. -Further, a common requirement in all of these artifacts is the need to display translated messages -to the user. The RSE supplies a framework for defining and displaying rich messages that have second -level help, severity and ID attributes. -</p> -<p> -In the following sections we introduce the support offered by the RSE for these UI constructs. -<h2>Plugin Class</h2> -<p>The RSE supplies a base plugin class <samp><a href="plugin/uiPluginAPI.html">SystemBasePlugin</a></samp> that offers -some advantages over the base eclipse <samp>AbstractUIPlugin</samp> class: -<ol> -<li>Simplified methods for registering images, and support for retrieving them either as an image -or an image descriptor. -<li>Support for <a href="logger/uiLoggerAPI.html">logging</a> error, warning and information messages, using the RSE logging framework. -<li>Support for loading a resource bundle, and easily retrieving translated strings from it. -<li>Support for loading an RSE <a href="messages/uiMessageFile.html">message file</a>, and easily retrieving translated messages from it. -<li>Helper methods for getting the active workbench window and shell. -</ol> -</p> -<p>To use the base plugin class effectively, you must subclass it and supply some critical -methods of your own. -</p> - -<h2>Logging</h2> -<p>The Remote System Explorer comes with special support for <a href="logger/uiLoggerAPI.html">logging information</a> to a log file, -for the purpose of problem determination for servicing your plugin. The log file support allows -you to either log your messages to the common RSE log file in the <samp>.metadata\plugins\org.eclipse.rse.core</samp> -folder, or to define your own log file in your plugin metadata folder, if desired. -</p> - -<h2>Messages</h2> -<p>The Java property file for messages is not very rich, as it offers only the ability to define a -single message string. Throughout the RSE perspective you will notice that the messages are richer -than this. They contain second level help, severity, and ID and more. Further, there is a unique -error message dialog for displaying messages, with their second level help, and specialized support -in the RSE dialog, wizard and property page classes for displaying messages on a message line. These -messages can be selected by the user, to bring up the specialized message dialog displaying the -additional properties of the message. Further, there is support for logging severe errors to a log -file, enabling better service support. -</p> -<p> -Your own plugins can enjoy this rich message support too, even independently of using the rest of -the RSE for remote resource access. This support involves defining an xml -<a href="messages/uiMessageFile.html">message file</a>, which defines -the messages, and using a set of -<a href="messages/uiMessageAPI.html">supplied classes</a> to work with the messages. -</p> -<p>Before defining your own messages, you may wish to peruse the list of <a href="messages/uiMessagesCore.html">RSE-supplied messages</a> that are -already defined. The key benefit to using an existing message is translation, as these are already -translated into many languages. -</p> - -<h2>Preference Pages</h2> -<p>When defining your own <a href="preferences/uiPreferencesAPI.html">preferences pages</a>, -you may want to place your preference pages within the Remote Systems preference page category. -As you author your preference page classes, you may find some of the RSE-supplied classes for -preference pages to be useful. -</p> - -<h2>Property Pages</h2> -<p>Property pages can appear in the Properties dialog of any object in eclipse. This dialog is available by selecting -"Properties" from the pop-up menu for the object. The RSE supports defining your own -<a href="properties/uiPropertiesAPI.html">property pages</a> for the resources in its model, although there is a -distinction between local and remote resources. -</p> - -<h2>Validators</h2> -<p>Validating user-entered text is a common and tedious task in any GUI programming. Using validators to encapsulate -the error checking for a particular type of data is a highly recommended practice. The -<a href="validators/uiValidatorsAPI.html">RSE validator</a> support is very -helpful for this, offering both a common interface for all manner of validators and a large list of pre-supplied -validators. -</p> - -<h2>Massagers</h2> -<p>While validating user-entered text is common, so is affecting user-entered text prior to saving it. For example, folding it -to upper or lower case. The <a href="massagers/uiMassagersAPI.html">RSE massager</a> support encapsulates this concept, and -supplies a few re-usable massagers for you. -</p> - -<h2>Widgets</h2> -<p>Populating preference pages, property pages, dialogs and wizards requires use of SWT widget programming. The RSE -<a href="widgets/uiWidgetsAPI.html">widget support</a> can help, with helper methods and classes, and re-usable widgets you may -find useful. -</p> - -<h2>Dialogs</h2> -<p>The RSE supplies rich support for <a href="dialogs/uiDialogsAPI.html">dialogs</a>, including a powerful base class -and, re-usable pre-built dialogs. -</p> - -<h2>Wizards</h2> -<p>Wizards are a common building block of an eclipse GUI. Typically, a wizard is used to prompt for information to create -something new, while a dialog is used to prompt for information for other purposes. -The RSE <a href="wizards/uiWizardsAPI.html">wizard support</a> includes base classes that can simplify the task of creating wizards. -</p> - -<h2>Actions</h2> -<p>Populating popup and pulldown menu items requires the creation of actions. These actions typically popup dialogs or wizards, -and need to be able to pass selections and inputs from the action to the dialog or wizard, and get outputs back. The RSE -<a href="actions/uiActionsAPI.html">action support</a> can significantly help with this programming task, especially when used -together with the RSE dialog and wizard support. -</p> - -<p>Often we want to refresh the contents of the Remote Systems view or Table view from within our actions, to visualize -changes to the selected resources. To do this, use the -<samp><A href="../../reference/api/org/eclipse/rse/model/SystemRegistry.html#fireRemoteResourceChangeEvent(int, java.lang.Object, java.lang.Object, org.eclipse.rse.core.subsystems.ISubSystem, java.lang.String, org.eclipse.jface.viewers.Viewer)">method</a></samp>. -To get the system registry, use the -<samp><A href="../../reference/api/org/eclipse/rse/model/SystemStartHere.html#getSystemRegistry()">method</a></samp>. -</body> - -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/uiValidatorsAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/uiValidatorsAPI.html deleted file mode 100755 index 6894a0a58..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/uiValidatorsAPI.html +++ /dev/null @@ -1,226 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Validators API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Validators API</h1> -<p>Throughout an eclipse UI there are times when we need to validate what the user has typed in. Validators -offer a way to encapsulate the error checking for a particular domain, so it can be re-used wherever the user -is prompted for this. This includes dialogs, property pages, preference pages, wizard pages and viewer -cells. Eclipse's JFace offers two interfaces for this, one for viewer cells and one for the rest. In RSE, -there is a single interface combining the requirements of both, so you can author a single validator that is -re-usable anywhere. Further, the RSE validator interface and sub-interfaces force additional information to be -supplied to enhance re-use, such as the maximum length, which can be used to set the text limit for a text field. -</p> - -<h2>RSE Validator Interfaces</h2> -<p>All RSE validator interfaces and classes are in package <samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/package-summary.html">org.eclipse.rse.ui.validators</A></samp>. - -<h3>ISystemValidator Interface</h3> -<p>The primary validator interface is <samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidator.html">ISystemValidator</A></samp>, which is extends <samp>org.eclipse.jface.dialogs.IInputValidator</samp> -and <samp>org.eclipse.jface.viewers.ICellEditorValidator</samp>. Both parent interfaces define an <samp>isValid</samp> method, -but the former takes a String while the latter takes an Object. They both return a String which is the error message if an -error was detected, or null if no error detected. The <samp>ISystemValidator</samp> interface adds the following additional methods: -</p> - -<TABLE border="1"> - <TBODY> - <TR> - <TH>Method</TH> - <TH>Description</TH> - </TR> - <TR> - <TD><samp>public int <A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidator.html#getMaximumNameLength()">getMaximumNameLength()</A></samp></TD> - <TD>Returns the maximum length allowed for this text. Can be used to set text limit of text widgets.</TD> - </TR> - <TR> - <TD><samp>public SystemMessage <A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidator.html#getSystemMessage()">getSystemMessage()</A></samp></TD> - <TD>If <samp>isValid</samp> returns false, this returns a <samp>SystemMessage</samp> object that offers richer message support than just a string. - Return null if you don't support <samp><A href="../messages/uiMessageAPI.html">SystemMessages</A></samp>. - Callers don't need to use this if they use <samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidator.html#validate(java.lang.String)">validate(String)</A></samp> instead of <samp>isValid(String)</samp>.</TD> - </TR> - <TR> - <TD><samp>public SystemMessage <A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidator.html#validate(java.lang.String)">validate(String text)</A></samp></TD> - <TD>An alternative to <samp>isValid</samp> if your validator does support <samp>SystemMessage</samp> objects versus simple strings for error messages.</TD> - </TR> - </TBODY> -</TABLE> - -<h3>ISystemValidatorUniqueString Interface</h3> -<p>Often our validation requires checking that the given text is unique, in some given list of existing things, like names say. To facilitate -this, there is an interface <samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidatorUniqueString.html">ISystemValidatorUniqueString</A></samp>, which extends <samp>ISystemValidator</samp> and adds some additional -methods required for uniqueness validation: -</p> - -<TABLE border="1"> - <TBODY> - <TR> - <TH>Method</TH> - <TH>Description</TH> - </TR> - <TR> - <TD><samp>public void <A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidatorUniqueString.html#setCaseSensitive(boolean)">setCaseSensitive(boolean caseSensitive)</A></samp></TD> - <TD>Specifies whether the test for an existing string should consider case or not.</TD> - </TR> - <TR> - <TD><samp>public void <A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidatorUniqueString.html#setExistingNamesList(java.lang.String[])">setExistingNamesList(String[] existingList)</A></samp></TD> - <TD>Sets the existing list to test against, as an array.</TD> - </TR> - <TR> - <TD><samp>public void <A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidatorUniqueString.html#setExistingNamesList(java.util.Vector)">setExistingNamesList(Vector existingList)</A></samp></TD> - <TD>Sets the existing list to test against, as a vector of Strings.</TD> - </TR> - <TR> - <TD><samp>public String[] <A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidatorUniqueString.html#getExistingNamesList()">getExistingNamesList()</A></samp></TD> - <TD>Returns the existing list that is used to test against.</TD> - </TR> - </TBODY> -</TABLE> -<p>If you desire to create a unique string validator, you probably will start by subclassing <samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorUniqueString.html">ValidatorUniqueString</A></samp>. -</p> - -<h3>IValidatorRemoteSelection Interface</h3> -<p>The third validator interface is <samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/IValidatorRemoteSelection.html">IValidatorRemoteSelection</A></samp>, which is specifically intended to be used -in the remote resource selection dialogs supplied by the RSE. It allows you to decide when to enable the OK button, based on what -is selected. It contains only the following method:</p> -<samp>public SystemMessage <A href="../../../reference/api/org/eclipse/rse/ui/validators/IValidatorRemoteSelection.html#isValid(org.eclipse.rse.core.model.IHost, java.lang.Object[], org.eclipse.rse.ui.view.ISystemRemoteElementAdapter[])">isValid(SystemConnection selectedConnection, Object[] selectedObjects, ISystemRemoteElementAdapter[] remoteAdaptersForSelectedObject)</A>;</samp> -<p>You typically won't implement this interface directly, but rather sublcass <samp>ValidatorRemoteSelection</samp>.</p> - -<h3>Validator Samples</h3> -<ul> -<li><A href="validatorSample1.html">Sample 1</A></li> -<li><A href="validatorSample2.html">Sample 2</A></li> -<li><A href="validatorSample3.html">Sample 3</A></li> -<li><A href="validatorSample4.html">Sample 4</A></li> -</ul> - -<h2>RSE-Supplied Validators</h2> -<p>You may be able to avoid creating a new validator if you find that RSE has already supplied one you need. Or, you may find it -appropriate to simply subclass one of these RSE-supplied validators. All of them are designed to be either used as-is, or configured -via setter calls, or subclassed, whichever is most convenient.</p> -<p>All of these validators support rich <samp><A href="../messages/uiMessageAPI.html">SystemMessage</A></samp> objects, versus just simple strings for the error message. When used with the -RSE dialog, property page or wizard page classes, you should call -<samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidator.html#validate(java.lang.String)">validate(String)</A></samp> and call -<samp><A href="../../../reference/api/org/eclipse/rse/ui/messages/ISystemMessageLine.html#setErrorMessage(org.eclipse.rse.ui.messages.SystemMessage)">setErrorMessage</A></samp> with the result. When used -in other places you should use <samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ISystemValidator.html#isValid(java.lang.String)">isValid(String)</A></samp> as it returns just the first-level text of the system message.</p> -<TABLE border="1"> - <TBODY> - <TR> - <TH>Validator Class</TH> - <TH>Description</TH> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorCompileCommandLabel.html">ValidatorCompileCommandLabel</A></samp></TD> - <TD>Validates the label for a compile command in the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorConnectionName.html">ValidatorConnectionName</A></samp></TD> - <TD>Validates the name of a connection in the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorFileName.html">ValidatorFileName</A></samp></TD> - <TD>Validates the name of a file in eclipse.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorFilterName.html">ValidatorFilterName</A></samp></TD> - <TD>Validates the name of a filter in the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorFilterPoolName.html">ValidatorFilterPoolName</A></samp></TD> - <TD>Validates the name of a filter pool in the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorFilterString.html">ValidatorFilterString</A></samp></TD> - <TD>Validates the contents of a filter string in the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorFolderName.html">ValidatorFolderName</A></samp></TD> - <TD>Validates the name of a folder in eclipse.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorIntegerInput.html">ValidatorIntegerInput</A></samp></TD> - <TD>Validates the given string is a valid integer.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorIntegerRangeInput.html">ValidatorIntegerRangeInput</A></samp></TD> - <TD>Validates the given string is a valid integer within a given range.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorLongInput.html">ValidatorLongInput</A></samp></TD> - <TD>Validates the given string is a valid long integer.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorLongRangeInput.html">ValidatorLongRangeInput</A></samp></TD> - <TD>Validates the given string is a valid long integer within a given range.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorPathName.html">ValidatorPathName</A></samp></TD> - <TD>Validates the given string is a valid folder path in eclipse.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorPortInput.html">ValidatorPortInput</A></samp></TD> - <TD>Validates the given string is a valid TCP/IP port number.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorProfileName.html">ValidatorProfileName</A></samp></TD> - <TD>Validates the name of a system profile in the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorRemoteSelection.html">ValidatorRemoteSelection</A></samp></TD> - <TD>This is a very special case abstract base class, for validators that decide the enablement of the OK button - in the RSE-supplied remote resource selection dialogs.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorSourceType.html">ValidatorSourceType</A></samp></TD> - <TD>A validator for source types, such as a file type or "*.java". It is intended to be subclassed.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorSpecialChar.html">ValidatorSpecialChar</A></samp></TD> - <TD>A base class for validators that need to ensure the given string doesn't contain certain characters.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorSystemName.html">ValidatorSystemName</A></samp></TD> - <TD>A name validator, to be used when the name being prompted for must follow Java identifier rules.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorUniqueString.html">ValidatorUniqueString</A></samp></TD> - <TD>A base class, or configurable class, to be used for any validation that requires the string to be unique within a given list.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorUserActionCommand.html">ValidatorUserActionCommand</A></samp></TD> - <TD>Validates the command of a user defined action in the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorUserActionComment.html">ValidatorUserActionComment</A></samp></TD> - <TD>Validates the comment of a user defined action in the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorUserActionName.html">ValidatorUserActionName</A></samp></TD> - <TD>Validates the name of a user defined action in the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorUserId.html">ValidatorUserId</A></samp></TD> - <TD>Validates a user ID. Does only basic checking, intended to be subclassed.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorUserTypeName.html">ValidatorUserTypeName</A></samp></TD> - <TD>Validates the name of a named type in the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/validators/ValidatorUserTypeTypes.html">ValidatorUserTypeTypes</A></samp></TD> - <TD>Validates the type list of a named type in the RSE.</TD> - </TR> - </TBODY> -</TABLE> - - - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample1.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample1.html deleted file mode 100755 index b323525fb..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample1.html +++ /dev/null @@ -1,97 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Validator Sample One</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Validator Sample One</h1> -<p>This is an example of a validator written from scratch, that just validates a customer name field is not empty. -Note that while that is all is does today, the power of encapsulation is that we can easily add additional error -checking in the future, and all dialogs or wizards that use the validator will pick up that change. -<pre> - -package org.eclipse.rse.samples.ui.frameworks.dialogs; -import org.eclipse.rse.samples.*; -import org.eclipse.rse.ui.messages.SystemMessage; -import org.eclipse.rse.ui.validators.ISystemValidator; - -/** - * <I>A validator for a customer name. We simply ensure it is not empty, but this could easily be expanded.</I> - */ -public class <B>SampleNameValidator</B> implements ISystemValidator -{ - private SystemMessage currentMsg; - private SystemMessage emptyMsg; - - /** - * <I>Constructor for SampleNameValidator.</I> - */ - public <B>SampleNameValidator</B>() - { - super(); - emptyMsg = SamplesPlugin.<A - href="../messages/uiMessageAPI.html#getPluginMessage">getPluginMessage</A>(<A - href="../messages/sampleMessageFile.html#SPPD1000">"SPPD1000"</A>); - } - - /** - * <I>Required ISystemValidator interface method.</I> - * <I>Return the maximum length for customer names. We return 100.</I> - */ - public int <B>getMaximumNameLength</B>() - { - return 100; - } - - /** - * <I>Required ISystemValidator interface method.</I> - * <I>@see org.eclipse.rse.ui.validators.ISystemValidator#getSystemMessage()</I> - */ - public SystemMessage <B>getSystemMessage</B>() - { - return currentMsg; - } - - /** - * <I>Required ISystemValidator interface method.</I> - * <I>@see org.eclipse.rse.ui.validators.ISystemValidator#validate(String)</I> - */ - public SystemMessage <B>validate</B>(String text) - { - isValid(text); - return currentMsg; - } - /** - * <I>@see org.eclipse.jface.dialogs.IInputValidator#isValid(String)</I> - */ - public String <B>isValid</B>(String newText) - { - if ((newText==null) || (newText.length()==0)) - currentMsg = emptyMsg; - // todo: more error checking - - if (currentMsg != null) - return currentMsg.getLevelOneText(); - else - return null; - } - /** - * <I>@see org.eclipse.jface.viewers.ICellEditorValidator#isValid(Object)</I> - */ - public String <B>isValid</B>(Object value) - { - if (value instanceof String) - return isValid((String)value); - return null; - } -} -</pre> - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample2.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample2.html deleted file mode 100755 index 5b2d63fe4..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample2.html +++ /dev/null @@ -1,45 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Validator Sample Two</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Validator Sample Two</h1> -<p>This is an example of a validator written by extending an existing RSE-supplied validator, and -simply supplying unique messages. -<pre> - -package org.eclipse.rse.samples.ui.frameworks.dialogs; -import org.eclipse.rse.ui.validators.ValidatorIntegerRangeInput; -import org.eclipse.rse.samples.*; - -/** - * <I>An example of a customized validator, that prompts for a birth year.</I> - */ -public class <B>SampleBirthYearValidator</B> extends ValidatorIntegerRangeInput -{ - /** - * <I>Constructor. Specifies the valid range, and unique error messages.</I> - */ - public SampleBirthYearValidator() - { - super(1900, 2003); - super.setErrorMessages(SamplesPlugin.<A - href="../messages/uiMessageAPI.html#getPluginMessage">getPluginMessage</A>("<A - href="../messages/sampleMessageFile.html#SPPD1001">SPPD1001</A>"), // <I>empty</I> - SamplesPlugin.getPluginMessage("<A - href="../messages/sampleMessageFile.html#SPPD1002">SPPD1002</A>"), // <I>non-numeric</I> - SamplesPlugin.getPluginMessage("<A - href="../messages/sampleMessageFile.html#SPPD1003">SPPD1003</A>")); // <I>out of range</I> - } - -}</pre> - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample3.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample3.html deleted file mode 100755 index 551b14350..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample3.html +++ /dev/null @@ -1,43 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Validator Sample Three</title></head> - -<body bgcolor="#ffffff"> -<h1>RSE Validator Sample Three</h1> -<p>This is an example of a validator written by extending an existing RSE-supplied validator, and -simply supplying unique messages. -<pre> -package org.eclipse.rse.samples.ui.frameworks.dialogs; -import org.eclipse.rse.ui.validators.ValidatorIntegerRangeInput; -import org.eclipse.rse.samples.*; - -/** - * <I>An example of a customized validator, that prompts for a birth month.</I> - */ -public class <B>SampleBirthMonthValidator</B> extends ValidatorIntegerRangeInput -{ - /** - * <I>Constructor. Specifies the valid range, and unique error messages.</I> - */ - public SampleBirthMonthValidator() - { - super(1, 12); - super.setErrorMessages(SamplesPlugin.<A - href="../messages/uiMessageAPI.html#getPluginMessage">getPluginMessage</A>("<A - href="../messages/sampleMessageFile.html#SPPD1004">SPPD1004</A>"), // <I>empty</I> - SamplesPlugin.getPluginMessage("<A - href="../messages/sampleMessageFile.html#SPPD1005">SPPD1005</A>"), // <I>non-numeric</I> - SamplesPlugin.getPluginMessage("<A - href="../messages/sampleMessageFile.html#SPPD1006">SPPD1006</A>")); // <I>out of range</I> - } - -}</pre> - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample4.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample4.html deleted file mode 100755 index 23fdb97f2..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/validators/validatorSample4.html +++ /dev/null @@ -1,44 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Validator Sample Four</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Validator Sample Four</h1> -<p>This is an example of a validator written by extending an existing RSE-supplied validator, and -simply supplying unique messages. -<pre> -package org.eclipse.rse.samples.ui.frameworks.dialogs; -import org.eclipse.rse.core.ui.validators.ValidatorIntegerRangeInput; -import org.eclipse.rse.samples.*; - -/** - * <I>An example of a customized validator, that prompts for a birth day.</I> - */ -public class <B>SampleBirthDayValidator</B> extends ValidatorIntegerRangeInput -{ - /** - * <I>Constructor. Specifies the valid range, and unique error messages</I>. - */ - public SampleBirthDayValidator() - { - super(1, 31); - super.setErrorMessages(SamplesPlugin.<A - href="../messages/uiMessageAPI.html#getPluginMessage">getPluginMessage</A>("<A - href="../messages/sampleMessageFile.html#SPPD1007">SPPD1007</A>"), // <I>empty</I> - SamplesPlugin.getPluginMessage("<A - href="../messages/sampleMessageFile.html#SPPD1008">SPPD1008</A>"), // <I>non-numeric</I> - SamplesPlugin.getPluginMessage("<A - href="../messages/sampleMessageFile.html#SPPD1009">SPPD1009</A>")); // <I>out of range</I> - } - -}</pre> - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/widgets/uiWidgetsAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/widgets/uiWidgetsAPI.html deleted file mode 100755 index 39f1366ed..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/widgets/uiWidgetsAPI.html +++ /dev/null @@ -1,73 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Widgets API</title> -</head> - -<body bgcolor="#ffffff"> - -<h1>RSE Widgets API</h1> -<p>Whether coding dialogs, property pages, preference pages or wizard pages we need to write the code to display -and process the widgets in the client area. The RSE offers some help in this area in two ways: -</p> -<ol> -<li>A <samp><A href="../../../reference/api/org/eclipse/rse/ui/SystemWidgetHelpers.html">SystemWidgetHelpers</A></samp> -class full of static methods to make it easier to create SWT widgets. -<li>A few re-usable widgets that extend SWT. -</ol> - -<h2>SystemWidgetHelpers Class</h2> -<p>The <samp><A href="../../../reference/api/org/eclipse/rse/ui/SystemWidgetHelpers.html">SystemWidgetHelpers</A></samp> -class in <samp><A href="../../../reference/api/org/eclipse/rse/ui/package-summary.html">org.eclipse.rse.ui</A></samp> -is chock full of static methods to simplify the work in populating a GridLayout composite with widgets. The GridLayout composite is the most -flexible and useful of the layouts, yet the most work to code to. These methods will help with that. The methods include: -</p> -<ul> -<li>Methods for creating a GridLayout composite. You typically call this at the start of your code that populates the client area. -<li>Methods for creating all the common SWT controls, with the GridData values specified for you. -<li>Methods for creating readonly flavours of input controls, such as a Text field or Combo box. -<li>Methods for creating labeled entry fields that have a prompting label in front of an input widget. -<li>Methods for automatically assigning unique mnemonics to all input widgets on a given composite or page. -<li>Methods for setting composite, widget, action and menu item contextual help. -<li>Methods for creating RSE-supplied widgets. -<li>Methods for creating populated combo boxes for connections, remote folders, system types and host names. -</ul> - -<h2>RSE-Supplied Widgets</h2> -<p>The <samp><A href="../../../reference/api/org/eclipse/rse/ui/widgets/package-summary.html">org.eclipse.rse.ui.widgets</A></samp> -package contains some specialized widgets you may find a use for: -</p> -<TABLE border="1"> - <TBODY> - <TR> - <TH>Widget Class</TH> - <TH>Description</TH> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/widgets/SystemHistoryCombo.html">SystemHistoryCombo</A></samp></TD> - <TD>A entry field that remembers its previous values and shows them in a dropdown so the user can easily re-select a previously typed value. The history is maintained for you, and is indexed by a key. This allows the combos to share history across numerous dialogs, property pages or wizard pages. The history can be bounded and pre-filled, and the user can clear the history at any time. This handy widget is used extensively within the RSE.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/widgets/InheritableEntryField.html">InheritableEntryField</A></samp></TD> - <TD>An entry field with an left-right arrow beside it. When toggled left, the entry field is not editable and displays a supplied value. When toggled right, the entry field is editable. Useful in cases where the user can choose between an inherited or default value, or enter their own value.</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/widgets/SystemPortPrompt.html">SystemPortPrompt</A></samp></TD> - <TD>Uses the InheritableEntryField to prompt for a TCP/IP port, where toggling to the left means port 0, or let the "first available port".</TD> - </TR> - <TR> - <TD><samp><A href="../../../reference/api/org/eclipse/rse/ui/widgets/SystemHostCombo.html">SystemHostCombo</A></samp></TD> - <TD>This is a combo box that displays the currently defined RSE system connections. The list can be subset by system type or types. Further, you can optionally display a New button beside the combo that allows the user to create a new connection.</TD> - </TR> - </TBODY> -</TABLE> -<p>There are also many useful widgets related to the selection of remote files or folders, in package -<samp><A href="../../../reference/api/org/eclipse/rse/files/ui/widgets/package-summary.html">org.eclipse.rse.files.ui.widgets</A></samp> - -<P><BR></P> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/wizards/uiWizardsAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/wizards/uiWizardsAPI.html deleted file mode 100755 index 89adf7765..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/wizards/uiWizardsAPI.html +++ /dev/null @@ -1,74 +0,0 @@ -<!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" HREF="../../../book.css" TYPE="text/css"> -<title>RSE Wizards API</title> -</head> - -<body bgcolor="#ffffff"> -<h1>RSE Wizards API</h1> -<p>Typically in eclipse GUI design we use a wizard to create new things, and a dialog -to prompt for secondary information, or update existing things. The Remote System Explorer -can offer help in creating wizards, just as it does in creating dialogs. -</p> - -<h2>RSE-Supplied Base Classes for Wizards</h2> -<p>The RSE offers the following classes, in package -<samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/package-summary.html">org.eclipse.rse.ui.wizards</A></samp> to simplify the creation of wizards.</p> - -<h3>The <samp>AbstractSystemWizardPage</samp> class</h3> -<p>The <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizardPage.html">AbstractSystemWizardPage</A></samp> abstract base class extends the -JFace <samp>WizardPage</samp> class to offer the following benefits to subclasses:</p> -<ol> - <li>Designed to work in conjunction with <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html">AbstractSystemWizard</A></samp>, - propogating settings from the wizard to the individual wizard pages. - <li>Supports using the overall wizard page title as set - by <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html#setWizardPageTitle(java.lang.String)">setWizardPageTitle(String)</A></samp> - in <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html">AbstractSystemWizard</A></samp>, - if no title specified in the constructor. - <li>Supports a <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizardPage.html#setHelp(java.lang.String)">setHelp(String)</A></samp> method to set the wizard page's overall contextual help - <li>Implements <samp><A - href="../messages/uiMessageAPI.html#ISystemMessageLine">ISystemMessageLine</A></samp> so supports setting error messages as - either strings or, preferably, <samp><A - href="../messages/uiMessageAPI.html#SystemMessage">SystemMessage</A></samp> objects. - <li>Supports automatic assignment of unique mnemonics for all input-capable controls on the page, to aid in accessibility. - <li>Supports setting a default-focus control, which gets initial focus when the page is shown. - <li>Supports helper methods to aid in population of the client area: - <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizardPage.html#addSeparatorLine(org.eclipse.swt.widgets.Composite, int)">addSeparatorLine(Composite,int)</A></samp>, - <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizardPage.html#addFillerLine(org.eclipse.swt.widgets.Composite, int)">addFillerLine(Composite,int)</A></samp> and - <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizardPage.html#addGrowableFillerLine(org.eclipse.swt.widgets.Composite, int)">addGrowableFillerLine(Composite,int)</A></samp>. -</ol> - - -<h3><A name="AbstractSystemWizard"></A>The <samp>AbstractSystemWizard</samp> class</h3> -<p>The <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html">AbstractSystemWizard</A></samp> abstract base class extends the JFace <samp>Wizard</samp> -class to offer the following benefits to subclasses:</p> -<ol> - <li>Designed to work in conjunction with the <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseWizardAction.html">SystemBaseWizardAction</A></samp>, - and <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemWizardDialog.html">SystemWizardDialog</A></samp> classes, propogating settings - from these to the wizard, and further propogating those to the individual wizard pages. - <li>The overall wizard title and image can be set via the constructor or setter methods. - <li>Supports setting an input object, and getting an output object. This is exploited by the - <samp><A href="../../../reference/api/org/eclipse/rse/ui/actions/SystemBaseWizardAction.html">SystemBaseWizardAction</A></samp> class, when this wizard is launched from a subclass of that action class. - <li>Supports setting a wizard page title via <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html#setWizardPageTitle(java.lang.String)">setWizardPageTitle(String)</A></samp>, that all - <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizardPage.html">AbstractSystemWizardPage</A></samp> pages will use by default for - their title, if the non-title constructor is used for that page. - <li>If being hosted by a <samp><A href="../../../reference/api/org/eclipse/rse/ui/dialogs/SystemWizardDialog.html">SystemWizardDialog</A></samp>, supports dynamically - updating the wizard size via <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html#updateSize()">updateSize()</A></samp>, - if dynamic content is added to a wizard page, causing the page to grow beyond its initial size. - <li>Supports a <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html#setHelp(java.lang.String)">setHelp(String)</A></samp> method to set the overall wizard's contextual help. This is propogated to each - <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizardPage.html">AbstractSystemWizardPage</A></samp> as it is added. - <li>Supports setting the viewer that launched this wizard, as wizards often need to know this so they can update the UI upon Finish. - <li>Supports a <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html#wasCancelled()">wasCancelled()</A></samp> method so callers can easily test if the wizard was cancelled by the user. - <li>Supports a <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html#setMinimumPageSize(int, int)">setMinimumPageSize(int,int)</A></samp> method to set the minimum width and height of the wizard. - <li>Supports a <samp><A href="../../../reference/api/org/eclipse/rse/ui/wizards/AbstractSystemWizard.html#setPageError(org.eclipse.jface.wizard.IWizardPage)">setPageError(IWizardPage)</A></samp> method that can be called in performFinish when an error is detected on a - non-current page. This issues a message telling the user there is an error on another page. -</ol> - -<P><BR></P> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/file_conn.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/file_conn.gif Binary files differdeleted file mode 100755 index 136f576a3..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/file_conn.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/file_profiles.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/file_profiles.gif Binary files differdeleted file mode 100755 index e0ad94fca..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/file_profiles.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/images/configexample.jpg b/rse/doc/org.eclipse.rse.doc.isv/guide/images/configexample.jpg Binary files differdeleted file mode 100755 index 62197bc69..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/images/configexample.jpg +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/images/layers.jpg b/rse/doc/org.eclipse.rse.doc.isv/guide/images/layers.jpg Binary files differdeleted file mode 100755 index 0dd8792ec..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/images/layers.jpg +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/overview.html b/rse/doc/org.eclipse.rse.doc.isv/guide/overview.html deleted file mode 100755 index de5f0c361..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/overview.html +++ /dev/null @@ -1,14 +0,0 @@ -<!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">
-<title>Remote System Explorer Overview</title>
-<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">
-</head>
-
-<body bgcolor="#ffffff">
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/ChangeFilterDialog_Default.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/ChangeFilterDialog_Default.gif Binary files differdeleted file mode 100755 index 55e98e121..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/ChangeFilterDialog_Default.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/NewConnection.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/NewConnection.gif Binary files differdeleted file mode 100755 index 567d476dd..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/NewConnection.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/NewFilterWizard_Default.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/NewFilterWizard_Default.gif Binary files differdeleted file mode 100755 index e39164720..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/NewFilterWizard_Default.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/RSView_iSeries.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/RSView_iSeries.gif Binary files differdeleted file mode 100755 index c268d212f..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/RSView_iSeries.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/other.html b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/other.html deleted file mode 100755 index 9a5485053..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/other.html +++ /dev/null @@ -1,160 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>Other Relevant Extension Points</title> -</head> - -<body bgcolor="#ffffff"> -<h1>Other Relevant Extension Points</h1> -<p>There are some Eclipse extension points that are relevant as-is to the Remote System Explorer, -which we list here. We do not describe how to use these extension points here, except to document -the information needed to enable them to in Remote System Explorer. -</p> - -<TABLE border="1"> - <TBODY> - <TR> - <TH>Extension Point</TH> - <TH>Description</TH> - </TR> - <TR> - <TD><samp>org.eclipse.ui.viewActions</samp></TD> - <TD>For adding actions to the pulldown menu in any view's local toolbar, or to the toolbar itself. - To use this you need to know the ID of the RSE views, for the <samp>targetID</samp> attribute: There are: - <ul> - <li><samp>org.eclipse.rse.ui.view.systemView</samp> for the primary - <A href="view_RS.gif">Remote Systems</A> view. - <li><samp>org.eclipse.rse.ui.view.teamView</samp> for the - <A href="view_Team.gif">Team</A> view in the RSE perspective. - <li><samp>org.eclipse.rse.ui.view.systemTableView</samp> for the - <A href="view_Table.gif">Remote System Details</A> view in the RSE perspective. - </ul> - </TD> - </TR> - <TR> - <TD><samp>org.eclipse.ui.propertyPages</samp></TD> - <TD>For adding property pages for non-remote objects within the - Remote System Explorer. To use this you need to know the class type - of these objects for the <samp>objectClass</samp> attribute of the <samp><page></samp> element: - <ul> - <li>Connections: <samp><A href="../../reference/api/org/eclipse/rse/core/model/IHost.html">org.eclipse.rse.core.model.IHost</A></samp> - <li>SubSystems: <samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/ISubSystem.html">org.eclipse.rse.core.subsystems.ISubSystem</A></samp> - <li>Filter Pools: <samp><A href="../../reference/api/org/eclipse/rse/core/filters/ISystemFilterPoolReference.html">org.eclipse.rse.core.filters.ISystemFilterPoolReference</A></samp> - <li>Filters: <samp><A href="../../reference/api/org/eclipse/rse/core/filters/ISystemFilterReference.html">org.eclipse.rse.core.filters.ISystemFilterReference</A></samp> - </ul> - It is possible to scope your property pages to only appear for certain system types or subsystems, using - the <samp><filter></samp> element. For example:<br> - <pre><code> - <extension point="org.eclipse.ui.propertyPages"> - <page name="Team Info" - class="samples.ui.propertypages.TeamFilterPropertyPage" - id="samples.ui.pp.filter.team" - objectClass="org.eclipse.rse.core.filters.ISystemFilterReference" > - <b><filter name="subsystemFactoryId" value="samples.subsystems.factory"/></b> - </page> - </extension> - </code></pre> - See <a href="#scoping">Scoping</a> for all the filter <samp>names</samp> supported by RSE objects. - </TD> - </TR> - <TR> - <TD><samp>org.eclipse.ui.popupMenus</samp></TD> - <TD>For adding pop-up menu actions for non-remote objects within the Remote System Explorer. - To use this you need to know the class type of these objects for the <samp>objectClass</samp> attribute - of the <objectContribution> element: - <ul> - <li>Connections: <samp><A href="../../reference/api/org/eclipse/rse/core/model/IHost.html">org.eclipse.rse.core.model.IHost</A></samp> - <li>SubSystems: <samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/ISubSystem.html">org.eclipse.rse.core.subsystems.ISubSystem</A></samp> - <li>Filter Pools: <samp><A href="../../reference/api/org/eclipse/rse/core/filters/ISystemFilterPoolReference.html">org.eclipse.rse.core.filters.ISystemFilterPoolReference</A></samp> - <li>Filters: <samp><A href="../../reference/api/org/eclipse/rse/core/filters/ISystemFilterReference.html">org.eclipse.rse.core.filters.ISystemFilterReference</A></samp> - </ul> - It is possible to scope your actions to only appear for certain system types or subsystems, using - the <samp><filter></samp> element. For example:<br> - <pre><code> - <extension point="org.eclipse.ui.popupMenus"> - <objectContribution - id ="samples.ui.actions.TeamFilterActions" - objectClass="org.eclipse.rse.core.filters.ISystemFilterReference"> - <b><filter name="subsystemFactoryId" value="samples.subsystems.factory"/></b> - <action id="samples.ui.actions.TeamFilterAction1" - label="Sample Team Filter Action" - class="samples.ui.actions.ShowJarContents"> - </action> - </objectContribution> - </extension> - </code></pre> - See <a href="#scoping">Scoping</a> for all the filter <samp>names</samp> supported by RSE objects. - </TD> - </TR> - </TBODY> -</TABLE> - -<a name="scoping"></a><h2>Scoping</h2> -<p>For the <samp>org.eclipse.ui.propertyPages</samp> and <samp>org.eclipse.ui.popupMenus</samp> extension points, it is -possible to scope your property pages and actions to only filters in a particular subsystem, or connections of a -particular system type, say. These extension points support the <samp><filter></samp> element, which -allows you to specify a property name, and a property value, such that the page or action will only show if -that property's value is the one given:<br> -<pre><code> - <filter name="<i>name</i>" value="<i>value</i>"/> -</code></pre> -It is up to the selected object's adapter to perform this test, in its -<code>testAttribute(Object target,String <i>name</i>,String <i>value</i>)</code> method. This method is implemented for the adapters for every object shown in the -Remote Systems view, and what follows is a list of the tests it will do on the given <samp><i>value</i></samp>, -for the given <samp><i>name</i></samp>:</p> -<ul> -<li><b><samp>"name"</samp></b>. Will test the <i>value</i> for an exact match on an object's name, -or beginning-of-name match if ends with an asterisk. -<li><b><samp>"type"</samp></b>. Will test the <i>value</i> for an exact match on an object's type. -<li><b><samp>"offline"</samp></b>.Will test the <i>value</i> against "true" if the user is working -in "offline" mode or "false" if not. Currently only supported for iSeries connections. -<li><b><samp>"connected"</samp></b>. Will test the <i>value</i> against "true" if the connection -containing the selected object is active or "false" if not. -<li><b><samp>"hasChildren"</samp></b>. Will test the <i>value</i> against "true" if this object's -adapter reports that it has children or "false" if it doesn't have children. -<li><b><samp>"systemType"</samp></b>. Will test the <i>value</i> for an exact match on the system type of -this object's parent SystemConnection object. -You can specify multiple values if you comma-separate them. -<li><b><samp>"subsystemFactoryId"</samp></b>. Will test the <i>value</i> for an exact match on the -<samp>ID</samp> of the subsystem factory that created this object's subsystem. Returns false for SystemConnection objects. -You can specify multiple values if you comma-separate them. -<li><b><samp>"subsystemFactoryCategory"</samp></b>. Will test the <i>value</i> for an exact match -on the <samp>category</samp> of the subsystem factory that created this object's subsystem. -You can specify multiple values if you comma-separate them. -</ul> - -<p>For system filter objects of type <samp>org.eclipse.rse.core.filters.ISystemFilterReference</samp>, -the following names are also supported: -<ul> -<li><b><samp>"filterType"</samp></b>. Will test the <i>value</i> for an exact match on the selected filter's -untranslated type, as set internally. The only RSE-supplied subsystem to support multiple filter types is -the iSeries Objects subsystem for iSeries connections. It contains these types: - <ul> - <li><samp>"Library"</samp>. - <li><samp>"LibraryList"</samp>. - <li><samp>"Object"</samp>. - <li><samp>"Member"</samp>. - </ul> -</ul> - -<p>For the <samp>org.eclipse.ui.popupMenus</samp> extension point, you can also use the above names -in the <visibility> and <enablement> elements, for extreme flexibility in when -the action is shown, and when it is enabled or disabled. These map to the <samp>objectState</samp> -attribute. For example: -<pre><code> - <enablement> - <objectState name="hasChildren" value="true"/> - </enablement> -</code></pre> - - -<p>Be aware the <samp><visibility></samp> element is available at the -<samp><objectContribution></samp> level, while the <samp><enablement></samp> -element is available at the <samp><Action></samp> level. -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/popup.html b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/popup.html deleted file mode 100755 index 3c39a717d..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/popup.html +++ /dev/null @@ -1,146 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>Plugging In Popup Menu Actions</title> -</head> - -<body bgcolor="#ffffff"> -<h1>Plugging In Popup Menu Actions</h1> -<p>The <samp><A href="../../reference/extension-points/org_eclipse_rse_ui_popupMenus.html">org.eclipse.rse.ui.popupMenus</a></samp> extension point is defined in the -plugin <samp>org.eclipse.rse.ui</samp>, and it is patterned -after Eclipse's <samp>org.eclipse.ui.popupMenus</samp> extension point. However, it is -both simplified and extended specifically for remote objects. -</p> -<p>The primary element in the markup for this extension point is the <b><samp><objectContribution></samp></b> element, -which scopes the remote objects to which the child elements apply: -</p> -<ul> -<li><b>id</b>.A unique ID for this extension point. Not used, but required by Eclipse. -<li><b><i>filtering attributes</i></b>.To scope which remote objects these actions should show up for. -Described in the <samp><A href="../../reference/extension-points/org_eclipse_rse_ui_popupMenus.html">documentation</a></samp> -of this element. -</ul> -<p>Within each <samp><objectContribution></samp> element are zero or more <B><samp><menu></samp></B> elements for -optionally defining cascading submenus, and <<B>action</B>> elements for the actual actions. -To have the actions show up in a cascading menu, use the <samp><menu></samp> element with these -attributes: -</p> -<ul> -<li><b>id</b>. Unique id for the submenu. Used later to target actions into this cascading submenu. -<li><b>label</b>. The text the user sees in the pop-up menu. -<li><b>path</b>. For multi-cascading menus, use this attribute to identify a previously specified menu that -this menu is to be nested within. The syntax is a bit tricky. It is <samp>id/group</samp>, where <samp>id</samp> -matches the id attribute from a previous <samp><menu></samp> element, and <samp>group</samp> matches the name attribute -of a <samp><separator></samp> sub-element within that previous <samp><menu></samp> element. For multi-nesting, repeat the <samp>id</samp> -part, as in <samp>id1/id2/id3/group</samp>. In this case, there must be a <samp><menu></samp> element with and id value of -<samp>id3</samp> that refers to another <samp><menu></samp> element <samp>id2</samp> via is path attribute, which in turn -refers to <samp><menu></samp> element <samp>id1</samp> via its <samp>path</samp> attribute. If the group does not exist, -it will be created. -<br> -For the root cascading menu, you can also use this to specify a group within the remote object's pop-up, -for where to place this cascading menu. The default is the <samp>additions</samp> group, which is near the -bottom of the pop-up menu. The RSE-supplied groups for pop-up menus are listed shortly in Table 4. There are -also a few RSE-supplied cascading menus listed in Table 4, which can be specified for the id prefix in order -to add a cascading menu to an RSE-supplied cascading menu. -</ul> -<P>Within each <samp><menu></samp> element are one or more <b><samp><separator></samp></b> elements that partition the cascading -menu into groups. Groups are simply named physical areas of the menu. The order in which they are defined is the order they -appear in the menu. Actions always go into groups. Groups avoid the need to specify relative information to identify where -within a pop-up menu to place actions. There is only one attribute for this element: -</P> -<ul> -<li><b>name</b>. The name to give this group. Users do not see this, but it is used in the <samp>action</samp> element to identify where to place -the action within this submenu. Groups exist in the order they are defined, top to bottom. Between groups is a separator unless -contiguous groups are empty. There is always a default group named <samp>additions</samp> supplied for you. -</ul> -<p>Finally, within <samp><objectContribution></samp> elements are one or more <b><samp><action></samp></b> elements identifying the -actual actions, each of which only show up if the scoping criteria is met for that parent <samp><objectContribution></samp> -element. The attributes for <samp><action></samp> elements are: -</p> -<ul> -<li><b>id</b>. Unique id for the action. -<li><b>label</b>. What the user sees in the pop-up menu. -<li><b>icon</b>. Optional icon to show beside the label. This is the name of a file qualified by a path relative to this plugin's directory. -<li><b>class</b>. Name of the class extending one of the classes listed in the documentation. -<li><b>menubarPath</b>. Where to put this action. This is optional and only required when you do not want the action to go into the -default location within the remote object's pop-up menu. This is a group name, optionally preceded by slash-delimited Ids for actions -that go inside cascading menus, where each Id matches an id attribute from a previously specified <samp><menu></samp> element. -If no menubarPath is specified, the action goes into the <samp><additions></samp> area of the object's popup menu, which is -near the bottom of the pop-up menu. The RSE-supplied groups for remote object pop-up menus are listed in Table 4, as well as menu Ids -for RSE-supplied cascading menus, should you wish to add an action to an RSE-supplied cascading menu. -<li><b>enablesFor</b>. Tells when to enable this action based on how many items are selected. Typically, specify "1" for -single-selection or "+" for multiple-selection. You can also change the enabled state of your action within your class, -by calling the <samp>setEnabled(boolean)</samp> method or overriding the <samp>getEnabled(Object[] currentlySelected)</samp> method that is called -when the selection changes. -<li><b>state</b>. Specify if this is a toggle (checkable) menu item. Specify "true" or "false" to indicate initial -toggle status. Call <samp>setChecked(boolean)</samp> in your class to change the toggled state. -<li><b>helpContextId</b>. Allows F1 help for this action. Optional. -</ul> -<p> -The <samp>path</samp> attribute for the <samp><menu></samp> element, and the <samp>menubarPath</samp> attribute for the <samp><action></samp> -element, are the most difficult to master. The rules are reasonably simple though: -</p> -<ol> -<li>To have your action show up in the initial pop-up menu, just specify a group name on the <samp>menubarPath</samp> attribute. That name can be -one of the RSE-supplied group names defined in Table 4, or your own group name, which will be created and appended to the end of the -pop-up menu. The default group is <samp>"additions"</samp>. -<br>Example: <samp>menubarPath="myGroup"</samp> -<li>To have your action show up in a simple RSE-supplied cascading menu within the pop-up menu, in your <samp><action></samp> element, -specify the RSE-supplied menu ID from Table 4 in the <samp>menubarPath</samp> attribute, then a slash followed by the name of a group. The only -RSE-supplied group for cascading menus is <samp>"additions"</samp>. If you specify anything else for the group, the group will be created for you -at the bottom of the menu. -<br>Example: <samp>menubarPath="menu.new/myGroup"</samp> -<li>To have your action show up in a simple cascading menu of your own, first define the menu with a <samp><menu></samp> element, -giving it an ID via the id attribute. In your <samp><action></samp> element, in the <samp>menubarPath</samp> attribute specify that id followed by a slash -and then the name of a group. That group name can be one specified on a <samp><separator></samp> element within your menu, or a new name, which -results in a new group at the bottom of the menu. In the latter case, there will be no separators delimiting the group, while in the former case -there will be. -<br>Example: <samp>menubarPath="myMenu1/myGroup"</samp> -<li>To have your action show up in a multi-cascading menu of your own, define each of the menu via <samp><menu></samp> elements. For all but the -first, identify the parent menu using the path attribute, specifying the Ids for each of the parent menus, slash-separated. At -the end of the path attribute, specify the group within the final parent menu into which this menu will be placed. Again, this -will either be a group defined with a <samp><separator></samp> element in the parent <samp>menu</samp> element, or specify a non-existing group that will be -created for you. Once your multi-cascading menu is created, you identify it in your <samp><action></samp> element via the <samp>menubarPath</samp> attribute, -specifying all the menu Ids up to the final menu, slash-separated, and then the group within that final menu, as usual. -<br>Example: <samp>menubarPath="myMenu1/myMenu2/myGroup"</samp> -</ol> - -<h2>Programming Details</h2> -<p>To use this extension point you will create a class that extends the -<samp><A href="../../reference/api/org/eclipse/rse/ui/actions/SystemAbstractPopupMenuExtensionAction.html">SystemAbstractPopupMenuExtensionAction</A></samp> class in the -package <samp><A href="../../reference/api/org/eclipse/rse/ui/actions/package-summary.html">org.eclipse.rse.ui.actions</A></samp>. This is your action class, -and when the user selects your action, the <samp>run()</samp> -method in your action class will be called. You will rarely extend the <samp>SystemAbstractPopupMenuExtensionAction</samp> base class -directly, though. Instead there are subclasses of it that offer additional functionality for specific types of remote objects, -as shown here: -</p> - - -<TABLE border="1"> - <TBODY> - <TR> - <TH>Base Class</TH> - <TH>Description</TH> - </TR> - <TR> - <TD><samp><A href="../../reference/api/org/eclipse/rse/ui/actions/SystemAbstractPopupMenuExtensionAction.html">SystemAbstractPopupMenuExtensionAction</A></samp> in - <samp>org.eclipse.rse.ui</samp> plugin</TD> - <TD>Base class offering generic support for any remote object pop-up menu action, for any system type.</TD> - </TR> - <TR> - <TD><samp><A href="../../reference/api/org/eclipse/rse/files/ui/actions/SystemAbstractRemoteFilePopupMenuExtensionAction.html">SystemAbstractRemoteFilePopupMenuExtensionAction</A></samp> - in <samp>org.eclipse.rse.files.ui</samp> plugin</TD> - <TD>Specialized base class offering specific support for any remote file object pop-up menu action, for any system type.</TD> - </TR> - </TBODY> -</TABLE> - -<br><hr> -<p>See the <a href="../tutorial/popup.html">pop-up menu action tutorial</a> for a step-by-step example.</p> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/propertypage.html b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/propertypage.html deleted file mode 100755 index d7d71a13e..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/propertypage.html +++ /dev/null @@ -1,77 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>Plugging In Property Pages</title> -</head> - -<body bgcolor="#ffffff"> -<h1>Plugging In Property Pages</h1> -<p>The <samp><A href="../../reference/extension-points/org_eclipse_rse_ui_propertyPages.html">org.eclipse.rse.ui.propertyPages</a></samp> extension point is defined in the -plugin <samp>org.eclipse.rse.ui</samp>, and it is patterned after Eclipse's <samp>org.eclipse.ui.propertyPages</samp> extension point, but both -simplified and extended specifically for remote objects. <BR> -What is a property page? -It is a page that shows up in the Eclipse <A href="propertypage_figure2.gif">Properties dialog</A> that users -get to by right-clicking on an object within any tree or table view, and selecting -the <A href="propertypage_figure1.gif">Properties action</A>.</p> -<p>Extenders supply one or more <samp><page></samp> elements within the beginning and ending <samp><extension></samp> element for this. -The attributes of this <samp><page></samp> element are:</p> -<ul> -<li><b>id</b>. A unique ID for this extension point. Not actually used, but required by Eclipse. -<li><b>name</b>. A translated node-name to show in the left tree view in the Eclipse-supplied -Properties dialog that comes up when the user selects "Properties..." from the pop-up menu. -<li><b>icon</b>. An optional icon to show in the Properties dialog for this property page. -<li><b>class</b>. The fully qualified name of the class that implements the Eclipse interface -<samp>org.Eclipse.ui.IWorkbenchPropertyPage</samp>. This is usually done by extending the Eclipse class -<samp>org.Eclipse.ui.dialog.PropertyPage</samp>. Your class will populate the detail page on the right of the -Eclipse-supplied Properties dialog when the node-name is selected in the left hand tree view. -<li><b><i>filtering criteria</i></b>. To scope which remote objects these property pages should show up for, -there are a series of filtering attributes. These attributes are identical to those in the <samp><A href="popup.html">pop-upMenus</A></samp> -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>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. -<li><b>subtypefilter</b>. Restrict to remote objects matching this simple sub-type filter. The "subtype" of any remote object is subsystem-determined. -<li><b>subsubtypefilter</b>. Restrict to remote objects matching this simple sub-sub-type filter. The "sub-subtype" of any remote object is subsystem-determined. -</ul> -</ul> - -<h2>Programming Details</h2> -<p>To use this extension point your class will typically extend one of the supplied base classes to -make it easier to create these property pages for remote objects. The only method you must implement in these -classes is <samp>createContents(Composite)</samp>, which populates the details page on the right side when the node is -selected on the left side. The supplied classes are listed here: -</p> - -<TABLE border="1"> - <TBODY> - <TR> - <TH>Base Class</TH> - <TH>Description</TH> - </TR> - <TR> - <TD><samp><A href="../../reference/api/org/eclipse/rse/ui/propertypages/SystemAbstractPropertyPageExtensionAction.html">SystemAbstractPropertyPageExtensionAction</A></samp> - in <samp>org.eclipse.rse.ui</samp> plugin.</TD> - <TD>Base class offering generic support for any remote object property page.</TD> - </TR> - <TR> - <TD><samp><A href="../../reference/api/org/eclipse/rse/files/ui/propertypages/SystemAbstractRemoteFilePropertyPageExtensionAction.html">SystemAbstractRemoteFilePropertyPageExtensionAction</A></samp> - in <samp>org.eclipse.rse.files.ui</samp> plugin.</TD> - <TD>Specialized base class offering specific support for any remote file object property page.</TD> - </TR> - </TBODY> -</TABLE> -<p> -</p> - -<br><hr> -<p>See the <a href="../tutorial/propertypage.html">property page tutorial</a> for a step-by-step example.</p> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/propertypage_figure1.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/propertypage_figure1.gif Binary files differdeleted file mode 100755 index 14bda64e8..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/propertypage_figure1.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/propertypage_figure2.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/propertypage_figure2.gif Binary files differdeleted file mode 100755 index 7950bb9aa..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/propertypage_figure2.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html deleted file mode 100755 index 0eb6b5490..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html +++ /dev/null @@ -1,243 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>Plugging In SubSystems</title> -</head> - -<body bgcolor="#ffffff"> -<h1>Plugging In SubSystems</h1> -<p>The <samp><A href="../../reference/extension-points/org_eclipse_rse_ui_subsystemConfigurations.html">org.eclipse.rse.ui.subsystemConfigurations</a></samp> -extension point is defined in the plugin <samp>org.eclipse.rse.ui</samp>. -This is the most complex extension point to use, but also the most powerful. It enables -tool providers to register a class that creates subsystem objects, which appear under -a connection when a connection is expanded in the Remote Systems view. -For example, <A href="RSView_iSeries.gif">here is an iSeries connection</A> with four subsystems, -each created by a subsystem configuration registered with this extension point. -</p> -<p>The <A href="../../reference/extension-points/org_eclipse_rse_ui_subsystemConfiguration.html">extension markup</A> is quite simple for this extension point, -as it has only one element, <b><samp><configuration></samp></b>, with only a few simple attributes to supply: -</p> -<ul> -<li><b>id</b>. Unique id for the extension, as required for all extensions. However, in this case it is used to create -folders within the <samp>RemoteSystemsConnections</samp> project, where all Remote Systems Explorer data is stored. -There is also a way to <A href="../../reference/api/org/eclipse/rse/core/model/ISystemRegistry.html#getSubSystemConfiguration(java.lang.String)">query</A> a subsystem configuration -object via its ID.<li><b>vendor</b>. Your company name, shown in properties dialog for subsystems created by this subsystem configuration. -<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 -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> -and <A href="propertypage.html">propertyPages</A> extension points to allow actions and property pages to be scoped to -resources shown in subsystems of a particular category. Multiple subsystems can have the same category. -<li><b>class</b>. A class implementing <A href="../../reference/api/org/eclipse/rse/core/subsystems/ISubSystemConfiguration.html">ISubSystemConfiguration</A> -interface, as described in the following programming details section. -</ul> - - -<h2>Programming Details</h2> -<p>It is important to remember what the purpose of a subsystem is, and how it fits in the overall RSE <A - href="../Model.html">model</A>, so as to understand the programming details for supporting -subsystems via this subsystem configuration extension point. Minimally speaking, this extension point requires a class that implements the interface -<samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/ISubSystemConfiguration.html"><B>ISubSystemFactory</B></A></samp>. -Ultimately, the intent of a subsystem <I>configuration</I> is to provide individual -subsystem <I>instances</I> to each connection, and the intent of a subsystem instance is to present remote resources for display or manipulation purposes. Thus, you must also create a class implementing the interface <samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/ISubSystem.html"><B>ISubSystem</B></A></samp>. -<BR> -The intent of each subsystem is to show remote resources from the remote system -identified by the parent connection, for the user. (Subsystems can in fact be hidden, which means their their role is to return remote resources for programmatic purposes only.) When the first request is made for remote objects, the subsystem is asked to connect to the remote system if it is not already. -This job is deferred to a <A href="../../reference/api/org/eclipse/rse/core/subsystems/IConnectorService.html">IConnectorService</A> object whose role it is to manage connecting and disconnecting -to the remote physical system. By use of a <A href="../../reference/api/org/eclipse/rse/core/subsystems/AbstractConnectorServiceManager.html">connector service manager</a>, -one system can manage the live connections of multiple subsystems in the same system connection, should they happen to share the same communication pipe. -If filters are <A href="../../reference/api/org/eclipse/rse/core/subsystems/ISubSystemConfiguration.html#supportsFilters()">supported</A> -(the default), the first connection is made, and the remote resources are subsequently shown, when filters within the subsystem -are expanded, which results in a call to -<samp><A href="../../reference/api/org/eclipse/rse/subsystems/files/core/subsystems/RemoteFileSubSystem.html#internalResolveFilterString(org.eclipse.core.runtime.IProgressMonitor, java.lang.String)">resolveFilterString</A></samp> -in the subsystem object. <BR> -Furthermore, you will want to supply your own -<B><A - href="../../reference/api/org/eclipse/rse/ui/filters/actions/SystemNewFilterAction.html">new-filter</A></B> and -<A href="../../reference/api/org/eclipse/rse/ui/filters/actions/SystemChangeFilterAction.html"><B>change-filter</B></A> actions. -If filters are not supported, then these remote resources are shown immediately when the subsystem itself is expanded, via a call to -<samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/ISubSystem.html#getChildren()">getChildren</A></samp>. -Either way the resulting resources are displayed to the user. To facilitate the displaying of these objects in the RSE views, the objects -themselves must implement the Eclipse IAdaptable interface (to enable the property sheet viewer) and there must be a specific RSE -<B><A - href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html">view -adapter</A></B> -and an RSE <B><A - href="../../reference/api/org/eclipse/rse/ui/view/ISystemRemoteElementAdapter.html">remote-information -adapter</A></B> -registered for the remote objects, which the RSE views consult to get the labels, images, actions, -and property sheet values for the remote objects. -Typically, you will supply actions by leveraging the <A - href="../api/uiAPI.html">user interface elements</A> supplied by the RSE, such as base classes for <A - href="../api/messages/uiMessageAPI.html">messages</A>, <A - href="../api/actions/uiActionsAPI.html">actions</A>, <A - href="../api/dialogs/uiDialogsAPI.html">dialogs</A>, <A - href="../api/wizards/uiWizardsAPI.html">wizards</A>, <A - href="../api/properties/uiPropertiesAPI.html">property pages</A> and <A - href="../api/preferences/uiPreferencesAPI.html">preference page editors</A>. You will probably also supply a - property page for your subsystem objects, via the Eclipse <samp>propertyPages</samp> extension point, and for your remote resource objects, via the RSE <A - href="propertypage.html">propertyPages</A> extension point.</p> - -<h3>Base Classes</h3> -<P>For many of the interfaces you must implement, there are base classes supplied that you can extend to make the development effort easier.</P> -<p>The -following summarizes the minimum set of classes you will be creating in order to realize your own subsystem support, including the RSE-supplied base classes to extend:</p> - -<TABLE border="1"> - <TBODY> - <TR> - <TH>Class(es)</TH> - <TH>Base Class</TH> - <TH>Description</TH> - </TR> - <TR> - <TD>subsystem configuration</TD> - <TD><samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/SubSystemConfiguration.html">SubSystemConfiguration</A></samp></TD> - <TD>The factory class responsible for creating instances of subsystem class</TD> - </TR> - <TR> - <TD>subsystem</TD> - <TD><samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/SubSystem.html">SubSystem</A></samp></TD> - <TD>The subsystem class. There will be one instance created for each connection. In addition to storing - your unique attributes, this must return the remote resource objects when a filter is expanded within the - subsystem. How that communication with the remote system is done is left up to you.</TD> - </TR> - <TR> - <TD>system</TD> - <TD><samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/AbstractConnectorService.html">AbstractConnectorService</A></samp></TD> - <TD>Represents and manages a live connection to the remote system, doing the connecting and disconnecting.</TD> - </TR> - <TR> - <TD>system manager</TD> - <TD><samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/AbstractConnectorServiceManager.html">AbstractConnectorServiceManager</A></samp></TD> - <TD>Manages a single system instance that is shared among multiple subsystems in a single connection. Even if you only have a single subsystem configuration it is useful to use this in - case you later add additional factories, and their subsystems share the same communication pipe. To enable this, all your subsystem classes need to implement a unique interface of your own creation.</TD> - </TR> - <TR> - <TD>remote resource</TD> - <TD><samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/AbstractResource.html">AbstractResource</A></samp></TD> - <TD>Can be used as a base class for the objects representing remote resources.</TD> - </TR> - <TR> - <TD>new-filter wizard</TD> - <TD><samp><A href="../../reference/api/org/eclipse/rse/ui/filters/actions/SystemNewFilterAction.html">SystemNewFilterAction</A></samp> and - <samp><A href="../../reference/api/org/eclipse/rse/ui/filters/SystemFilterStringEditPane.html">SystemFilterStringEditPane</A></samp></TD> - <TD>Displays a wizard prompting for a new filter. Filters contain filter strings, which are up to each subsystem to design and interpret. The New Filter wizard - prompts for a single filter string (more can be added in change mode). Typically you subclass <samp>SystemFilterStringEditPane</samp> to create your own - prompt for the filter string information, and then subclass <samp>SystemNewFilterAction</samp> so as to configure the default New Filter wizard to use - your edit pane in the first page.</TD> - </TR> - <TR> - <TD>change-filter dialog</TD> - <TD><samp><A href="../../reference/api/org/eclipse/rse/ui/filters/actions/SystemChangeFilterAction.html">SystemChangeFilterAction</A></samp> and - <samp><A href="../../reference/api/org/eclipse/rse/ui/filters/SystemFilterStringEditPane.html">SystemFilterStringEditPane</A></samp></TD> - <TD>Displays a dialog prompting to change an existing filter. The default dialog allows the user to create and edit filter strings. Typically, you - override the <samp>SystemChangeFilterAction</samp> class, and configure the dialog to use the same edit pane used in the New Filter wizard. - </TD> - </TR> - <TR> - <TD>remote element adapter</TD> - <TD><samp><A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html">AbstractSystemViewAdapter</A></samp> and - <samp><A href="../../reference/api/org/eclipse/rse/ui/view/ISystemRemoteElementAdapter.html">ISystemRemoteElementAdapter</A></samp> - </TD> - <TD>The view adapter is an amalgamation of all the required information needed to populate the RSE views. You will define one class per unique remote object interface or class, and in it you will override methods to return the remote object's label, image, popup-menu actions, property sheet properties and children (if expandable). You can also decide whether to enable common RSE popup menu actions like rename, delete and refresh. <BR>Your view adapter will usually also implement the remote adapter interface, enabling the many common RSE capabilities to work, such as the copy, paste, drag and drop, and more. </TD> - </TR> - </TBODY> -</TABLE> - -<h3><A name="steps"></A>Overview of Steps</h3> -<p>Implementing a subsystem involves the following steps, in the following order:</p> -<OL> - <li>Creating an interface for your subsystem. It can, and often is, an empty interface.</li> - <li>Creating a subclass of <A href="../../reference/api/org/eclipse/rse/core/subsystems/AbstractConnectorService.html">AbstractConnectorService</A>. - The code here will interact as necessary with your subsystem to manage the live connection to the remote system.</li> - <li>Creating a subclass of <A href="../../reference/api/org/eclipse/rse/core/subsystems/AbstractConnectorServiceManager.html">AbstractConnectorServiceManager</A>. - The code here will re-use the same system object from step 2 for all subsystems that implement the interface from step 1, within the same connection.</li> - <li>Designing the classes to represent the remote resources (your <i>model</i>) that you will show from your subsystem. - Each must implement the <samp>org.eclipse.core.runtime.IAdaptable</samp> interface from Eclipse. - It is also very helpful if they also maintain a reference to the subsystem which created them. The base class - <A href="../../reference/api/org/eclipse/rse/core/subsystems/AbstractResource.html">AbstractResource</A> is offered to help with this.</li> - <li>Designing the syntax of the <i>filter string</i> that will be used as a pattern to tell your subsystem what resources to show. For example, for files this might be of the - form "path/generic-name /options". It is the job of your subsystem to interpret these strings and return a list of remote resources matching the - criteria capturing in the string. You will eventually design a user interface to prompt the user for one the - contents of one of these filter strings. You might find it helps to create a class that holds one of these filter strings passed via a constructor, and - can parse it into its constituent pieces via getter methods. It should also support a default constructor and setting of constituent pieces via setter methods, - and the generation of the filter string via toString(). - </li> - <li>Creating a subclass of <A href="../../reference/api/org/eclipse/rse/core/subsystems/SubSystem.html">SubSystem</A> - that implements the interface you designed in step 1. This will: - <ul> - <li>return a singleton instance of the system manager from step 3 in its <A href="../../reference/api/org/eclipse/rse/core/subsystems/SubSystem.html#getSystemManager()">getSystemManager</A> method, - <li>manage persistent properties via calls to the inherited <A href="../../reference/api/org/eclipse/rse/core/subsystems/SubSystem.html#setVendorAttribute(java.lang.String, java.lang.String, java.lang.String)">setVendorAttribute</A> - and <A href="../../reference/api/org/eclipse/rse/core/subsystems/SubSystem.html#getVendorAttribute(java.lang.String, java.lang.String)">getVendorAttribute</A> methods, - <li>use your communications layer to return instances of your model objects in its <A href="../../reference/api/org/eclipse/rse/core/subsystems/SubSystem.html#internalResolveFilterString(org.eclipse.core.runtime.IProgressMonitor, java.lang.String)">internalResolveFilterString</A> method. - The input to this is one or more strings such as you designed in step 5. It will return all remote resources matching the criteria captured in the input filter string. - You may also find the <A href="../../reference/api/org/eclipse/rse/services/clientserver/NamePatternMatcher.html">org.eclipse.rse.services.clientserver.NamePatternMatcher</a> - class to be handy in comparing a generic pattern to a particular input. This class is in the <samp>runtime/clientserver.jar</samp> file, - and has no eclipse-dependencies, so it can be used in your client subsystem code, or your server-side code. - </ul> - </li> - <li>Creating a subclass of <A href="../../reference/api/org/eclipse/rse/core/subsystems/SubSystemConfiguration.html">DefaultSubSystemFactoryImpl.</A></li> - <li>Defining your <A href="../../reference/extension-points/org_eclipse_rse_ui_subsystemConfigurations.html">subsystemConfigurations extension</a> in your <samp>plugin.xml</samp> file.</li> - <li>For each remote resource class you created in step 4, you need to create an adapter class, which extends - <A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html">AbstractSystemViewAdapter</A> and which - implements <A href="../../reference/api/org/eclipse/rse/ui/view/ISystemRemoteElementAdapter.html">ISystemRemoteElementAdapter</A>. - </li> - <li>Register your adapters with the platform. First you create an - adapter class that extends <samp><a href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemRemoteAdapterFactory.html">AbstractSystemRemoteAdapterFactory</a></samp> - and implements interface <samp><b>org.eclipse.core.runtime.IAdapterFactory</b></samp>. Next, - in the <samp>startup()</samp> method of your plugin class, add code to instantiate the class and register the object with - the platform adapter manager, once for each class in your resource model. For example: - <br><samp> - MyAdapterFactory factory = new MyAdapterFactory(); // extends AbstractSystemRemoteAdapterFactory<br> - IAdapterManager manager = Platform.getAdapterManager();<br> - manager.registerAdapters(factory, MyModelObject1.class);<br> - manager.registerAdapters(factory, MyModelObject2.class);<br> - </samp> - </li> - <li>If your filter string from step 5 is complicated enough, you will probably find the - RSE-supplied <a href="NewFilterWizard_Default.gif">filter wizard</a> and - <a href="ChangeFilterDialog_Default.gif">change-dialog</a> insufficient. The idea with these is that the - New Filter wizard prompts in its first page for a single filter string. The change dialog - allows the user to change that single filter string, or add additional filter strings. To - change these for your subsystem, you need to: - <ol> - <li type="i">Create your own - <a href="../../reference/api/org/eclipse/rse/ui/filters/SystemFilterStringEditPane.html">filter string edit pane</a> - subclass that contains your own GUI prompts as desired. - <li type="i">Create your own - <a href="../../reference/api/org/eclipse/rse/ui/filters/actions/SystemNewFilterAction.html">new-filter wizard action</a> - subclass, and configure it to use your own edit pane subclass by overriding - <samp><a href="../../reference/api/org/eclipse/rse/ui/filters/actions/SystemNewFilterAction.html#configureNewFilterWizard(org.eclipse.rse.ui.filters.dialogs.SystemNewFilterWizard)">configureNewFilterWizard</a></samp> - and in it calling <samp><a href="../../reference/api/org/eclipse/rse/ui/filters/dialogs/SystemNewFilterWizard.html#setFilterStringEditPane(org.eclipse.rse.ui.filters.SystemFilterStringEditPane)">setFilterStringEditPane</a></samp> - on the given wizard. - <li type="i">Create your own - <a href="../../reference/api/org/eclipse/rse/ui/filters/actions/SystemChangeFilterAction.html">change-filter action</a> - subclass, and configure it to use your own edit pane subclass by overriding - <samp><a href="../../reference/api/org/eclipse/rse/ui/filters/actions/SystemChangeFilterAction.html#configureFilterDialog(org.eclipse.rse.ui.filters.dialogs.SystemChangeFilterDialog)">configureFilterDialog</a></samp> - and in it calling <samp><a href="../../reference/api/org/eclipse/rse/ui/filters/dialogs/SystemChangeFilterDialog.html#setFilterStringEditPane(org.eclipse.rse.ui.filters.SystemFilterStringEditPane)">setFilterStringEditPane</a></samp> - on the given dialog. - <li type="i">Override the <samp><a href="../../reference/api/org/eclipse/rse/core/subsystems/util/ISubsystemConfigurationAdapter.html#getNewFilterPoolFilterAction(org.eclipse.rse.core.filters.ISystemFilterPool, org.eclipse.swt.widgets.Shell)">getNewFilterPoolFilterAction(SystemFilterPool, Shell)</a></samp> - method in your subsystem factory, to return an instance of your new-filter action. - You can actually avoid creating an action subclass if you choose, by calling the configuration methods - in the RSE-supplied <a href="../../reference/api/org/eclipse/rse/ui/filters/actions/SystemNewFilterAction.html">new-filter action class</a>. - <li type="i">Override the <samp><a href="../../reference/api/org/eclipse/rse/core/subsystems/util/ISubsystemConfigurationAdapter.html#getChangeFilterAction(org.eclipse.rse.core.filters.ISystemFilter, org.eclipse.swt.widgets.Shell)">getChangeFilterAction(SystemFilter, Shell)</a></samp> - method in your subsystem factory, to return an instance of your change-filter action. - You can actually avoid creating an action subclass if you choose, by calling the configuration methods - in the RSE-supplied <a href="../../reference/api/org/eclipse/rse/ui/filters/actions/SystemChangeFilterAction.html">change-filter action class</a>. - </ol> - </li> -</OL> - -<br><hr> -<p>See the <a href="../tutorial/subsystem.html">subsystem tutorial</a> for a step-by-step example.</p> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/systemtype.html b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/systemtype.html deleted file mode 100755 index a19febddc..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/systemtype.html +++ /dev/null @@ -1,37 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>Plugging In System Types</title> -</head> - -<body bgcolor="#ffffff"> -<h1>Plugging In System Types</h1> -<p>The <samp><A href="../../reference/extension-points/org_eclipse_rse_core_systemTypes.html">org.eclipse.rse.core.systemTypes</a></samp> extension point is defined in the -plugin <samp>org.eclipse.rse.core</samp>. It enables new system types to be -defined in the Remote System Explorer's <A href="NewConnection.gif">New -Connection wizard</A>, such that users can define connections to systems of that type. For example, -you might define a new system type of "Solaris" or "RedHat" or some other specific type -of operating system. The reason to define a system type is to enable tools to be created, -via the <A href="subsystem.html">subsystem extension point</A>, that are scoped so as to -only appear for connections to systems of that type. -</p> -<p> -Defining a new system type is easy. You merely need to supply the name of the system -type, and two icons - one icon for connections to that systems of that type, and another -adorned icon that is used when there is a live connection to that particular system. -</p> -<p> -When you create a new connection, the Remote System Explorer framework will consult -each registered <A href="subsystem.html">subsystem extension point</A> to see if it supports -that connection's system type, and if so the extension point's subsystem factory class -will be used to create a new subsystem within the new connection. Thus, when the user -expands a connection in the Remote Systems view, only subsystems supported for that -connection's system type are available. -</p> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_Cmds.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_Cmds.gif Binary files differdeleted file mode 100755 index 377862151..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_Cmds.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_RS.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_RS.gif Binary files differdeleted file mode 100755 index 8ee06ea76..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_RS.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_Table.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_Table.gif Binary files differdeleted file mode 100755 index 0cb086739..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_Table.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_Team.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_Team.gif Binary files differdeleted file mode 100755 index 80bd2c7c7..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/plugin/view_Team.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/preference_activeProfiles.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/preference_activeProfiles.gif Binary files differdeleted file mode 100755 index b241fe998..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/preference_activeProfiles.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/preferences.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/preferences.gif Binary files differdeleted file mode 100755 index e31a1104b..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/preferences.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/rse.gif Binary files differdeleted file mode 100755 index cfdc37dc1..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int.html deleted file mode 100755 index e0fb49b68..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int.html +++ /dev/null @@ -1,16 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-
-<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 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>RSE Programmer's Guide</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-
-<body>
-<h1>RSE Programmer's Guide</h1>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_architecture.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_architecture.html deleted file mode 100755 index 0bb2eeb94..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_architecture.html +++ /dev/null @@ -1,78 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<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 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>RSE Architecture</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>RSE Architecture</h1>
-
-
-<p> The Remote System Explorer is structured into three major layors:</p>
-<ul>
- <li><A href="#Services">Service Layer</A></li>
- <li><A href="#Subsystems">Subsystem Layer</A></li>
- <li><A href="#UIs">UI Layer</A></li>
-</ul>
-
-
-<h2><A name="Services">RSE Service Layer</A></h2>
-<p>
-This is the headless, barebones API layer that is used to interact with different protocols to
-provide remote services that can be integrated into RSE. By default, RSE defines the following
-types of services:
-
- <ul>
- <li>File Service - for listing, modifying, copying, and transfering remote file and folders</li>
- <li>Shell Service - for launching remote shells and interacting with the associated IO</li>
- <li>Process Services - for listing remote processes</li>
-</ul>
- <p>
-New service types can be added as needed, either in core RSE, or extensions to the base. The service
-interfaces are defined loosely so that different implementations of the same service can be made using
-different protocols. For example, the IFileService could be implemented locally with java.io, FTP, DataStore or some
-other protocol. Similarly, the IShellService could be implemented locally via DataStore, telnet, SSH or something
-else.
-</p>
- <h2><A name="SubSystems">RSE Subsystem Layer</A></h2>
-<p>
-RSE subsystems integrate the services of the service layer with connection information, model artifacts and persistence.
-Each subsystem is associated with a single service type. For example, the file service subsystem is associated with the
-file service. Each <a href="rse_int_subsystems.html">subsystem</a> is associated with one or more services from the service layer,
-a <a href="rse_int_connectorservices.html">connector service</a> and, in some cases, a model adapter, which is used to
-convert artifacts from the service layer into a form that is suitable for the subsystem layer.
-</p>
-<p>
-Subsystems are contributed via the subsystem configuration extension point. A subsystem configuration is registered with
-one or more system type (i.e. Local, Linux, Windows, etc.). When there is an RSE <a href="rse_int_hosts.html">host</a>
-of a particular system type, the subsystem configurations that are registered with that system type are used to instantiate
-and configure the subsystems for that host. Each subsystem configuration determines the subsystem to instantiate, the service
-implementation, the connector service and anything else that requires customization for it's service.
-</p>
-<p>
-Multiple subsystem configurations can exist for the same type of subsystem. This will be the case when there are more than
-one protocols that can be used to implement the same service. For example, there are both FTP and DataStore implementations of
-the IFileService. Subsystem configurations are contributed for both the FTP implementation and the DataStore one. In
-such cases, only one subsystem is instantiated for each host, however that subsystem can have its configuration changed from FTP
-to DataStore and vice versa.
-</p>
-<p>
-Subsystems are RSE objects that are persistable and maintain higher level functionality from the service layer. Subsystems that
-are used to query information on a host often have <a href="rse_int_filters.html">filters</a>. Filters provide the user the means to
-specify a criteria for which to query a set of data. In addition to filters, there are more arbitrary properties that can be
-associated with a subsystem, each of which can be saved and restored across sessions.
-</p>
-
-<h2><A name="UI">RSE UI Layer</A></h2>
-<p>
-The Remote System Explorer perspective provides views that render the subsystems and associated artifacts. Users can create
-new connections, which can be expanded to reveal subsystems and the information the subsystems reveal about a system.
-</p>
-
-</body>
-</html>
-
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_connectorservices.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_connectorservices.html deleted file mode 100755 index 0e908d1f8..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_connectorservices.html +++ /dev/null @@ -1,15 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<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 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>RSE Connector Services</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>RSE Connector Services</h1>
-</body>
-</html>
-
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_files.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_files.html deleted file mode 100755 index d9e165406..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_files.html +++ /dev/null @@ -1,16 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-
-<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 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>RSE UI</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-
-<body>
-<h1>RSE Files</h1>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_filters.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_filters.html deleted file mode 100755 index 8040c8990..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_filters.html +++ /dev/null @@ -1,15 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<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 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>RSE Hosts</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>RSE Filters</h1>
-</body>
-</html>
-
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_hosts.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_hosts.html deleted file mode 100755 index 309efcbe5..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_hosts.html +++ /dev/null @@ -1,15 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<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 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>RSE Hosts</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>RSE Hosts</h1>
-</body>
-</html>
-
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_overview.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_overview.html deleted file mode 100755 index 66d81b30e..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_overview.html +++ /dev/null @@ -1,44 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<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 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>RSE Overview</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>RSE Overview</h1>
-<p>
-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
-<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
-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
-shows to the user.
-</p>
-<p>A user can extend the Remote System Explorer by adding their own
-<A href="Artifacts.html#filters">filters</A>,
-<A href="Artifacts.html#useractions">user actions</A>, and
-<A href="Artifacts.html#compilecmds">compile commands</A>.
-They may also customize the RSE by setting
-<A href="Artifacts.html#preferences">preferences</A>.</p>
-<p>
-As a programmer, you can extend the Remote System Explorer by using
-<A href="../reference/extension-points/index.html">RSE-unique extension points</A> to
-add property pages to remote objects, add actions to the pop-up menus for remote objects, and
-even create your own subsystems that appear when a connection is expanded. The full Eclipse application
-programming interface (API) set is
-at your disposal for these, as well as the API set supplied by the Remote System Explorer. Furthermore,
-you can use existing Eclipse extension points to author menu items, tool bar actions, pop-up menu actions,
-and more for non-remote objects in the Remote System Explorer.
-</p>
-<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>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_processes.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_processes.html deleted file mode 100755 index d73ae1dbc..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_processes.html +++ /dev/null @@ -1,16 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-
-<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 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>RSE UI</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-
-<body>
-<h1>RSE Processes</h1>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_services.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_services.html deleted file mode 100755 index 451a1056d..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_services.html +++ /dev/null @@ -1,15 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<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 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>RSE Services</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>RSE Services</h1>
-</body>
-</html>
-
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_shells.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_shells.html deleted file mode 100755 index 774da36b1..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_shells.html +++ /dev/null @@ -1,16 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-
-<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 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>RSE UI</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-
-<body>
-<h1>RSE Shells</h1>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_subsystems.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_subsystems.html deleted file mode 100755 index f4799a539..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_subsystems.html +++ /dev/null @@ -1,15 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-<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 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>RSE Subsystems</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>RSE Subsystems</h1>
-</body>
-</html>
-
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_ui.html b/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_ui.html deleted file mode 100755 index 33bba22aa..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/rse_int_ui.html +++ /dev/null @@ -1,16 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html>
-
-<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 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>RSE UI</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-
-<body>
-<h1>RSE UI</h1>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperAdapterFactory.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperAdapterFactory.html deleted file mode 100755 index ea0623e4c..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperAdapterFactory.html +++ /dev/null @@ -1,58 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>DeveloperAdapterFactory Class After Editing</title>
-</head>
-
-<body>
-<h1>DeveloperAdapterFactory Class After Editing</h1>
-<pre><samp>
-package samples.model;
-
-import org.eclipse.core.runtime.IAdapterFactory;
-import org.eclipse.rse.ui.view.AbstractSystemRemoteAdapterFactory;
-import org.eclipse.rse.ui.view.ISystemViewElementAdapter;
-import org.eclipse.ui.views.properties.IPropertySource;
-
-/**
- * This factory maps requests for an adapter object from a given remote object.
- */
-public class DeveloperAdapterFactory
- extends AbstractSystemRemoteAdapterFactory
- implements IAdapterFactory
-{
- <b>private TeamResourceAdapter teamAdapter = new TeamResourceAdapter();
- private DeveloperResourceAdapter developerAdapter = new DeveloperResourceAdapter();</b>
-
- /**
- * Constructor for DeveloperAdapterFactory.
- */
- public DeveloperAdapterFactory()
- {
- super();
- }
-
- /**
- * @see org.eclipse.core.runtime.IAdapterFactory#getAdapter(Object, Class)
- */
- public Object getAdapter(Object adaptableObject, Class adapterType)
- {
- <b>ISystemViewElementAdapter adapter = null;
- if (adaptableObject instanceof TeamResource)
- adapter = teamAdapter;
- else if (adaptableObject instanceof DeveloperResource)
- adapter = developerAdapter;
- // <i>these lines are very important! </i>
- if ((adapter != null) && (adapterType == IPropertySource.class))
- adapter.setPropertySourceInput(adaptableObject);
- return adapter;</b>
- }
-}
-</samp></pre>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperConnectorService.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperConnectorService.html deleted file mode 100755 index 5a2d8c891..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperConnectorService.html +++ /dev/null @@ -1,100 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>DeveloperConnectorService Class After Editing</title> -</head> - -<body> -<h1>DeveloperConnectorService Class After Editing</h1> -<pre><samp> -package samples.subsystems; - -import org.eclipse.core.runtime.IProgressMonitor; -import org.eclipse.rse.core.subsystems.AbstractConnectorService; -import org.eclipse.rse.core.model.IHost; - -import samples.RSESamplesPlugin; - -/** - * Our system class that manages connecting to, and disconnecting from, - * our remote server-side code. - */ -public class DeveloperConnectorService extends AbstractConnectorService { - - <strong>private boolean connected = false;</strong> - - /** - * Constructor for DeveloperConnectorService. - * @param host - */ - public DeveloperConnectorService(IHost host) - { - super( - RSESamplesPlugin.getResourceString("connectorservice.devr.name"), - RSESamplesPlugin.getResourceString("connectorservice.devr.desc"), - host, - 0 - ); - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.IConnectorService#isConnected() - */ - public boolean isConnected() - { - return connected; - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.AbstractConnectorService#internalConnect(org.eclipse.core.runtime.IProgressMonitor) - */ - protected void internalConnect(IProgressMonitor monitor) throws Exception - { - super.internalConnect(monitor); - // pretend. Normally, we'd connect to our remote server-side code here - connected=true; - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.AbstractConnectorService#internalDisconnect(org.eclipse.core.runtime.IProgressMonitor) - */ - public void internalDisconnect(IProgressMonitor monitor) throws Exception - { - super.internalDisconnect(monitor); - // pretend. Normally, we'd disconnect from our remote server-side code here - connected=false; - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.IConnectorService#supportsRemoteServerLaunching() - */ - public boolean supportsRemoteServerLaunching() - { - return false; - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.IConnectorService#hasRemoteServerLauncherProperties() - */ - public boolean hasRemoteServerLauncherProperties() - { - return false; - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.IConnectorService#supportsServerLaunchProperties() - */ - public boolean supportsServerLaunchProperties() - { - return false; - } - -} -</samp></pre> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperConnectorServiceManager.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperConnectorServiceManager.html deleted file mode 100755 index 7e06dadb6..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperConnectorServiceManager.html +++ /dev/null @@ -1,94 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>DeveloperConnectorServiceManager Class After Editing</title> -</head> - -<body> -<h1>DeveloperConnectorServiceManager Class After Editing</h1> -<pre><samp> -/******************************************************************************** - * Copyright (c) 2006 IBM Corporation. All rights reserved. - * This program and the accompanying materials are made available under the terms - * of the Eclipse Public License v1.0 which accompanies this distribution, and is - * available at http://www.eclipse.org/legal/epl-v10.html - * - * Initial Contributors: - * The following IBM employees contributed to the Remote System Explorer - * component that contains this file: David McKnight, Kushal Munir, - * Michael Berger, David Dykstal, Phil Coulthard, Don Yantzi, Eric Simpson, - * Emily Bruner, Mazen Faraj, Adrian Storisteanu, Li Ding, and Kent Hawley. - * - * Contributors: - * Martin Oberhuber (Wind River) - Adapted original tutorial code to Open RSE. - ********************************************************************************/ - -package samples.subsystems; - -import org.eclipse.rse.core.subsystems.AbstractConnectorServiceManager; -import org.eclipse.rse.core.subsystems.IConnectorService; -import org.eclipse.rse.core.subsystems.ISubSystem; -import org.eclipse.rse.core.model.IHost; - -/** - * This class manages our DeveloperConnectorService objects, so that if we - * ever have multiple subsystem configurations, different subsystems can share - * the same system object if they share the communication layer. - */ -public class DeveloperConnectorServiceManager extends - AbstractConnectorServiceManager { - - <strong>private static DeveloperConnectorServiceManager inst;</strong> - - /** - * Constructor for DeveloperConnectorServiceManager. - */ - public DeveloperConnectorServiceManager() - { - super(); - } - - <strong>/** - * Return singleton instance - */ - public static DeveloperConnectorServiceManager getTheDeveloperConnectorServiceManager() - { - if (inst == null) - inst = new DeveloperConnectorServiceManager(); - return inst; - }</strong> - - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.AbstractConnectorServiceManager#createConnectorService(org.eclipse.rse.core.model.IHost) - */ - public IConnectorService createConnectorService(IHost host) - { - <strong>return new DeveloperConnectorService(host);</strong> - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.AbstractConnectorServiceManager#sharesSystem(org.eclipse.rse.core.subsystems.ISubSystem) - */ - public boolean sharesSystem(ISubSystem otherSubSystem) - { - <strong>return (otherSubSystem instanceof IDeveloperSubSystem);</strong> - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.AbstractConnectorServiceManager#getSubSystemCommonInterface(org.eclipse.rse.core.subsystems.ISubSystem) - */ - public Class getSubSystemCommonInterface(ISubSystem subsystem) - { - <strong>return IDeveloperSubSystem.class;</strong> - } - -} -</samp></pre> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperFilterDialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperFilterDialog.gif Binary files differdeleted file mode 100755 index a281793fd..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperFilterDialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperFilterStringEditPane.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperFilterStringEditPane.html deleted file mode 100755 index 38095d16a..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperFilterStringEditPane.html +++ /dev/null @@ -1,210 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>DeveloperFilterStringEditPane Class After Editing</title>
-</head>
-
-<body>
-<h1>DeveloperFilterStringEditPane Class After Editing</h1>
-<pre><samp>
-package samples.subsystems;
-
-<strong>import org.eclipse.rse.services.clientserver.messages.SystemMessage;
-import org.eclipse.rse.ui.SystemWidgetHelpers;</strong>
-import org.eclipse.rse.ui.filters.SystemFilterStringEditPane;
-<strong>import org.eclipse.swt.events.ModifyEvent;
-import org.eclipse.swt.events.ModifyListener;
-import org.eclipse.swt.layout.GridLayout;
-import org.eclipse.swt.widgets.Composite;
-import org.eclipse.swt.widgets.Control;
-import org.eclipse.swt.widgets.Shell;
-import org.eclipse.swt.widgets.Text;</strong>
-
-<strong>import samples.RSESamplesPlugin;</strong>
-
-/**
- * Our specialized filter string edit pane for developer filters.
- */
-public class DeveloperFilterStringEditPane extends SystemFilterStringEditPane {
-
- // gui widgets
- <strong>private Text textTeam, textDevr;</strong>
-
- /**
- * Constructor for DeveloperFilterStringEditPane.
- * @param shell - parent window
- */
- public DeveloperFilterStringEditPane(Shell shell)
- {
- super(shell);
- }
-
- /**
- * Override of parent method.
- * This is where we populate the client area.
- * @param parent - the composite that will be the parent of the returned client area composite
- * @return Control - a client-area composite populated with widgets.
- *
- * @see org.eclipse.rse.ui.SystemWidgetHelpers
- */
- <strong>public Control createContents(Composite parent)
- {
- // Inner composite
- int nbrColumns = 1;
- Composite composite_prompts = SystemWidgetHelpers.createComposite(parent, nbrColumns);
- ((GridLayout)composite_prompts.getLayout()).marginWidth = 0;
-
- // CREATE TEAM-PARENT PROMPT
- textTeam = SystemWidgetHelpers.createLabeledTextField(
- composite_prompts,
- null,
- RSESamplesPlugin.getResourceString("filter.devr.teamprompt.label"), //$NON-NLS-1$
- RSESamplesPlugin.getResourceString("filter.devr.teamprompt.tooltip") //$NON-NLS-1$
- );
-
- // CREATE DEVELOPER PROMPT
- textDevr = SystemWidgetHelpers.createLabeledTextField(
- composite_prompts,
- null,
- RSESamplesPlugin.getResourceString("filter.devr.devrprompt.label"), //$NON-NLS-1$
- RSESamplesPlugin.getResourceString("filter.devr.devrprompt.tooltip") //$NON-NLS-1$
- );
-
- resetFields();
- doInitializeFields();
-
- // add keystroke listeners...
- textTeam.addModifyListener(
- new ModifyListener()
- {
- public void modifyText(ModifyEvent e)
- {
- validateStringInput();
- }
- }
- );
- textDevr.addModifyListener(
- new ModifyListener()
- {
- public void modifyText(ModifyEvent e)
- {
- validateStringInput();
- }
- }
- );
- return composite_prompts;
- }</strong>
-
- /**
- * Override of parent method.
- * Return the control to recieve initial focus.
- */
- <strong>public Control getInitialFocusControl()
- {
- return textTeam;
- }</strong>
-
- /**
- * Override of parent method.
- * Initialize the input fields based on the inputFilterString, and perhaps refProvider.
- * This can be called before createContents, so test for null widgets first!
- * Prior to this being called, resetFields is called to set the initial default state prior to input
- */
- <strong>protected void doInitializeFields()
- {
- if (textTeam == null)
- return; // do nothing
- if (inputFilterString != null)
- {
- int idx = inputFilterString.indexOf('/');
- if (idx < 0)
- textTeam.setText(inputFilterString);
- else
- {
- textTeam.setText(inputFilterString.substring(0,idx));
- textDevr.setText(inputFilterString.substring(idx+1));
- }
- }
- }</strong>
-
- /**
- * Override of parent method.
- * This is called in the change filter dialog when the user selects "new", or selects another string.
- */
- <strong>protected void resetFields()
- {
- textTeam.setText(""); //$NON-NLS-1$
- textDevr.setText("*"); //$NON-NLS-1$
- }</strong>
-
- /**
- * Override of parent method.
- * Called by parent to decide if information is complete enough to enable finish.
- */
- <strong>protected boolean areFieldsComplete()
- {
- if ((textTeam == null) || (textDevr == null))
- return false;
- else
- return (textTeam.getText().trim().length()>0) && (textDevr.getText().trim().length()>0);
- }</strong>
-
- /**
- * Override of parent method.
- * Get the filter string in its current form.
- * Functional opposite of doInitializeFields, which tears apart the input string in update mode,
- * to populate the GUIs. This method creates the filter string from the information in the GUI.
- */
- <strong>public String getFilterString()
- {
- if ((textTeam == null) || (textDevr == null))
- return inputFilterString; // return what we were given.
- else
- {
- String teamName = textTeam.getText().trim();
- String devrName = textDevr.getText().trim();
- return teamName + "/" + devrName; //$NON-NLS-1$
- }
- }</strong>
-
- /**
- * Override of parent method.
- * Does complete verification of input fields. If this
- * method returns null, there are no errors and the dialog or wizard can close.
- *
- * @return error message if there is one, else null if ok
- */
- <strong>public SystemMessage verify()
- {
- errorMessage = null;
- Control controlInError = null;
-
- /*
- errorMessage = validateTeamInput(); // todo: implement if we want to syntax check input
- if (errorMessage != null)
- controlInError = textTeam;
- else
- {
- errorMessage = validateDevrInput(); // todo: implement to syntax check input
- if (errorMessage != null)
- controlInError = textDevr;
- }
- */
-
- if (errorMessage != null)
- {
- if (controlInError != null)
- controlInError.setFocus();
- }
- return errorMessage;
- }</strong>
-
-}
-</samp></pre>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperFilterWizard.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperFilterWizard.gif Binary files differdeleted file mode 100755 index 9a0b9aed9..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperFilterWizard.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperResource.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperResource.html deleted file mode 100755 index 4da58a080..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperResource.html +++ /dev/null @@ -1,104 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>DeveloperResource Class After Editing</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>DeveloperResource Class After Editing</h1>
-<p>
-<pre><samp>
-package samples.model;
-
-import org.eclipse.rse.core.subsystems.AbstractResource;
-import org.eclipse.rse.core.subsystems.ISubSystem;
-
-/**
- * This models a remote resource representing a developer defined on a particular system.
- */
-public class DeveloperResource extends AbstractResource {
-
- <strong>private String name;</strong>
- <strong>private String id;</strong>
- <strong>private String deptNbr;</strong>
-
- /**
- * Default constructor for DeveloperResource.
- */
- public DeveloperResource()
- {
- super();
- }
-
- /**
- * Constructor for DeveloperResource when given parent subsystem.
- */
- public DeveloperResource(ISubSystem parentSubSystem)
- {
- super(parentSubSystem);
- }
-
- /**
- * Returns the name.
- * @return String
- */
- public String getName()
- {
- return name;
- }
-
- /**
- * Sets the name.
- * @param name The name to set
- */
- public void setName(String name)
- {
- this.name = name;
- }
-
- /**
- * Returns the id.
- * @return String
- */
- public String getId()
- {
- return id;
- }
-
- /**
- * Sets the id.
- * @param id The id to set
- */
- public void setId(String id)
- {
- this.id = id;
- }
-
- /**
- * Returns the deptNbr.
- * @return String
- */
- public String getDeptNbr()
- {
- return deptNbr;
- }
-
- /**
- * Sets the deptNbr.
- * @param deptNbr The deptNbr to set
- */
- public void setDeptNbr(String deptNbr)
- {
- this.deptNbr = deptNbr;
- }
-
-}
-</samp></pre>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperResourceAdapter.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperResourceAdapter.html deleted file mode 100755 index f7cdae861..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperResourceAdapter.html +++ /dev/null @@ -1,219 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>DeveloperResourceAdapter Class After Editing</title>
-</head>
-
-<body>
-<h1>DeveloperResourceAdapter Class After Editing</h1>
-<pre><samp>
-package samples.model;
-
-import org.eclipse.jface.resource.ImageDescriptor;
-import org.eclipse.jface.viewers.IStructuredSelection;
-import org.eclipse.rse.ui.SystemMenuManager;
-import org.eclipse.rse.ui.view.AbstractSystemViewAdapter;
-import org.eclipse.rse.ui.view.ISystemRemoteElementAdapter;
-import org.eclipse.swt.widgets.Shell;
-<strong>import org.eclipse.ui.views.properties.IPropertyDescriptor;</strong>
-<strong>import org.eclipse.ui.views.properties.PropertyDescriptor;</strong>
-
-<strong>import samples.RSESamplesPlugin;</strong>
-
-/**
- * This is the adapter which enables us to work with our remote developer resources.
- */
-public class DeveloperResourceAdapter extends AbstractSystemViewAdapter
- implements ISystemRemoteElementAdapter
-{
-
- /**
- * Constructor
- */
- public DeveloperResourceAdapter() {
- super();
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#addActions(org.eclipse.rse.ui.SystemMenuManager,
- * org.eclipse.jface.viewers.IStructuredSelection, org.eclipse.swt.widgets.Shell, java.lang.String)
- */
- public void addActions(SystemMenuManager menu,
- IStructuredSelection selection, Shell parent, String menuGroup)
- {
- }
-
- /**
- * @see org.eclipse.ui.model.IWorkbenchAdapter#getImageDescriptor(Object)
- */
- public ImageDescriptor getImageDescriptor(Object object)
- {
- <strong>return RSESamplesPlugin.getDefault().getImageDescriptor("ICON_ID_DEVELOPER");</strong>
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getText(java.lang.Object)
- */
- public String getText(Object element)
- {
- <strong>return ((DeveloperResource)element).getName();</strong>
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getAbsoluteName(java.lang.Object)
- */
- public String getAbsoluteName(Object object)
- {
- <strong>DeveloperResource devr = (DeveloperResource)object;</strong>
- r<strong>eturn "Devr_" + devr.getId();</strong>
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getType(java.lang.Object)
- */
- public String getType(Object element)
- {
- <strong>return RSESamplesPlugin.getResourceString("property.devr_resource.type");</strong>
- }
-
- /**
- * @see org.eclipse.ui.model.IWorkbenchAdapter#getParent(Object)
- */
- public Object getParent(Object o)
- {
- return null; // not really used, which is good because it is ambiguous
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#hasChildren(java.lang.Object)
- */
- public boolean hasChildren(Object element)
- {
- return false;
- }
-
- /**
- * @see org.eclipse.ui.model.IWorkbenchAdapter#getChildren(Object)
- */
- public Object[] getChildren(Object o)
- {
- return null;
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#internalGetPropertyDescriptors()
- */
- protected IPropertyDescriptor[] internalGetPropertyDescriptors()
- {
- // the following array should be made static to it isn't created every time
- <strong>PropertyDescriptor[] ourPDs = new PropertyDescriptor[2];</strong>
- <strong>ourPDs[0] = new PropertyDescriptor("devr_id", RSESamplesPlugin.getResourceString("property.devr_id.name"));</strong>
- <strong>ourPDs[0].setDescription(RSESamplesPlugin.getResourceString("property.devr_id.desc"));</strong>
- <strong>ourPDs[1] = new PropertyDescriptor("devr_dept", RSESamplesPlugin.getResourceString("property.devr_dept.name"));</strong>
- <strong>ourPDs[1].setDescription(RSESamplesPlugin.getResourceString("property.devr_dept.desc"));</strong>
- <strong>return ourPDs;</strong>
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#internalGetPropertyValue(java.lang.Object)
- */
- protected Object internalGetPropertyValue(Object key)
- {
- // propertySourceInput holds the currently selected object
- <strong>DeveloperResource devr = (DeveloperResource)propertySourceInput;
- if (key.equals("devr_id"))
- return devr.getId();
- else if (key.equals("devr_dept"))
- return devr.getDeptNbr();
- return null;</strong>
- }
- // --------------------------------------
- // ISystemRemoteElementAdapter methods...
- // --------------------------------------
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getAbsoluteParentName(java.lang.Object)
- */
- public String getAbsoluteParentName(Object element)
- {
- <strong>return "root";</strong> // not really applicable as we have no unique hierarchy
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getSubSystemConfigurationId(java.lang.Object)
- */
- public String getSubSystemConfigurationId(Object element)
- {
- <strong>return "samples.subsystems.factory";</strong> // as declared in extension in plugin.xml
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteTypeCategory(java.lang.Object)
- */
- public String getRemoteTypeCategory(Object element)
- {
- <strong>return "developers";</strong> // Course grained. Same for all our remote resources.
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteType(java.lang.Object)
- */
- public String getRemoteType(Object element)
- {
- <strong>return "developer";</strong> // Fine grained. Unique to this resource type.
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteSubType(java.lang.Object)
- */
- public String getRemoteSubType(Object element)
- {
- return null; // Very fine grained. We don't use it.
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#refreshRemoteObject(java.lang.Object, java.lang.Object)
- */
- public boolean refreshRemoteObject(Object oldElement, Object newElement)
- {
- <strong>DeveloperResource oldDevr= (DeveloperResource)oldElement;
- DeveloperResource newDevr = (DeveloperResource)newElement;
- newDevr.setName(oldDevr.getName());
- return false;</strong>
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteParent(org.eclipse.swt.widgets.Shell, java.lang.Object)
- */
- public Object getRemoteParent(Shell shell, Object element) throws Exception
- {
- return null; // maybe this would be a Department obj, if we fully fleshed out our model
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteParentNamesInUse(org.eclipse.swt.widgets.Shell, java.lang.Object)
- */
- public String[] getRemoteParentNamesInUse(Shell shell, Object element)
- throws Exception
- {
- // developers names do not have to be unique! So we don't need to implement this!
- return null;
-
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#supportsUserDefinedActions(java.lang.Object)
- */
- public boolean supportsUserDefinedActions(Object object) {
- <strong>return false;</strong>
- }
-
-}
-</samp></pre>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystem.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystem.html deleted file mode 100755 index cd27ebf58..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystem.html +++ /dev/null @@ -1,202 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>DeveloperSubSystem Class After Editing</title> -</head> - -<body bgcolor="#ffffff"> -<h1>DeveloperSubSystem Class After Editing</h1> -<pre><samp> -package samples.subsystems; - -<strong>import java.util.Vector; - -import org.eclipse.core.runtime.IProgressMonitor; -import org.eclipse.rse.core.subsystems.IConnectorService;</strong> -import org.eclipse.rse.core.subsystems.SubSystem; -<strong>import org.eclipse.rse.core.model.IHost; -import org.eclipse.rse.services.clientserver.NamePatternMatcher; - -import samples.model.DeveloperResource; -import samples.model.TeamResource;</strong> - -<strong>/** - * This is our subsystem, which manages the remote connection and resources for - * a particular system connection object. - */</strong> -public class DeveloperSubSystem extends SubSystem -{ - <strong>private TeamResource[] teams; // faked-out master list of teams</strong> - <strong>private Vector devVector = new Vector(); // faked-out master list of developers</strong> - <strong>private static int employeeId = 123456; // employee Id factory</strong> - - /** - * @param host - * @param connectorService - */ - public DeveloperSubSystem(IHost host, IConnectorService connectorService) { - super(host, connectorService); - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.SubSystem#initializeSubSystem(org.eclipse.core.runtime.IProgressMonitor) - */ - public void initializeSubSystem(IProgressMonitor monitor) { - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.ISubSystem#uninitializeSubSystem(org.eclipse.core.runtime.IProgressMonitor) - */ - public void uninitializeSubSystem(IProgressMonitor monitor) { - } - - <strong>/** - * For drag and drop, and clipboard support of remote objects. - * - * Return the remote object within the subsystem that corresponds to - * the specified unique ID. Because each subsystem maintains it's own - * objects, it's the responsability of the subsystem to determine - * how an ID (or key) for a given object maps to the real object. - * By default this returns null. - */ - public Object getObjectWithAbsoluteName(String key) - { - // Functional opposite of getAbsoluteName(Object) in our resource adapters - if (key.startsWith("Team_")) //$NON-NLS-1$ - { - String teamName = key.substring(5); - TeamResource[] allTeams = getAllTeams(); - for (int idx=0; idx < allTeams.length; idx++) - if (allTeams[idx].getName().equals(teamName)) - return allTeams[idx]; - } - else if (key.startsWith("Devr_")) //$NON-NLS-1$ - { - String devrId = key.substring(5); - DeveloperResource[] devrs = getAllDevelopers(); - for (int idx=0; idx < devrs.length; idx++) - if (devrs[idx].getId().equals(devrId)) - return devrs[idx]; - } - return null; - }</strong> - - <strong>/** - * When a filter is expanded, this is called for each filter string in the filter. - * Using the criteria of the filter string, it must return objects representing remote resources. - * For us, this will be an array of TeamResource objects. - * - * @param monitor - the progress monitor in effect while this operation performs - * @param filterString - one of the filter strings from the expanded filter. - */ - protected Object[] internalResolveFilterString(IProgressMonitor monitor, String filterString) - throws java.lang.reflect.InvocationTargetException, - java.lang.InterruptedException - { - // Fake it out for now and return dummy list. - // In reality, this would communicate with remote server-side code/data. - TeamResource[] allTeams = getAllTeams(); - - // Now, subset master list, based on filter string... - NamePatternMatcher subsetter = new NamePatternMatcher(filterString); - Vector v = new Vector(); - for (int idx = 0; idx < allTeams.length; idx++) - { - if (subsetter.matches(allTeams[idx].getName())) - v.addElement(allTeams[idx]); - } - TeamResource[] teams = new TeamResource[v.size()]; - for (int idx=0; idx < v.size(); idx++) - teams[idx] = (TeamResource)v.elementAt(idx); - return teams; - }</strong> - - <strong>/** - * When a remote resource is expanded, this is called to return the children of the resource, if - * the resource's adapter states the resource object is expandable. - * For us, it is a Team resource that was expanded, and an array of Developer resources will be returned. - * - * @param monitor - the progress monitor in effect while this operation performs - * @param parent - the parent resource object being expanded - * @param filterString - typically defaults to "*". In future additional user-specific quick-filters may be supported. - */ - <a id="resolveFilterString"/>protected Object[] internalResolveFilterString(IProgressMonitor monitor, Object parent, String filterString) - throws java.lang.reflect.InvocationTargetException, - java.lang.InterruptedException - { - // typically we ignore the filter string as it is always "*" - // until support is added for "quick filters" the user can specify/select - // at the time they expand a remote resource. - - TeamResource team = (TeamResource)parent; - return team.getDevelopers(); - }</strong> - - <strong>// ------------------ - // Our own methods... - // ------------------</strong> - - <strong>/** - * Get the list of all teams. Normally this would involve a trip the server, but we - * fake it out and return a hard-coded local list. - */ - public TeamResource[] getAllTeams() - { - if (teams == null) - teams = createTeams("Team ", 4); - return teams; - }</strong> - - <strong>/** - * Get the list of all developers. Normally this would involve a trip the server, but we - * fake it out and return a hard-coded local list. - */ - public DeveloperResource[] getAllDevelopers() - { - DeveloperResource[] allDevrs = new DeveloperResource[devVector.size()]; - for (int idx = 0; idx < allDevrs.length; idx++) - allDevrs[idx] = (DeveloperResource)devVector.elementAt(idx); - return allDevrs; - }</strong> - - <strong>/* - * Create and return a dummy set of teams - */ - private TeamResource[] createTeams(String prefix, int howMany) - { - TeamResource[] teams = new TeamResource[howMany]; - for (int idx = 0; idx < teams.length; idx++) - { - teams[idx] = new TeamResource(this); - teams[idx].setName(prefix + (idx+1)); - teams[idx].setDevelopers(createDevelopers(teams[idx].getName()+" developer",idx+1)); - } - return teams; - }</strong> - - <strong>/* - * Create and return a dummy set of developers - */ - private DeveloperResource[] createDevelopers(String prefix, int nbr) - { - DeveloperResource[] devrs = new DeveloperResource[nbr]; - for (int idx=0; idx < devrs.length; idx++) - { - devrs[idx] = new DeveloperResource(this); - devrs[idx].setName(prefix + (idx+1)); - devrs[idx].setId(Integer.toString(employeeId++)); - devrs[idx].setDeptNbr(Integer.toString((idx+1)*100)); - devVector.add(devrs[idx]); // update master list - } - return devrs; - }</strong> - -} -</samp></pre> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystem2.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystem2.html deleted file mode 100755 index 060d235f5..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystem2.html +++ /dev/null @@ -1,233 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>DeveloperSubSystem Class After Editing Supporting Multiple Filter Types</title> -</head> - -<body> -<h1>DeveloperSubSystem Class After Editing Supporting Multiple Filter Types</h1> -<pre><samp> -package samples.subsystems; - -import java.util.Vector; - -import org.eclipse.core.runtime.IProgressMonitor; -import org.eclipse.rse.core.subsystems.IConnectorService; -import org.eclipse.rse.core.subsystems.SubSystem; -import org.eclipse.rse.core.model.IHost; -import org.eclipse.rse.services.clientserver.NamePatternMatcher; - -import samples.model.DeveloperResource; -import samples.model.TeamResource; - -/** - * This is our subsystem, which manages the remote connection and resources for - * a particular system connection object. - */ -public class DeveloperSubSystem extends SubSystem -{ - private TeamResource[] teams; // faked-out master list of teams - private Vector devVector = new Vector(); // faked-out master list of developers - private static int employeeId = 123456; // employee Id factory - - /** - * @param host - * @param connectorService - */ - public DeveloperSubSystem(IHost host, IConnectorService connectorService) { - super(host, connectorService); - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.SubSystem#initializeSubSystem(org.eclipse.core.runtime.IProgressMonitor) - */ - public void initializeSubSystem(IProgressMonitor monitor) { - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.ISubSystem#uninitializeSubSystem(org.eclipse.core.runtime.IProgressMonitor) - */ - public void uninitializeSubSystem(IProgressMonitor monitor) { - } - - /** - * For drag and drop, and clipboard support of remote objects. - * - * Return the remote object within the subsystem that corresponds to - * the specified unique ID. Because each subsystem maintains it's own - * objects, it's the responsability of the subsystem to determine - * how an ID (or key) for a given object maps to the real object. - * By default this returns null. - */ - public Object getObjectWithAbsoluteName(String key) - { - // Functional opposite of getAbsoluteName(Object) in our resource adapters - if (key.startsWith("Team_")) - { - String teamName = key.substring(5); - TeamResource[] allTeams = getAllTeams(); - for (int idx = 0; idx < allTeams.length; idx++) - if (allTeams[idx].getName().equals(teamName)) - return allTeams[idx]; - } - else if (key.startsWith("Devr_")) - { - String devrId = key.substring(5); - DeveloperResource[] devrs = getAllDevelopers(); - for (int idx=0; idx < devrs.length; idx++) - if (devrs[idx].getId().equals(devrId)) - return devrs[idx]; - } - return null; - } - - /** - * When a filter is expanded, this is called for each filter string in the filter. - * Using the criteria of the filter string, it must return objects representing remote resources. - * For us, this will be an array of TeamResource objects. - * - * @param monitor - the progress monitor in effect while this operation performs - * @param filterString - one of the filter strings from the expanded filter. - */ - protected Object[] internalResolveFilterString(IProgressMonitor monitor, String filterString) - throws java.lang.reflect.InvocationTargetException, - java.lang.InterruptedException - { - <strong>int slashIdx = filterString.indexOf('/'); - if (slashIdx < 0) - {</strong> - // Fake it out for now and return dummy list. - // In reality, this would communicate with remote server-side code/data. - TeamResource[] allTeams = getAllTeams(); - - // Now, subset master list, based on filter string... - NamePatternMatcher subsetter = new NamePatternMatcher(filterString); - Vector v = new Vector(); - for (int idx=0; idx <1; allTeams.length; idx++) - { - if (subsetter.matches(allTeams[idx].getName())) - v.addElement(allTeams[idx]); - } - TeamResource[] teams = new TeamResource[v.size()]; - for (int idx=0; idx < v.size(); idx++) - teams[idx] = (TeamResource)v.elementAt(idx); - return teams; - <strong>} - else - { - String teamName = filterString.substring(0, slashIdx); - String devrName = filterString.substring(slashIdx+1); - TeamResource[] allTeams = getAllTeams(); - TeamResource match = null; - for (int idx=0; (match==null) && (idx < allTeams.length); idx++) - if (allTeams[idx].getName().equals(teamName)) - match = allTeams[idx]; - if (match != null) - { - DeveloperResource[] allDevrs = match.getDevelopers(); - // Now, subset master list, based on filter string... - NamePatternMatcher subsetter = new NamePatternMatcher(devrName); - Vector v = new Vector(); - for (int idx=0; idx < allDevrs.length; idx++) - { - if (subsetter.matches(allDevrs[idx].getName())) - v.addElement(allDevrs[idx]); - } - DeveloperResource[] devrs = new DeveloperResource[v.size()]; - for (int idx=0; idx < v.size(); idx++) - devrs[idx] = (DeveloperResource)v.elementAt(idx); - return devrs; - } - } - return null;</strong> - } - - /** - * When a remote resource is expanded, this is called to return the children of the resource, if - * the resource's adapter states the resource object is expandable. <br> - * For us, it is a Team resource that was expanded, and an array of Developer resources will be returned. - * - * @param monitor - the progress monitor in effect while this operation performs - * @param parent - the parent resource object being expanded - * @param filterString - typically defaults to "*". In future additional user-specific quick-filters may be supported. - */ - protected Object[] internalResolveFilterString(IProgressMonitor monitor, Object parent, String filterString) - throws java.lang.reflect.InvocationTargetException, - java.lang.InterruptedException - { - // typically we ignore the filter string as it is always "*" - // until support is added for "quick filters" the user can specify/select - // at the time they expand a remote resource. - - TeamResource team = (TeamResource)parent; - return team.getDevelopers(); - } - - // ------------------ - // Our own methods... - // ------------------ - - /** - * Get the list of all teams. Normally this would involve a trip the server, but we - * fake it out and return a hard-coded local list. - */ - public TeamResource[] getAllTeams() - { - if (teams == null) - teams = createTeams("Team ", 4); - return teams; - } - - /** - * Get the list of all developers. Normally this would involve a trip the server, but we - * fake it out and return a hard-coded local list. - */ - public DeveloperResource[] getAllDevelopers() - { - DeveloperResource[] allDevrs = new DeveloperResource[devVector.size()]; - for (int idx=0; idx < allDevrs.length; idx++) - allDevrs[idx] = (DeveloperResource)devVector.elementAt(idx); - return allDevrs; - } - - /* - * Create and return a dummy set of teams - */ - private TeamResource[] createTeams(String prefix, int howMany) - { - TeamResource[] teams = new TeamResource[howMany]; - for (int idx=0; idx < teams.length; idx++) - { - teams[idx] = new TeamResource(this); - teams[idx].setName(prefix + (idx+1)); - teams[idx].setDevelopers(createDevelopers(teams[idx].getName()+" developer",idx+1)); - } - return teams; - } - - /* - * Create and return a dummy set of developers - */ - private DeveloperResource[] createDevelopers(String prefix, int nbr) - { - DeveloperResource[] devrs = new DeveloperResource[nbr]; - for (int idx=0; idx < devrs.length; idx++) - { - devrs[idx] = new DeveloperResource(this); - devrs[idx].setName(prefix + (idx+1)); - devrs[idx].setId(Integer.toString(employeeId++)); - devrs[idx].setDeptNbr(Integer.toString((idx+1)*100)); - devVector.add(devrs[idx]); // update master list - } - return devrs; - } - -} -</samp></pre> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystemConfiguration.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystemConfiguration.html deleted file mode 100755 index 9e73c074f..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystemConfiguration.html +++ /dev/null @@ -1,102 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>DeveloperSubSystemConfiguration Class After Editing</title> -</head> - -<body> -<h1>DeveloperSubSystemConfiguration Class After Editing</h1> -<pre><samp> -package samples.subsystems; - -<strong>import java.util.Vector;</strong> - -<strong>import org.eclipse.rse.core.subsystems.IConnectorService; -import org.eclipse.rse.core.subsystems.ISubSystem;</strong> -import org.eclipse.rse.core.subsystems.SubSystemConfiguration; -<strong>import org.eclipse.rse.core.filters.ISystemFilterPool; -import org.eclipse.rse.core.filters.ISystemFilterPoolManager; -import org.eclipse.rse.core.filters.ISystemFilter; -import org.eclipse.rse.core.model.IHost;</strong> - -<strong>import samples.RSESamplesPlugin;</strong> - -/** - * This is our subsystem factory, which creates instances of our subsystems, - * and supplies the subsystem and filter actions to their popup menus. - */ -public class DeveloperSubSystemConfiguration extends SubSystemConfiguration { - - /** - * Constructor for DeveloperSubSystemConfiguration. - */ - public DeveloperSubSystemConfiguration() { - super(); - } - - /** - * Create an instance of our subsystem. - */ - <strong>public ISubSystem createSubSystemInternal(IHost conn) { - return new DeveloperSubSystem(conn, getConnectorService(conn)); - }</strong> - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.ISubSystemConfiguration#getConnectorService(org.eclipse.rse.core.model.IHost) - */ - public IConnectorService getConnectorService(IHost host) { - <strong>return DeveloperConnectorServiceManager.getTheDeveloperConnectorServiceManager() - .getConnectorService(host, IDeveloperSubSystem.class);</strong> - } - - /** - * Intercept of parent method that creates an initial default filter pool. - * We intercept so that we can create an initial filter in that pool, which will - * list all teams. - */ - <a id="createDefaultFilterPool"/><strong>protected ISystemFilterPool createDefaultFilterPool(ISystemFilterPoolManager mgr) - { - ISystemFilterPool defaultPool = null; - try { - defaultPool = mgr.createSystemFilterPool(getDefaultFilterPoolName(mgr.getName(), getId()), true); // true=>is deletable by user - Vector strings = new Vector(); - strings.add("*"); - mgr.createSystemFilter(defaultPool, "All teams", strings); - } catch (Exception exc) {} - return defaultPool; - }</strong> - - /** - * Intercept of parent method so we can supply our own value shown in the property - * sheet for the "type" property when a filter is selected within our subsystem. - * - * Requires this line in rseSamplesResources.properties: property.type.teamfilter=Team filter - */ - <strong>public String getTranslatedFilterTypeProperty(ISystemFilter selectedFilter) - { - return RSESamplesPlugin.getResourceString("property.type.teamfilter"); - }</strong> - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.SubSystemConfiguration#supportsUserId() - */ - <strong>public boolean supportsUserId() { - return false; - }</strong> - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.SubSystemConfiguration#supportsServerLaunchProperties(org.eclipse.rse.core.model.IHost) - */ - <strong>public boolean supportsServerLaunchProperties(IHost host) { - return false; - }</strong> - -} -</samp></pre> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystemConfiguration2.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystemConfiguration2.html deleted file mode 100755 index 6729261ec..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystemConfiguration2.html +++ /dev/null @@ -1,112 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css"> -<title>DeveloperSubSystemFactory Class After Editing For Filter Support</title> -</head> - -<body> -<h1>DeveloperSubSystemFactory Class After Editing For Filter Support</h1> -<pre><samp> -package samples.subsystems; - -import java.util.Vector; - -import org.eclipse.rse.core.subsystems.IConnectorService; -import org.eclipse.rse.core.subsystems.ISubSystem; -import org.eclipse.rse.core.subsystems.SubSystemConfiguration; -import org.eclipse.rse.core.filters.ISystemFilter; -import org.eclipse.rse.core.filters.ISystemFilterPool; -import org.eclipse.rse.core.filters.ISystemFilterPoolManager; -import org.eclipse.rse.core.filters.ISystemFilter; -import org.eclipse.rse.core.model.IHost; - -import samples.RSESamplesPlugin; - -/** - * This is our subsystem factory, which creates instances of our subsystems, - * and supplies the subsystem and filter actions to their popup menus. - */ -public class DeveloperSubSystemConfiguration extends SubSystemConfiguration { - - /** - * Constructor for DeveloperSubSystemConfiguration. - */ - public DeveloperSubSystemConfiguration() { - super(); - } - - /** - * Create an instance of our subsystem. - */ - public ISubSystem createSubSystemInternal(IHost conn) { - return new DeveloperSubSystem(conn, getConnectorService(conn)); - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.ISubSystemConfiguration#getConnectorService(org.eclipse.rse.core.model.IHost) - */ - public IConnectorService getConnectorService(IHost host) { - return DeveloperConnectorServiceManager.getTheDeveloperConnectorServiceManager() - .getConnectorService(host, IDeveloperSubSystem.class); - } - - /** - * Intercept of parent method that creates an initial default filter pool. - * We intercept so that we can create an initial filter in that pool, which will - * list all teams. - */ - protected ISystemFilterPool createDefaultFilterPool(ISystemFilterPoolManager mgr) - { - ISystemFilterPool defaultPool = null; - try { - defaultPool = mgr.createSystemFilterPool(getDefaultFilterPoolName(mgr.getName(), getId()), true); // true=>is deletable by user - Vector strings = new Vector(); - strings.add("*"); - I<strong>SystemFilter filter = mgr.createSystemFilter(defaultPool, - RSESamplesPlugin.getResourceString("filter.default.name"), - strings); - filter.setType("team");</strong> - } catch (Exception exc) {} - return defaultPool; - } - - /** - * Intercept of parent method so we can supply our own value shown in the property - * sheet for the "type" property when a filter is selected within our subsystem. - * - * Requires this line in rseSamplesResources.properties: property.type.teamfilter=Team filter - */ - public String getTranslatedFilterTypeProperty(ISystemFilter selectedFilter) - { - <strong>String type = selectedFilter.getType(); - if (type == null) - type = "team"; - if (type.equals("team")) - return RSESamplesPlugin.getResourceString("property.type.teamfilter"); - else - return RSESamplesPlugin.getResourceString("property.type.devrfilter");</strong> - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.SubSystemConfiguration#supportsUserId() - */ - public boolean supportsUserId() { - return false; - } - - /* (non-Javadoc) - * @see org.eclipse.rse.core.subsystems.SubSystemConfiguration#supportsServerLaunchProperties(org.eclipse.rse.core.model.IHost) - */ - public boolean supportsServerLaunchProperties(IHost host) { - return false; - } - -} -</samp></pre> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/FolderInfoPropertyPage1.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/FolderInfoPropertyPage1.html deleted file mode 100755 index 61fb592d5..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/FolderInfoPropertyPage1.html +++ /dev/null @@ -1,47 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>FolderInfoPropertyPage Class After Creation</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>FolderInfoPropertyPage Class After Creation</h1>
-<p>
-<pre><samp>
-package samples.ui.propertypages;
-
-import org.eclipse.swt.widgets.Composite;
-import org.eclipse.swt.widgets.Control;
-
-import org.eclipse.rse.files.ui.propertypages.SystemAbstractRemoteFilePropertyPageExtensionAction;
-
-public class <b>FolderInfoPropertyPage</b>
- extends SystemAbstractRemoteFilePropertyPageExtensionAction
-{
-
- /**
- * Constructor for FolderInfoPropertyPage.
- */
- public <b>FolderInfoPropertyPage</b>()
- {
- super();
- }
-
- /**
- * @see org.eclipse.rse.ui.propertypages.SystemBasePropertyPage#createContentArea(Composite)
- */
- protected Control <b>createContentArea</b>(Composite parent)
- {
- return null;
- }
-
-}
-</samp></pre>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/FolderInfoPropertyPage2.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/FolderInfoPropertyPage2.html deleted file mode 100755 index 40b45e2e8..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/FolderInfoPropertyPage2.html +++ /dev/null @@ -1,243 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>FolderInfoPropertyPage Class After Editing</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>FolderInfoPropertyPage Class After Editing</h1>
-<p>
-<pre><samp>
-package samples.ui.propertypages;
-
-import org.eclipse.swt.widgets.*;
-import org.eclipse.swt.events.*;
-
-import RSESamples.*;
-import org.eclipse.rse.files.ui.propertypages.SystemAbstractRemoteFilePropertyPageExtensionAction;
-import com.ibm.etools.systems.subsystems.*;
-import com.ibm.etools.systems.core.ui.*;
-
-import java.util.*;
-
-/**
- * A sample property page for a remote object, which in this case is scoped via the
- * extension point xml to only apply to folder objects.
- */
-public class <b>FolderInfoPropertyPage</b>
- extends SystemAbstractRemoteFilePropertyPageExtensionAction
- implements SelectionListener
-{
- // gui widgets...
- private Label sizeLabel, filesLabel, foldersLabel;
- private Button stopButton;
- // state...
- private int totalSize = 0;
- private int totalFolders = 0;
- private int totalFiles = 0;
- private boolean stopped = false;
- private Thread workerThread;
- private Runnable guiUpdater;
-
- /**
- * Constructor for FolderInfoPropertyPage.
- */
- public <b>FolderInfoPropertyPage</b>()
- {
- super();
- }
-
- // --------------------------
- // <i>Parent method overrides...</i>
- // --------------------------
-
- /**
- * @see org.eclipse.rse.ui.propertypages.SystemBasePropertyPage#createContentArea(Composite)
- */
- protected Control <b>createContentArea</b>(Composite parent)
- {
- Composite composite = SystemWidgetHelpers.createComposite(parent, 2);
- ResourceBundle rb = RSESamplesPlugin.getDefault().getResourceBundle();
- // draw the gui
- sizeLabel = SystemWidgetHelpers.createLabeledLabel(composite, rb, "pp.size.", false);
- filesLabel = SystemWidgetHelpers.createLabeledLabel(composite, rb, "pp.files.", false);
- foldersLabel = SystemWidgetHelpers.createLabeledLabel(composite, rb, "pp.folders.", false);
- stopButton = SystemWidgetHelpers.createPushButton(composite, null, rb, "pp.stopButton.");
- stopButton.addSelectionListener(this);
-
- setValid(false); // Disable OK button until thread is done
-
- // show "Processing..." message
- setMessage(RSESamplesPlugin.getPluginMessage("RSSG1002"));
-
- // create instance of Runnable to allow asynchronous GUI updates from background thread
- guiUpdater = new RunnableGUIClass();
- // spawn a thread to calculate the information
- workerThread = new RunnableClass(getRemoteFile());
- workerThread.start();
-
- return composite;
- }
-
- /**
- * Intercept from PreferencePage. Called when user presses Cancel button.
- * We stop the background thread.
- */
- public boolean <b>performCancel</b>()
- {
- killThread();
- return true;
- }
-
- /**
- * Intercept from DialogPage. Called when dialog going away.
- * If the user presses the X to close this dialog, we
- * need to stop that background thread.
- */
- public void <b>dispose</b>()
- {
- killThread();
- super.dispose();
- }
-
- /**
- * Private method to kill our background thread.
- * Control doesn't return until it ends.
- */
- private void <b>killThread</b>()
- {
- if (!stopped && workerThread.isAlive())
- {
- stopped = true;
- try {
- workerThread.join(); // wait for thread to end
- } catch (InterruptedException exc) {}
- }
- }
-
- // -------------------------------------------
- // <i>Methods from SelectionListener interface...</i>
- // -------------------------------------------
-
- /**
- * From SelectionListener
- */
- public void <b>widgetSelected</b>(SelectionEvent event)
- {
- if (event.getSource() == stopButton)
- {
- stopped = true;
- stopButton.setEnabled(false);
- }
- }
- /**
- * From SelectionListener
- */
- public void <b>widgetDefaultSelected</b>(SelectionEvent event) {}
-
-
- // ----------------
- // <i>Inner classes...</i>
- // ----------------
- /**
- * Inner class encapsulating the background work to be done, so it may be executed
- * in background thread.
- */
- private class <b>RunnableClass</b> extends Thread
- {
- IRemoteFile inputFolder;
-
- <b>RunnableClass</b>(IRemoteFile inputFolder)
- {
- this.inputFolder = inputFolder;
- }
-
- public void <b>run</b>()
- {
- if (stopped)
- return;
- walkFolder(inputFolder);
- updateGUI();
- if (!stopped)
- {
- stopped = true;
- updateGUI();
- }
- }
-
- /**
- * Recursively walk a folder, updating the running tallies.
- * Update the GUI after processing each subfolder.
- */
- private void <b>walkFolder</b>(IRemoteFile currFolder)
- {
- IRemoteFile[] folders = currFolder.getParentRemoteFileSubSystem().listFoldersAndFiles(currFolder);
- if ((folders != null) && (folders.length>0))
- {
- for (int idx=0; !stopped && (idx<folders.length); idx++)
- {
- // is this a folder?
- if (folders[idx].isDirectory())
- {
- ++totalFolders;
- walkFolder(folders[idx]);
- updateGUI();
- }
- // is this a file?
- else
- {
- ++totalFiles;
- totalSize += folders[idx].getLength();
- }
- }
- }
- } // <i>end of walkFolder method</i>
-
- } // <i>end of inner class</i>
-
- /**
- * Inner class encapsulating the GUI work to be done from the
- * background thread.
- */
- private class <b>RunnableGUIClass</b> implements Runnable
- {
- public void <b>run</b>()
- {
- if (stopButton.isDisposed())
- return;
- if (!stopped)
- {
- sizeLabel.setText(Integer.toString(totalSize));
- filesLabel.setText(Integer.toString(totalFiles));
- foldersLabel.setText(Integer.toString(totalFolders));
- }
- else if (stopped)
- {
- setValid(true); // re-enable OK button
- stopButton.setEnabled(false); // disable Stop button
- clearMessage(); // clear "Processing..." message
- }
- }
- }
-
-
- /**
- * Update the GUI with the current status
- */
- private void <b>updateGUI</b>()
- {
- Display.getDefault().asyncExec(guiUpdater);
- }
-
-}
-
-
-</samp></pre>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/IDeveloperSubSystem.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/IDeveloperSubSystem.html deleted file mode 100755 index cf13a5a2d..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/IDeveloperSubSystem.html +++ /dev/null @@ -1,30 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>IDeveloperSubSystem Interface After Creation</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>IDeveloperSubSystem Interface After Creation</h1>
-<p>
-<pre><samp>
-package samples.subsystems;
-
-/**
- * Interface identifying our unique subsystems
- */
-public interface <b>IDeveloperSubSystem</b>
-{
-
-}
-
-</samp></pre>
-</p>
-</body>
-</html>
-
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/InitializeImageRegistry.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/InitializeImageRegistry.html deleted file mode 100755 index 2d618b753..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/InitializeImageRegistry.html +++ /dev/null @@ -1,26 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>InitializeImageRegistry Method</title>
-</head>
-
-<body>
-<h1>InitializeImageRegistry Method</h1>
-<pre><samp>
- /**
- * <i>Initialize the image registry by declaring all of the required graphics.</i>
- */
- protected void initializeImageRegistry()
- {
- String path = getIconPath();
- <b>putImageInRegistry("ICON_ID_TEAM", path + "team.gif");</b>
- <b>putImageInRegistry("ICON_ID_DEVELOPER", path + "developer.gif");</b>
- }
-</samp></pre>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/InitializeImageRegistry2.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/InitializeImageRegistry2.html deleted file mode 100755 index b62de4e67..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/InitializeImageRegistry2.html +++ /dev/null @@ -1,28 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>InitializeImageRegistry Method</title>
-</head>
-
-<body>
-<h1>InitializeImageRegistry Method</h1>
-<pre><samp>
- /**
- * <i>Initialize the image registry by declaring all of the required graphics.</i>
- */
- protected void initializeImageRegistry()
- {
- String path = getIconPath();
- putImageInRegistry("ICON_ID_TEAM", path + "team.gif");
- putImageInRegistry("ICON_ID_DEVELOPER", path + "developer.gif");
- <b>putImageInRegistry("ICON_ID_TEAMFILTER", path + "teamFilter.gif");</b>
- <b>putImageInRegistry("ICON_ID_DEVELOPERFILTER", path + "developerFilter.gif");</b>
- }
-</samp></pre>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/NewFilterActions.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/NewFilterActions.gif Binary files differdeleted file mode 100755 index 473b3fa4d..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/NewFilterActions.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/NewFilterIcons.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/NewFilterIcons.gif Binary files differdeleted file mode 100755 index 4889771e5..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/NewFilterIcons.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/NewFilterWizard.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/NewFilterWizard.gif Binary files differdeleted file mode 100755 index 692fbb263..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/NewFilterWizard.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/RSESamplesPlugin.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/RSESamplesPlugin.html deleted file mode 100755 index ef43681ed..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/RSESamplesPlugin.html +++ /dev/null @@ -1,141 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>RSESamplesPlugin Class</title>
-</head>
-
-<body>
-<h1>RSESamplesPlugin Class</h1>
-<pre><samp>
-package samples;
-
-import java.util.MissingResourceException;
-import java.util.ResourceBundle;
-
-import org.eclipse.core.resources.IWorkspace;
-import org.eclipse.core.resources.ResourcesPlugin;
-import org.eclipse.core.runtime.Platform;
-import org.eclipse.rse.core.SystemBasePlugin;
-import org.eclipse.rse.services.clientserver.messages.SystemMessage;
-import org.eclipse.rse.services.clientserver.messages.SystemMessageFile;
-import org.osgi.framework.BundleContext;
-
-/**
- * The activator class controls the plug-in life cycle
- */
-public class RSESamplesPlugin extends SystemBasePlugin {
-
- //The shared instance.
- private static RSESamplesPlugin plugin;
-
- //Resource bundle.
- private ResourceBundle resourceBundle = null;
- private static SystemMessageFile messageFile = null;
-
- /**
- * The constructor.
- */
- public RSESamplesPlugin() {
- super();
- }
-
- /**
- * This method is called upon plug-in activation
- */
- public void start(BundleContext context) throws Exception {
- super.start(context);
- <strong>plugin = this;
- messageFile = getMessageFile("rseSamplesMessages.xml");</strong>
- }
-
- /**
- * This method is called when the plug-in is stopped
- */
- public void stop(BundleContext context) throws Exception {
- <strong>plugin = null;
- resourceBundle = null;</strong>
- super.stop(context);
- }
-
- /**
- * Returns the shared instance.
- */
- <strong>public static RSESamplesPlugin getDefault() {
- return plugin;
- }</strong>
-
- /**
- * Returns the workspace instance.
- */
- <strong>public static IWorkspace getWorkspace() {
- return ResourcesPlugin.getWorkspace();
- }</strong>
-
- /**
- * Returns the string from the plugin's resource bundle,
- * or 'key' if not found.
- */
- <strong>public static String getResourceString(String key) {
- ResourceBundle bundle= RSESamplesPlugin.getDefault().getResourceBundle();
- try {
- return (bundle != null) ? bundle.getString(key) : key;
- } catch (MissingResourceException e) {
- return key;
- }
- }</strong>
-
- /**
- * Returns the plugin's resource bundle,
- */
- <strong>public ResourceBundle getResourceBundle() {
- try {
- if (resourceBundle == null)
- resourceBundle = ResourceBundle.getBundle("samples.rseSamplesResources");
- } catch (MissingResourceException x) {
- resourceBundle = null;
- }
- return resourceBundle;
- }</strong>
-
- /**
- * Initialize the image registry by declaring all of the required graphics.
- */
- protected void initializeImageRegistry()
- {
- }
-
- /**
- * Load a message file for this plugin.
- * @param messageFileName - the name of the message xml file. Will look for it in this plugin's install folder.
- * @return a message file object containing the parsed contents of the message file, or null if not found.
- */
- <strong>public SystemMessageFile getMessageFile(String messageFileName)
- {
- return loadMessageFile(getBundle(), messageFileName);
- }</strong>
-
- /**
- * Return our message file
- */
- <strong>public static SystemMessageFile getPluginMessageFile()
- {
- return messageFile;
- }</strong>
-
- /**
- * Retrieve a message from this plugin's message file
- */
- <strong>public static SystemMessage getPluginMessage(String msgId)
- {
- return getMessage(messageFile, msgId);
- }</strong>
-}
-</samp></pre>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/RSESamplesPlugin2.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/RSESamplesPlugin2.html deleted file mode 100755 index f1b2ee08a..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/RSESamplesPlugin2.html +++ /dev/null @@ -1,167 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>RSESamplesPlugin Class</title>
-</head>
-
-<body>
-<h1>RSESamplesPlugin Class</h1>
-<pre><samp>
-package samples;
-
-import java.util.MissingResourceException;
-import java.util.ResourceBundle;
-
-import org.eclipse.core.resources.IWorkspace;
-import org.eclipse.core.resources.ResourcesPlugin;
-import org.eclipse.core.runtime.IAdapterManager;
-import org.eclipse.core.runtime.Platform;
-import org.eclipse.rse.core.SystemBasePlugin;
-import org.eclipse.rse.services.clientserver.messages.SystemMessage;
-import org.eclipse.rse.services.clientserver.messages.SystemMessageFile;
-import org.osgi.framework.BundleContext;
-
-import samples.subsystems.DeveloperSubSystemConfigurationAdapterFactory;
-
-/**
- * The activator class controls the plug-in life cycle
- */
-public class RSESamplesPlugin extends SystemBasePlugin {
-
- //The shared instance.
- private static RSESamplesPlugin plugin;
-
- //Resource bundle.
- private ResourceBundle resourceBundle;
- private static SystemMessageFile messageFile = null;
-
- /**
- * The constructor.
- */
- public RSESamplesPlugin() {
- super();
- plugin = this;
- }
-
- /**
- * This method is called upon plug-in activation
- */
- public void start(BundleContext context) throws Exception {
- super.start(context);
- messageFile = getMessageFile("rseSamplesMessages.xml"); //$NON-NLS-1$
-
- IAdapterManager manager = Platform.getAdapterManager();
- samples.model.DeveloperAdapterFactory factory = new samples.model.DeveloperAdapterFactory();
- manager.registerAdapters(factory, samples.model.TeamResource.class);
- manager.registerAdapters(factory, samples.model.DeveloperResource.class);
-
- DeveloperSubSystemConfigurationAdapterFactory sscaf = new DeveloperSubSystemConfigurationAdapterFactory();
- sscaf.registerWithManager(manager);
-
- }
-
- /**
- * This method is called when the plug-in is stopped
- */
- public void stop(BundleContext context) throws Exception {
- super.stop(context);
- plugin = null;
- resourceBundle = null;
- }
-
- /**
- * Returns the shared instance.
- */
- public static RSESamplesPlugin getDefault() {
- return plugin;
- }
-
- /**
- * Returns the workspace instance.
- */
- public static IWorkspace getWorkspace() {
- return ResourcesPlugin.getWorkspace();
- }
-
- /**
- * Returns the string from the plugin's resource bundle,
- * or 'key' if not found.
- */
- public static String getResourceString(String key) {
- ResourceBundle bundle= RSESamplesPlugin.getDefault().getResourceBundle();
- try {
- return (bundle != null) ? bundle.getString(key) : key;
- } catch (MissingResourceException e) {
- return key;
- }
- }
-
- /**
- * Returns the plugin's resource bundle,
- */
- public ResourceBundle getResourceBundle() {
- try {
- if (resourceBundle == null)
- resourceBundle = ResourceBundle.getBundle("samples.rseSamplesResources");
- } catch (MissingResourceException x) {
- resourceBundle = null;
- }
- return resourceBundle;
- }
-
- /**
- * @see AbstractUIPlugin#initializeDefaultPreferences
- */
- //protected void initializeDefaultPreferences(IPreferenceStore store)
- //{
- // super.initializeDefaultPreferences(store);
- // //RSESamplesPreferencePage.initDefaults(store);
- //}
-
- /**
- * Initialize the image registry by declaring all of the required graphics.
- */
- protected void initializeImageRegistry()
- {
- String path = getIconPath();
- putImageInRegistry("ICON_ID_TEAM", path + "team.gif");
- putImageInRegistry("ICON_ID_DEVELOPER", path + "developer.gif");
- putImageInRegistry("ICON_ID_TEAMFILTER", path + "teamFilter.gif");
- putImageInRegistry("ICON_ID_DEVELOPERFILTER", path + "developerFilter.gif");
- }
-
- /**
- * Load a message file for this plugin.
- * @param messageFileName - the name of the message xml file. Will look for it in this plugin's install folder.
- * @return a message file object containing the parsed contents of the message file, or null if not found.
- */
- public SystemMessageFile getMessageFile(String messageFileName)
- {
- return loadMessageFile(getBundle(), messageFileName);
- }
-
- /**
- * Return our message file
- */
- public static SystemMessageFile getPluginMessageFile()
- {
- return messageFile;
- }
-
- /**
- * Retrieve a message from this plugin's message file
- */
- public static SystemMessage getPluginMessage(String msgId)
- {
- return getMessage(messageFile, msgId);
- }
-}
-</samp></pre>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/ShowJarContents1.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/ShowJarContents1.html deleted file mode 100755 index 90e137bc2..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/ShowJarContents1.html +++ /dev/null @@ -1,43 +0,0 @@ -<!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">
-<LINK REL="STYLESHEET" HREF="../../book.css" TYPE="text/css">
-<title>ShowJarContents Class After Creation</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>ShowJarContents Class After Creation</h1>
-<p>
-<pre><samp>
-package samples.ui.actions;
-
-import org.eclipse.rse.files.ui.actions.SystemAbstractRemoteFilePopupMenuExtensionAction;
-
-public class <b>ShowJarContents</b>
- extends SystemAbstractRemoteFilePopupMenuExtensionAction
-{
-
- /**
- * Constructor for ShowJarContents.
- */
- public <b>ShowJarContents</b>()
- {
- super();
- }
-
- /**
- * @see org.eclipse.rse.ui.actions.SystemAbstractPopupMenuExtensionAction#run()
- */
- public void <b>run</b>()
- {
- }
-
-}
-
-</samp></pre>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/ShowJarContents2.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/ShowJarContents2.html deleted file mode 100755 index 7464bd93e..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/ShowJarContents2.html +++ /dev/null @@ -1,52 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>ShowJarContents Class After Editing</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>ShowJarContents Class After Editing</h1>
-<p>
-<pre><samp>
-package samples.ui.actions;
-
-import org.eclipse.rse.files.ui.actions.SystemAbstractRemoteFilePopupMenuExtensionAction;
-<b>import com.ibm.etools.systems.subsystems.*;</b>
-
-/**
- * <i>An action that runs a command to display the contents of a Jar file.</i>
- * <i>The plugin.xml file restricts this action so it only appears for .jar files.</i>
- */
-public class ShowJarContents
- extends SystemAbstractRemoteFilePopupMenuExtensionAction
-{
-
- /**
- * Constructor for ShowJarContents.
- */
- public ShowJarContents()
- {
- super();
- }
-
- /**
- * @see org.eclipse.rse.ui.actions.SystemAbstractPopupMenuExtensionAction#run()
- */
- public void run()
- {
- <b>IRemoteFile selectedFile = getFirstSelectedRemoteFile();</b>
- <b>String cmdToRun = "jar -tvf " + selectedFile.getAbsolutePath();</b>
- <b>runCommand(cmdToRun);</b>
- }
-
-}
-
-</samp></pre>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamFilterDialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamFilterDialog.gif Binary files differdeleted file mode 100755 index 4d2ae4028..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamFilterDialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamFilterWizard.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamFilterWizard.gif Binary files differdeleted file mode 100755 index 1590342e3..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamFilterWizard.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamResource.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamResource.html deleted file mode 100755 index 9fbe890f1..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamResource.html +++ /dev/null @@ -1,83 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>TeamResource Class After Editing</title>
-</head>
-
-<body>
-<h1>TeamResource Class After Editing</h1>
-<pre><samp>
-package samples.model;
-
-import org.eclipse.rse.core.subsystems.AbstractResource;
-import org.eclipse.rse.core.subsystems.ISubSystem;
-
-/**
- * This models a remote resource representing a team defined on a particular system.
- */
-public class TeamResource extends AbstractResource {
-
- private String name;
- private DeveloperResource[] developers;
-
- /**
- * Default constructor
- */
- public TeamResource()
- {
- super();
- }
- /**
- * Constructor for TeamResource when given a parent subsystem.
- */
- public TeamResource(ISubSystem parentSubSystem)
- {
- super(parentSubSystem);
- }
-
- /**
- * Returns the name.
- * @return String
- */
- public String getName()
- {
- return name;
- }
-
- /**
- * Sets the name.
- * @param name The name to set
- */
- public void setName(String name)
- {
- this.name = name;
- }
-
- /**
- * Returns the developers.
- * @return DeveloperResource[]
- */
- public DeveloperResource[] getDevelopers()
- {
- return developers;
- }
-
- /**
- * Sets the developers.
- * @param developers The developers to set
- */
- public void setDevelopers(DeveloperResource[] developers)
- {
- this.developers = developers;
- }
-
-
-}
-</samp></pre>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamResourceAdapter.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamResourceAdapter.html deleted file mode 100755 index c576c6c5c..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamResourceAdapter.html +++ /dev/null @@ -1,228 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>TeamResourceAdapter Class After Editing</title>
-</head>
-
-<body>
-<h1>TeamResourceAdapter Class After Editing</h1>
-<pre><samp>
-package samples.model;
-
-import org.eclipse.jface.resource.ImageDescriptor;
-import org.eclipse.jface.viewers.IStructuredSelection;
-import org.eclipse.rse.ui.SystemMenuManager;
-import org.eclipse.rse.ui.view.AbstractSystemViewAdapter;
-import org.eclipse.rse.ui.view.ISystemRemoteElementAdapter;
-import org.eclipse.swt.widgets.Shell;
-import org.eclipse.ui.views.properties.IPropertyDescriptor;
-
-<strong>import samples.RSESamplesPlugin;</strong>
-<strong>import samples.subsystems.DeveloperSubSystem;</strong>
-
-/**
- * This is the adapter which enables us to work with our remote team resources.
- */
-public class TeamResourceAdapter extends AbstractSystemViewAdapter implements
- ISystemRemoteElementAdapter {
-
- /**
- * Constructor.
- */
- public TeamResourceAdapter() {
- super();
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#addActions(org.eclipse.rse.ui.SystemMenuManager,
- * org.eclipse.jface.viewers.IStructuredSelection, org.eclipse.swt.widgets.Shell, java.lang.String)
- */
- public void addActions(SystemMenuManager menu,
- IStructuredSelection selection, Shell parent, String menuGroup)
- {
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getImageDescriptor(java.lang.Object)
- */
- public ImageDescriptor getImageDescriptor(Object element)
- {
- <strong>return RSESamplesPlugin.getDefault().getImageDescriptor("ICON_ID_TEAM");</strong>
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getText(java.lang.Object)
- */
- public String getText(Object element)
- {
- <strong>return ((TeamResource)element).getName();</strong>
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getAbsoluteName(java.lang.Object)
- */
- <a id="getAbsoluteName"/>public String getAbsoluteName(Object object)
- {
- <strong>TeamResource team = (TeamResource)object;
- return "Team_"+team.getName();</strong>
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getType(java.lang.Object)
- */
- public String getType(Object element)
- {
- <strong>return RSESamplesPlugin.getResourceString("property.team_resource.type");</strong>
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getParent(java.lang.Object)
- */
- public Object getParent(Object element)
- {
- return null; // not really used, which is good because it is ambiguous
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#hasChildren(java.lang.Object)
- */
- public boolean hasChildren(Object element)
- {
- <strong>return true;</strong>
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getChildren(java.lang.Object)
- */
- public Object[] getChildren(Object element)
- {
- <strong>return ((TeamResource)element).getDevelopers();</strong>
- }
-
- /**
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#internalGetPropertyDescriptors()
- */
- protected IPropertyDescriptor[] internalGetPropertyDescriptors()
- {
- return null;
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#internalGetPropertyValue(java.lang.Object)
- */
- protected Object internalGetPropertyValue(Object key)
- {
- return null;
- }
-
- /**
- * Intercept of parent method to indicate these objects can be renamed using the RSE-supplied
- * rename action.
- */
- <a id="canRename"/>public boolean canRename(Object element)
- {
- <strong>return true;</strong>
- }
-
- /**
- * Intercept of parent method to actually do the rename. RSE supplies the rename GUI, but
- * defers the action work of renaming to this adapter method.
- */
- <a id="doRename"/>public boolean doRename(Shell shell, Object element, String newName)
- {
- <strong>((TeamResource)element).setName(newName);
- return true;</strong>
- }
- // --------------------------------------
- // ISystemRemoteElementAdapter methods...
- // --------------------------------------
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getAbsoluteParentName(java.lang.Object)
- */
- public String getAbsoluteParentName(Object element)
- {
- <strong>return "root";</strong> // not really applicable as we have no unique hierarchy
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getSubSystemConfigurationId(java.lang.Object)
- */
- public String getSubSystemConfigurationId(Object element)
- {
- <strong>return "samples.subsystems.factory";</strong> // as declared in extension in plugin.xml
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteTypeCategory(java.lang.Object)
- */
- public String getRemoteTypeCategory(Object element)
- {
- <strong>return "developers";</strong> // Course grained. Same for all our remote resources.
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteType(java.lang.Object)
- */
- public String getRemoteType(Object element)
- {
- <strong>return "team";</strong> // Fine grained. Unique to this resource type.
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteSubType(java.lang.Object)
- */
- public String getRemoteSubType(Object element)
- {
- return null; // Very fine grained. We don't use it.
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#refreshRemoteObject(java.lang.Object, java.lang.Object)
- */
- <a id="refreshRemoteObject"/>public boolean refreshRemoteObject(Object oldElement, Object newElement)
- {
- <strong>TeamResource oldTeam = (TeamResource)oldElement;
- TeamResource newTeam = (TeamResource)newElement;
- newTeam.setName(oldTeam.getName());
- return false;</strong> // If developer objects held references to their team names, we'd have to return true
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteParent(org.eclipse.swt.widgets.Shell, java.lang.Object)
- */
- public Object getRemoteParent(Shell shell, Object element) throws Exception
- {
- return null; // maybe this would be a Project or Roster object, or leave as null if this is the root
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteParentNamesInUse(org.eclipse.swt.widgets.Shell, java.lang.Object)
- */
- <a id="getNames"/>public String[] getRemoteParentNamesInUse(Shell shell, Object element)
- throws Exception
- {
- <strong>DeveloperSubSystem ourSS = (DeveloperSubSystem)getSubSystem(element);
- TeamResource[] allTeams = ourSS.getAllTeams();
- String[] allNames = new String[allTeams.length];
- for (int idx = 0; idx < allTeams.length; idx++)
- allNames[idx] = allTeams[idx].getName();
- return allNames;</strong> // Return list of all team names
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#supportsUserDefinedActions(java.lang.Object)
- */
- public boolean supportsUserDefinedActions(Object object) {
- <strong>return false;</strong>
- }
-
-}
-</samp></pre>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/index.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/index.html deleted file mode 100755 index c6cd77505..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/index.html +++ /dev/null @@ -1 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<meta name="generator" content="Adobe GoLive">
<title>RSE Tutorials</title>
</head>
<body>
<p>Note: This page exists only to provide a root page for debugging the
tutorial and should not
be accessible from any page or the table of contents.</p>
<p><a href="pdeProject.html">Getting Started</a></p>
<p><a href="propertypage.html">Property Page Tutorial</a></p>
<p><a href="subsystem.html">Subsystem Tutorial</a></p>
<p><a href="popup.html">Popup Menu Tutorial</a></p>
</body>
</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/newFilterAction.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/newFilterAction.gif Binary files differdeleted file mode 100755 index 0883a8979..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/newFilterAction.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_1.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_1.gif Binary files differdeleted file mode 100755 index 717f78de8..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_1.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props1.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props1.gif Binary files differdeleted file mode 100755 index 21548f3db..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props1.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props2.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props2.gif Binary files differdeleted file mode 100755 index 1d3b9ace0..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props2.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props2_addvar1.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props2_addvar1.gif Binary files differdeleted file mode 100755 index 0f2464574..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props2_addvar1.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props2_addvar2.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props2_addvar2.gif Binary files differdeleted file mode 100755 index a417d2b85..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props2_addvar2.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props3.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props3.gif Binary files differdeleted file mode 100755 index 3f985d848..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props3.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props3_addvar1.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props3_addvar1.gif Binary files differdeleted file mode 100755 index add8e33a8..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props3_addvar1.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props3_addvar2.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props3_addvar2.gif Binary files differdeleted file mode 100755 index 6ab3d1209..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props3_addvar2.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props4.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props4.gif Binary files differdeleted file mode 100755 index 78683a717..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props4.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar1.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar1.gif Binary files differdeleted file mode 100755 index 0106bbd81..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar1.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar1_selectFolder.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar1_selectFolder.gif Binary files differdeleted file mode 100755 index bf4d7431f..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar1_selectFolder.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar2.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar2.gif Binary files differdeleted file mode 100755 index bad6554da..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar2.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar3.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar3.gif Binary files differdeleted file mode 100755 index 134eccad8..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar3.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar4.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar4.gif Binary files differdeleted file mode 100755 index 493a7c8dd..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar4.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar5.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar5.gif Binary files differdeleted file mode 100755 index 8ec5cb2ff..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_addvar5.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_newVar_msg.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_newVar_msg.gif Binary files differdeleted file mode 100755 index 8ec5cb2ff..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_props_newVar_msg.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_after.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_after.gif Binary files differdeleted file mode 100755 index 53fa300b6..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_after.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_page1.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_page1.gif Binary files differdeleted file mode 100755 index e4fdfff8d..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_page1.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_page3.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_page3.gif Binary files differdeleted file mode 100755 index 5c42bae1b..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_page3.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_page4.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_page4.gif Binary files differdeleted file mode 100755 index 8bbc87bd9..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProj_wiz_page4.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProject.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProject.html deleted file mode 100755 index fd07da1a7..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/pdeProject.html +++ /dev/null @@ -1,64 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>Creating a Plug-in Project</title>
-</head>
-
- <body bgcolor="#ffffff">
- <h1>Creating a Plug-in Project</h1>
- <p>To use any Eclipse extension point, including those defined by the Remote System Explorer, you must first create a plug-in project using the plug-in development environment (PDE), which you will do shortly. At its simplest, a plug-in project requires a <tt>MANIFEST.MF</tt> file describing the plugin and its dependencies and, if extending the workbench a <samp>plugin.xml</samp> file identifying the extension points being implemented, and a set of Java classes implementing those extension points. There is usually also a plug-in class file that is used as the overall manager of the project, and point of integration that other classes can rely on.</p>
- <p><i>If you already have a plugin project, you will need to update it slightly to make it extend SystemBasePlugin and add the few methods it requires. You may wish to examine these steps to see what methods to add. The Eclipse environment will keep your classpaths and plugin dependecies in sync for you.</i></p>
- <p>Eclipse supplies a number of plug-in project templates, which generate a number of project files that illustrate examples of various Eclipse extension points. While you are free to pick one of these, or indeed start with any existing plug-in project if you have one, in the RSE tutorials everything is created by hand so as to keep focused on the RSE-required classes and files.</p>
- <p>The following tutorial uses numbered steps to indicate where you are required to do something as you follow along.</p>
- <h2>Step By Step: Creating an RSE Plug-in Project</h2>
- <ol>
- <li>Select <b>File->New->Project.</b>
- <li>On the left of the dialog box, select <b>Plug-in Development</b> category, and on the right, select the <b><a href="pdeProj_1.gif">Plug-in Project</a></b> wizard. Press <b>Next ></b>.
- <li>In the <a href="pdeProj_wiz_page1.gif">first page</a> of the wizard (Plug-in Project Name), enter <b>"RSESamples"</b> for the project name (without the quotes). Press <b>Next ></b>.
- <li>In the second page of the wizard (Plug-in Project Structure), just take the defaults, and press <b>Next ></b>.
- <li>In the <a href="pdeProj_wiz_page3.gif">third page</a> of the wizard (Plug-in Code Generators), select <b>"Default Plug-in Structure"</b>, and press <b>Next ></b>.
- <li>In the <a href="pdeProj_wiz_page4.gif">fourth page</a> of the wizard (Simple Plug-in Content), enter your company for the <b>Provider Name</b>, and press <b>Finish</b>.
- <li>Your new plugin project is created and visible in the Package Explorer of the Plug-in Development perspective. Your new <samp>plugin.xml</samp> file is also open in the <a href="pdeProj_wiz_after.gif">plug-in editor</a>. <i>Close this editor</i>, as you will not be using it in this tutorial.
-
- <li>Select the <samp>plugin.xml</samp> file, right click and select <b>Open</b>. Go to the dependencies tab and add the following plugins to the list:
- <ul>
- <li>org.eclipse.rse.ui
- <li>org.eclipse.rse.services
- <li>org.eclipse.rse.files.ui
- <li>org.eclipse.rse.shells.ui
- <li>org.rse.eclipse.subsystems.files.core
- <li>org.rse.subsystems.shells.core
- </ul>
- <li>Expand the <b>src</b> folder, then the <b>RSESamples</b> package folder, and double-click on <samp><b>RSESamplesPlugin.java</b></samp> to edit this class to make it look like <a href="RSESamplesPlugin.html">this</a>.
-
- <li>Create the project's resources file for translatable strings: right-click on the <b>RSESamples</b> project and select <b>New->File</b> to open the <b>New File</b> wizard. Enter <samp><b>rseSamplesResources.properties</b></samp> for the file name, as was specified in the call to <samp>loadResourceBundle</samp> in the plug-in class's constructor. Press <b>Finish</b> to create the file. You will populate as you go through the tutorials, so for now just <i>close</i> the editor opened for the file.
-
- <li>Create the project's RSE-style messages file for translatable messages: right-click on the <b>RSESamples</b> project and select <b>New->File</b> to get the <b>New File</b> wizard. Enter <samp><b>rseSamplesMessages.xml</b></samp> for the file name, as was specified in the call to <samp>loadMessageFile</samp> in the plug-in class's constructor. Press <b>Finish</b> to create the file. You will see the XML editor open for the new file. Press the <b>Source</b> tab at the bottom of the editor, and enter the following lines (so that you can add messages to the file later on):
- <pre><code>
-<?xml version="1.0" encoding='UTF-8'?>
-<!DOCTYPE MessageFile SYSTEM "../org.eclipse.rse.ui/messageFile.dtd">
-<!-- This is a message file used by SystemMessage and SystemMessageDialog -->
-<<b>MessageFile</b> Version="1.0">
- <<b>Component</b> Name="RSE Samples" Abbr="RSS">
- <<b>Subcomponent</b> Name="General" Abbr="G">
- <<b>MessageList</b>>
- <<b>Message</b> ID="1001" Indicator="E">
- <<b>LevelOne</b>>Sample message</<b>LevelOne</b>>
- <<b>LevelTwo</b>>This is a sample with one substution variable: %1</<b>LevelTwo</b>>
- </<b>Message</b>>
- </<b>MessageList</b>>
- </<b>Subcomponent</b>>
- </<b>Component</b>>
-</<b>MessageFile</b>>
-</code></pre>
- Save and close the file.
- <li>That's it! Your plugin is created and you are ready to go. Now you only need to add code, to implement the extension points.
- </ol>
- </body>
-
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup.html deleted file mode 100755 index 68e1b8275..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup.html +++ /dev/null @@ -1,88 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>Creating a Remote Resource Popup Menu Action</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>Creating a Remote Resource pop-up Menu Action</h1>
-<p>In this tutorial, you will use the RSE <A href="../plugin/popup.html">pop-up menus
-extension point</A> to
-create a pop-up menu action that will appear
-in the context menu for any <samp>.jar</samp> file, for any connection to
-any system type. The action will be labeled "Show contents" and will simply
-run the <samp>jar -tvf</samp> JDK command when selected, displaying the results
-in the command console. You could expand this example to copy the file
-to a local temporary folder, extract the list of file names within the jar, and
-display those names in an Eclipse table view.
-</p>
-
-<p><b>Tip:</b> If you prefer your Java code to use lined-up braces, select the
-first two options in the <b><A href="preferences_JavaFormatting.gif">Code
-Formatter</A></b> preferences page for <b>Java</b>, via <b>Windows->Preferences</b>.
-
-This will affect code generated by wizards. The source code shown assumes this option has been set, but this is not required.
-
-<h2>Step-by-Step: Creating an RSE Remote Resource Pop-up Menu Action</h2>
-
-<ol>
-<li>If you have not already, first <a href="pdeProject.html">create or prepare a plugin project</a>.
-</li>
-<li>Open the <b>plugin.xml</b> file for editing by right-clicking on it and selecting
-<b>Open With->Text Editor</b>. Before the ending </plugin> statement, add the following lines:
-<pre><code>
- <!-- ======================================= -->
- <!-- Remote Object Popup Menu Actions -->
- <!-- ======================================= -->
- <extension point="org.eclipse.rse.ui.popupMenus">
- <objectContribution id="actions.jar"
- typecategoryfilter="files"
- typefilter="file"
- namefilter="*.jar">
- <action id="actions.jar.show"
- enablesFor="1"
- label="Show contents"
- tooltip="List contents of this file"
- class="samples.ui.actions.ShowJarContents">
- </action>
- </objectContribution>
- </extension>
-</code></pre>
-Save and close the file.
-</li>
-<li>
-Create the Java package: right-click on the <B>src</B> source folder and select <B>New->Package</B> to open the <B>New
- Java Package</B> wizard. Enter <B>"samples.ui.actions"</B> for the name of the package and press <B>Finish</B>.</li>
-<li>
-Create the Java class: right-click on the new <B>"samples.ui.actions"</B> package folder and select <B>New->Class</B> to open the <B>New
-Java Class</B> wizard. Enter <B>"ShowJarContents"</B> for the <b>Name</b>
-and <b>"org.eclipse.rse.files.ui.actions.SystemAbstractRemoteFilePopupMenuExtensionAction"</b>
-for the <b>Superclass</b>. Select the <b>Constructors from superclass</b> check box, as shown
-<A href="popup_newClass.gif">here</A>.
-Press <b>Finish</b> to create the <samp><a href="ShowJarContents1.html">ShowJarContents</a></samp> class.
-</li>
-<li>Edit the generated <samp>ShowJarContents.java</samp> file as follows:
-<ol>
- <li type="i">Add import statement for <samp><b>import com.ibm.etools.systems.subsystems.*;</b></samp></li>
- <li type="i">Add the following three statements to the body of the <samp>run()</samp> method:</li>
- <pre><code>
- IRemoteFile selectedFile = getFirstSelectedRemoteFile();
- String cmdToRun = "jar -tvf " + selectedFile.getAbsolutePath();
- runCommand(cmdToRun);
- </code></pre>
-</ol>
-The final result after editing is shown <a href="ShowJarContents2.html">here</a>.
-</li>
-</ol>
-
-<p>Thats it! Now, you can try your new action. Use <b>Run->Run As->Run-time Workbench</b>. Drill
-down in the RSE to a Jar file in a local or remote connection and right-click to <a href="popup_see.gif">see</a> and <a href="popup_run.gif">run</a> your new action. Notice
-how it does not appear for files that do not end with the ".jar" extension. This is because of the "namefilter" attribute
-in our extension point .xml file.
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup_newClass.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup_newClass.gif Binary files differdeleted file mode 100755 index 1e097dc6b..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup_newClass.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup_run.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup_run.gif Binary files differdeleted file mode 100755 index e6646d36a..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup_run.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup_see.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup_see.gif Binary files differdeleted file mode 100755 index 5a1734fe8..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/popup_see.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/preferences_JavaFormatting.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/preferences_JavaFormatting.gif Binary files differdeleted file mode 100755 index 80b15a21d..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/preferences_JavaFormatting.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage.html deleted file mode 100755 index 22aeaa128..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage.html +++ /dev/null @@ -1,84 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>Creating a Remote Resource Property Page</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>Creating a Remote Resource Property Page</h1>
-<p>In this tutorial, you will use the RSE <A href="../plugin/propertypage.html">propertyPage
-extension point</A> to
-create a <a href="propertypage_run_done.gif">property page</a> that will appear
-in the Properties dialog for any folder, for any connection to
-any system type. The page will be labeled "Folder Contents" and will show the
-cumulative size of the contents of the folder, and the number of folders and files within it.
-This will show the extension point, plus how to use some of the RSE user interface helpers, as well
-as the remote file API for querying information about remote folders and files.
-</p>
-
-<p><b>Tip:</b> If you prefer your Java code to use lined-up braces, select the
-first two options in the <b><A href="preferences_JavaFormatting.gif">Code
-Formatter</A></b> preferences page for <b>Java</b>, via <b>Windows->Preferences</b>.
-
-This will affect code generated by wizards. The source code shown assumes this option has been set, but this is not required.
-
-
-
-
-<h2>Step-by-Step: Creating a Remote Resource Property Page</h2>
-<ol>
-<li>If you have not already, first <a href="pdeProject.html">create or prepare a plugin project</a>.
-
-Open the <b>plugin.xml</b> file for editing by right-clicking on it, and selecting
-<b>Open With->Text Editor</b>. Before the ending </plugin> statement, add the following lines:
-<pre><code>
- <!-- ======================================= -->
- <!-- Remote Object Property Pages -->
- <!-- ======================================= -->
- <extension point="org.eclipse.rse.ui.propertyPages">
- <page name="Folder Contents"
- class="samples.ui.propertypages.FolderInfoPropertyPage"
- id="samples.ui.PropertyPage1"
- typefilter="folder"
- typecategoryfilter="files">
- </page>
- </extension>
-
-</code></pre></li>
-<li>Save and close the file.</li>
-<li>
-Create the Java package: right-click on the <B>src</B> source folder and select <B>New->Package</B> to get the <B>New
- Java Package</B> wizard. Enter <B>"samples.ui.propertypages"</B> for the name of the package and press <B>Finish</B>.</li>
-<li>
-Create the Java class: right-click on the new <B>"samples.ui.propertypages"</B> package folder and select <B>New->Class</B> to open the <B>New
-Java Class</B> wizard. Enter <B>"FolderInfoPropertyPage"</B> for the <b>Name</b>
-and <b>"org.eclipse.rse.files.ui.propertypages.SystemAbstractRemoteFilePropertyPageExtensionAction"</b>
-for the <b>Superclass</b>. Select the <b>Constructors from superclass</b> check box, as shown
-<A href="propertypage_newClass.gif">here</A>.
-Press <b>Finish</b> to create the <samp><a href="FolderInfoPropertyPage1.html">FolderInfoPropertyPage</a></samp> class.
-</li>
-<li>Edit the <samp>FolderInfoPropertyPage</samp> class to look like <A href="FolderInfoPropertyPage2.html">this</A>. There are many changes, so you should use
-the clipboard to copy and paste.
-</li>
-<li>Edit the <samp>rseSamplesMesssage.xml</samp> file to look like <A href="rseSamplesMessages2.html">this</A>, where the changes are highlighted.
-</li>
-<li>Edit the <samp>rseSamplesResources.properties</samp> file to look like <A href="rseSamplesResources2.html">this</A>.
-</li>
-</ol>
-
-<p>Thats it! Now, you can try out your new property page. Use <b>Run->Run As->Run-time Workbench</b>. Drill
-down in the RSE to a folder in a local or remote connection and right-click to <a href="propertypage_see.gif">see</a>
-and <a href="propertypage_run_during.gif">run</a> your new property page. This sample is a unique case, in that this operation could potentially run for a long time, as you are recursively walking all
-the sub-folders and files to accumulate the size and count information. Because of this, we put this work
-in a background thread, and update the GUI as each sub-folder is processed. We also supply a stop button
-to the user and watch for them pressing Cancel or closing the dialog. When the thread ends, the
-result looks like <a href="propertypage_run_done.gif">this</a>.
-<p>Notice how this property page only appears for folders, due to the <b><samp>typefilter="folder"</samp></b> attribute
-in our extension point xml.
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_newClass.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_newClass.gif Binary files differdeleted file mode 100755 index 32531d37c..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_newClass.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_run_done.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_run_done.gif Binary files differdeleted file mode 100755 index 084a08ecf..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_run_done.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_run_during.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_run_during.gif Binary files differdeleted file mode 100755 index b14fcf530..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_run_during.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_see.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_see.gif Binary files differdeleted file mode 100755 index 9f5d4882d..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/propertypage_see.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/renameAction.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/renameAction.gif Binary files differdeleted file mode 100755 index 481259872..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/renameAction.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/renameDialog.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/renameDialog.gif Binary files differdeleted file mode 100755 index c04042cfe..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/renameDialog.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesMessages2.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesMessages2.html deleted file mode 100755 index ea240dd19..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesMessages2.html +++ /dev/null @@ -1,38 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>rseSamplesMessages Message File After Editing</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>rseSamplesMessages Message File After Editing</h1>
-<p>
-<pre><samp>
-<?xml version="1.0" encoding='UTF-8'?>
-<!DOCTYPE MessageFile SYSTEM "../org.eclipse.rse.ui/messageFile.dtd">
-<!-- This is a message file used by SystemMessage and SystemMessageDialog -->
-<MessageFile Version="1.0">
- <Component Name="RSE Samples" Abbr="RSS">
- <Subcomponent Name="General" Abbr="G">
- <MessageList>
- <Message ID="1001" Indicator="E">
- <LevelOne>Sample message</LevelOne>
- <LevelTwo>This is a sample with one substution variable: %1</LevelTwo>
- </Message>
- <b><Message ID="1002" Indicator="I"></b>
- <b><LevelOne>Processing...</LevelOne></b>
- <b><LevelTwo></LevelTwo></b>
- <b></Message></b>
- </MessageList>
- </Subcomponent>
- </Component>
-</MessageFile>
-</samp></pre>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesResources2.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesResources2.html deleted file mode 100755 index dae089a03..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesResources2.html +++ /dev/null @@ -1,27 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>rseSamplesResources Properties File After Editing</title>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>rseSamplesResources Properties File After Editing</h1>
-<p>
-<pre><samp>
-pp.size.label=Size
-pp.size.tooltip=Cumulative size, in bytes
-pp.files.label=Files
-pp.files.tooltip=Cumulative number of files
-pp.folders.label=Folders
-pp.folders.tooltip=Cumulative number of folders
-pp.stopButton.label=Stop
-pp.stopButton.tooltip=Cancel the thread
-</samp></pre>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesResources3.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesResources3.html deleted file mode 100755 index 93b3df7cb..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesResources3.html +++ /dev/null @@ -1,27 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>rseSamplesResources Properties File After Editing</title>
-</head>
-
-<body>
-<h1>rseSamplesResources Properties File After Editing</h1>
-<pre><samp>
-pp.size.label=Size
-pp.size.tooltip=Cumulative size, in bytes
-pp.files.label=Files
-pp.files.tooltip=Cumulative number of files
-pp.folders.label=Folders
-pp.folders.tooltip=Cumulative number of folders
-pp.stopButton.label=Stop
-pp.stopButton.tooltip=Cancel the thread
-
-<b>property.type.teamfilter=Team filter</b>
-</samp></pre>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesResources4.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesResources4.html deleted file mode 100755 index 6b91d8a1e..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/rseSamplesResources4.html +++ /dev/null @@ -1,41 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>rseSamplesResources Properties File After Editing</title>
-</head>
-
-<body>
-<h1>rseSamplesResources Properties File After Editing</h1>
-<pre><samp>
-pp.size.label=Size
-pp.size.tooltip=Cumulative size, in bytes
-pp.files.label=Files
-pp.files.tooltip=Cumulative number of files
-pp.folders.label=Folders
-pp.folders.tooltip=Cumulative number of folders
-pp.stopButton.label=Stop
-pp.stopButton.tooltip=Cancel the thread
-
-property.type.teamfilter=Team filter
-<b>property.type.devrfilter=Developer filter
-
-filter.team.dlgtitle=Change Team Filter
-filter.team.pagetitle=Team Filter
-filter.team.pagetext=Create a new filter to list teams
-
-filter.devr.dlgtitle=Change Developer Filter
-filter.devr.pagetitle=Developer Filter
-filter.devr.pagetext=Create a new filter to list developers
-filter.devr.teamprompt.label=Parent team
-filter.devr.teamprompt.tooltip=Specify the team within which to list developers
-filter.devr.devrprompt.label=Developers
-filter.devr.devrprompt.tooltip=Specify a simple or generic developer name pattern
-</b>
-</samp></pre>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/runIt1.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/runIt1.gif Binary files differdeleted file mode 100755 index 57af6bf40..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/runIt1.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/runIt2.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/runIt2.gif Binary files differdeleted file mode 100755 index 41b63a448..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/runIt2.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/startup.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/startup.html deleted file mode 100755 index 7e715b6bc..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/startup.html +++ /dev/null @@ -1,25 +0,0 @@ -<!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" HREF="../../book.css" TYPE="text/css">
-<title>Startup Method in RSESamplesPlugin</title>
-</head>
-
-<body>
-<h1>Startup Method in RSESamplesPlugin</h1>
-<pre><samp>
- public void startup() throws CoreException
- {
- super.startup();
- <b>IAdapterManager manager = Platform.getAdapterManager();
- samples.model.DeveloperAdapterFactory factory = new samples.model.DeveloperAdapterFactory();
- manager.registerAdapters(factory, samples.model.TeamResource.class);
- manager.registerAdapters(factory, samples.model.DeveloperResource.class);</b>
- }
-</samp></pre>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/subsystem.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/subsystem.html deleted file mode 100755 index b5f4aaff4..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/subsystem.html +++ /dev/null @@ -1,245 +0,0 @@ -<!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"> -<LINK REL="STYLESHEET" HREF="../../book.css" TYPE="text/css"> -<title>Creating a Subsystem Configuration</title> -</head> - -<body> -<h1>Creating a Subsystem Configuration</h1> -<p>In this tutorial you will use the RSE <A href="../../reference/extension-points/org_eclipse_rse_ui_subsystemConfigurations.html">subsystemConfigurations</A> extension point to show new subsystems within connections, which will then appear when those connections are expanded. Effectively, you will add a new <i>remote-accessing tool</i> to the Remote System Explorer.</p> -<p> -A full-blown tutorial to illustrate this extension point is a bit difficult without inventing -server-side code and a communication layer for that server-side code to communication with the -client-side subsystem. Rather than becoming bogged down in these details, this tutorial will not -write server-side code or a communications-layer, but instead will hard-code the remote resources -on the client-side so as to focus discussion on the client-side code. The extension point assumes -you already have server-side code and a communication layer you now want to exploit within -Eclipse. -</p> - <p>When you are finished you should have a working subsystem similar to the one found in the org.eclipse.rse.examples.tutorial plugin.</p> - <h2>Scenario</h2> - <p>This tutorial pretends that you have server-side code which manages user profiles for developers and teams of developers. We assume there is a master list of developers identified for development access to this server, and there is a grouping mechanism that allows developers to be assigned to named teams. A developer may exist on multiple teams. Each developer can have one or more <i>roles</i> which may affect what they are allowed to access.</p> -<p>In this tutorial you will define a subsystem for working with these resources in the remote system identified by the connection. This will first list teams and then developers within teams. Roles will be accessible via an action.</p> -<p><i>Do not worry about how useful or realistic the example is. The point of the exercise is -show the code necessary to fully enable new subsystems. It is up to the subsystem developer to -decide what resources to expose and what actions on those resources.</i></p> - -<br> -<hr> - - -<h2>Step By Step: Creating a Subsystem Configuration</h2> - <p>If you have not already, first <a href="pdeProject.html">create or prepare a plugin project</a> -We will follow the steps listed in the <A href="../plugin/subsystem.html#steps">Overview of Steps</A> section in the description of the plugin.</p> - <ol> -<li>Create a package named <samp><b>samples.subsystems</b></samp>, by right-clicking on the <samp>src</samp> folder -and using the <b>New->Package</b> wizard. In the new package, create an empty interface named <A href="IDeveloperSubSystem.html"><samp>IDeveloperSubSystem</samp></A>, by right-clicking on the package and selecting <b>New->Interface</b>. -</li> -<li>Also in package <samp>samples.subsystems</samp>, use <b>New->Class</b> to -create a class named <samp><b>DeveloperConnectorService</b></samp> that extends <b>superclass</b> -<samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/AbstractConnectorService.html">AbstractConnectorService</A></samp>, -selecting the option to include <b>Constructors from superclass</b>. Edit the result to add -a <samp>connected</samp> instance variable that is used in the methods, as shown in bold <a href="DeveloperConnectorService.html">here</a>. -</li> -<li>Again in package <samp>samples.subsystems</samp>, use <b>New->Class</b> to -create a class named <samp><b>DeveloperConnectorServiceManager</b></samp> that extends <b>superclass</b> -<samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/AbstractConnectorServiceManager.html">AbstractSystemManager</A></samp>, -selecting the option to include <b>Constructors from superclass</b>. Edit the result to add -a factory method, and flesh out the methods, as highlighted <a href="DeveloperConnectorServiceManager.html">here</a>. -</li> -<li>Create a package named <samp><b>samples.model</b></samp>. Create two classes in it: -<b><samp>TeamResource</samp></b> and <b><samp>DeveloperResource</samp></b>, each of which extend -<A href="../../reference/api/org/eclipse/rse/core/subsystems/AbstractResource.html"><samp>AbstractResource</samp></A>. - <ol> - <li type="i">Edit <samp>DeveloperResource</samp> to add <samp>name</samp>, <samp>id</samp>, and <samp>deptNbr</samp> properties, as shown in bold <a href="DeveloperResource.html">here</a>. You can use the refactoring support in eclipse to generate the getters and setters for these properties.<li type="i">Edit <samp>TeamResource</samp> to add <samp>name</samp> and <samp>developers</samp> (array) properties, - as shown in bold <a href="TeamResource.html">here</a>. - </ol> -<li>You need to think about filter support. For now, you can keep it simple: users can only create filters that list teams, -by specifying a single string that is either a scalar or a generic team name. If scalar, one team will be shown when the filter is expanded. -If generic, all teams matching the generic pattern will be listed. Given the simplicity, you will not need to create a filter string class to perform -parsing. As a result, you have nothing to do for this step.</li> -<li>Return to package <samp>samples.subsystems</samp>, and create class <b><samp>DeveloperSubSystem</samp></b> -that extends <samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/SubSystem.html">SubSystem</A></samp>. -Edit the generated class to add code highlighted <a href="DeveloperSubSystem.html">here</a>.</li> -<li>Again in package <samp>samples.subsystems</samp>, create class <b><samp>DeveloperSubSystemConfiguration</samp></b> -that extends <samp><A href="../../reference/api/org/eclipse/rse/core/subsystems/SubSystemConfiguration.html">SubSystemConfiguration</A></samp>. -Edit the generated class to add code highlighted <a href="DeveloperSubSystemConfiguration.html">here</a>. -</li> -<li>In the project's root folder, find and edit file <samp>rseSamplesResources.properties</samp> and -add the line highlighted <a href="rseSamplesResources3.html">here</a>. -</li> -<li>Update your <samp>plugin.xml</samp> file to include the following lines: -<pre><samp> - <!-- ======================================= --> - <!-- SubSystem Configuration --> - <!-- ======================================= --> - <extension point="org.eclipse.rse.ui.subsystemConfigurations"> - <configuration - id="samples.subsystems.factory" - systemTypes="Linux;Unix;Windows" - name="Teams" - class="samples.subsystems.DeveloperSubSystemConfiguration" - category="users" - vendor="ACME" - > - </configuration> - </extension> -</samp></pre> -<b>Note:</b> You would normal use the <samp>icon</samp> and <samp>iconlive</samp> attributes to specify -a unique icon for your subsystem, but to keep it simple here, just use the default icon. -</li> -</ol> - <p>Now you are far enough along that you can try our what you have, before proceeding. Select -<b>Run->Run As->Run-time workbench</b>. Create a new Linux connection in the RSE, and -expand it. You'll now see your <A href="runIt1.gif">new subsystem</A>, which you can expand -to see its default filter, which in turn you can expand to see your hardcoded list of teams:<br> -<IMG border="0" src="runIt1.gif" width="800" height="514"> -<br> -You will be prompted for a user ID and password, but since the system class does not really -connect, enter anything you like! -<p>Eventually, you will be able to expand a team to see its developers.</p> -<p>Now it is time to work on the appearance and functions of those remote resources. You will do this -by creating adapters for the resources:</p> -<ol start="10"> - <li>Select the <samp>samples.model</samp> package, and: - <ol> - <li type="i">Create a new class named <samp>TeamResourceAdapter</samp> that extends <a href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html"><samp>AbstractSystemViewAdapter</samp></A> and implements - <a href="../../reference/api/org/eclipse/rse/ui/view/ISystemRemoteElementAdapter.html"><samp>ISystemRemoteElementAdapter</samp></A>. - Edit the generated class and add the code highlighted <a href="TeamResourceAdapter.html"><b>here</b></a>. - </li> - <li type="i">Create a new class named <b><samp>DeveloperResourceAdapter</samp></b> - that extends <a href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html"><samp>AbstractSystemViewAdapter</samp></a> and implements - <a href="../../reference/api/org/eclipse/rse/ui/view/ISystemRemoteElementAdapter.html"><samp>ISystemRemoteElementAdapter</samp></A>. - Edit the generated class and add the code highlighted <a href="DeveloperResourceAdapter.html"><b>here</b></a>. - </li> - <li type="i">Next, you need the icons for your remote resources, which you referred to in your adapters. Edit the <samp>RSESamplesPlugin</samp> file and edit the <samp>initializeImageRegistry</samp> - to add the lines of code highlighted <a href="InitializeImageRegistry.html"><b>here</b></a>. Now, you need the icons. Select the <samp>RSESamplesPlugin</samp> project, right-click and select <b>New->Folder</b> and create a folder named <b>icons</b>. Select the new folder, and use <b>File->Import</b> to - import the <samp>team.gif</samp> and <samp>developer.gif</samp> files from the <samp>org.eclipse.rse.examples.tutorial/icons</samp> folder.</li> - </ol> - </li> - <li>Creating the adapters does nothing until you register them with the platform. To do that, you need - an adapter factory class and you need to register it with the platform: - <ol> - <li type="i">Select the <samp>samples.model</samp> package and in it create a class named - <b>DeveloperAdapterFactory</b> that extends <samp><a href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemRemoteAdapterFactory.html">AbstractSystemRemoteAdapterFactory</a></samp> - and implements interface <samp><b>org.eclipse.core.runtime.IAdapterFactory</b></samp>. - Edit the generate class as per the highlighted code <a href="DeveloperAdapterFactory.html"><b>here</b></a>. - </li> - <li type="i">Back in the <samp>RSESamplesPlugin</samp> class, add the highlighted code - <b><a href="startup.html">here</a></b> to your <samp>startup</samp> method. - </li> - </ol> -</li> -</ol> - -<p>Once again, run the workbench to see your new subsystem:<br> -<IMG border="0" src="runIt2.gif" width="886" height="594"><br> -It is looking better now! There are icons and labels, and the team resources are expandable. Try the following things with -your new subsystem resources:</p> -<ul> -<li>Right-click on <samp>Team 1</samp> and select the <a href="renameAction.gif">rename action</A>. The rename action is enabled because you -overwrote <a href="TeamResourceAdapter.html#canRename">canRename</a> in the team resource adapter class. Try renaming it to a name already in use. -The <a href="renameDialog.gif">rename dialog</a> can catch this error because we returned the list of names in use in -the <a href="TeamResourceAdapter.html#getNames">getRemoteParentNamesInUse</a> -method in our team resource adapter class. Rename to a new name. The rename in fact happens because we implemented -the <a href="TeamResourceAdapter.html#doRename">doRename</a> method. -<li>The default filter <samp>All teams</samp> exists because we wrote code to create it in our <a href="DeveloperSubSystemConfiguration.html#createDefaultFilterPool">createDefaultFilterPool</a> method of our subsystem configuration. Try creating a new filter: right-click on <samp>Teams</samp> subsystem and select -<a href="newFilterAction.gif">New->Filter</a> to get the -<a href="NewFilterWizard.gif">New Filter wizard</a>. Enter <samp>*2</samp>, press <b>Next</b>, and -enter <samp>Test filter</samp> for the filter name. Press <b>Finish</b> -to create the filter. Expand it, and you will see that only teams whose name ends with "2" are shown:<br> -<IMG border="0" src="testFilter.gif"> -<br> -Filter support is free in the RSE, -but you do have to write our own code to apply that filter pattern as you see fit. In this case, we did this in our -<a href="DeveloperSubSystem.html#resolveFilterString">internalResolveFilterString</a> method of our subsystem.<li>Notice how a resource like team can display multiple times, by different filters that resolve to it. -Rename <samp>Team 2</samp> shown under the new expanded <samp>Test filter</samp>, and notice how it is successfully -renamed under both filters. This ability to refresh the name in all occurrences of the same resource is made -possible by the adapter methods <a href="TeamResourceAdapter.html#getAbsoluteName">getAbsoluteName</a>, which helps -RSE find redundant copies of the same object, and <a href="TeamResourceAdapter.html#refreshRemoteObject">refreshRemoteObject</a>, -which the RSE calls, on each redundant copy, on a rename operation. -<IMG border="0" src="testRename.gif"></ul> -<p><em>Note:</em> For your reference here is some information on how to further -evolve the functions via your adapter, should you want to:</p> -<ul> -<li>To not show the rename and delete actions at all, or to enable them, -override appropriate methods in the adapter class. For details see the methods -<A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html#showRename(java.lang.Object)">showRename</A>, -<A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html#showDelete(java.lang.Object)">showDelete</A>, -<A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html#doRename(org.eclipse.swt.widgets.Shell, java.lang.Object, java.lang.String)">doRename</A> - and -<A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html#doDelete(org.eclipse.swt.widgets.Shell, java.lang.Object)">doDelete</A> in the parent -<samp><A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html">AbstractSystemViewAdapter</A></samp> class. -<li>To supply your own validator for syntax checking of new names on the rename dialogs, -override <A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html#getNameValidator(java.lang.Object)">getNameValidator</A>. -<li>To add additional actions to the pop-up menus, implement the <A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html#addActions(org.eclipse.rse.ui.SystemMenuManager, org.eclipse.jface.viewers.IStructuredSelection, org.eclipse.swt.widgets.Shell, java.lang.String)">addActions</a> -method in your adapter class. -<li>To support dragging and dropping, override the -<A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html#canDrag(java.lang.Object)">canDrag</a> and -<A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html#canDrop(java.lang.Object)">canDrop</a> parent methods in your adapter class. -<li>To add additional properties to the property sheet, implement the -<A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html#internalGetPropertyDescriptors()">internalGetPropertyDescriptors</a> and -<A href="../../reference/api/org/eclipse/rse/ui/view/AbstractSystemViewAdapter.html#internalGetPropertyValue()">internalGetPropertyValue</a> methods -in your adapter class. -<li>To add property pages to your remote objects (the Properties popup menu item will then appear) use -the RSE <A href="../plugin/propertypage.html">propertyPages</a> extension point. -</ul> -<p>Now you will continue with the tutorial by enhancing the running example to supply its own actions for creating and changing -filters. You will support two types of filters in our subsystems: team filters and developer filters. You have seen team filter already, -but developer filters will be new. They will contain a team name and a developer name-pattern, and when expanded, they will list all the -matching developers in the given team. The filter string syntax for developer filters will be "team-name/developer-generic-name". Because -you have more than one type of filter, our filter wizards will set the type attribute for the filters, so the change action will know -which dialog to present to the user. This will also allow you to have different icons for each filter. -<ol start="11"> - <li>Follow these steps to enable support for our own filter-support: - <ol> - <li type="i">First, create the new GUI pane for your developer filter prompts. Select the <samp>samples.subsystems</samp> - package and in it create a new class named <samp><b>DeveloperFilterStringEditPane</b></samp> that extends the - class <samp><b>SystemFilterStringEditPane</b></samp> in package <samp>org.eclipse.rse.ui.filters</samp>. - Edit the new class, adding the code highlighted <a href="DeveloperFilterStringEditPane.html">here</a>. - </li> - - <li type="i">Edit the <samp>DeveloperSubSystemConfiguration</samp> class, and add the code highlighted - <a href="DeveloperSubSystemConfiguration2.html">here</a>. - </li> - - <li type="i">Next, you need the unique icons for your own filters, which you referred to in your subsystem factory. Edit the <samp>RSESamplesPlugin</samp> file and edit the <samp>initializeImageRegistry</samp> - to add the lines of code highlighted <a href="InitializeImageRegistry2.html">here</a>. Now you need these icons. - Select the folder named <b>icons</b> and use <b>File->Import</b> to - import the <samp>teamFilter.gif</samp> and <samp>developerFilter.gif</samp> files from the - <samp>org.eclipse.rse.examples.tutorial\icons</samp> folder.</li> - - <li type="i">Now you need to edit your subsystem so it will parse the two types of filters you now - have. Edit <samp>DeveloperSubSystem</samp> and edit it as highlighted <a href="DeveloperSubSystem2.html#resolve">here</a>. - </li> - - <li type="i">In the project's root folder, find and edit file <samp>rseSamplesResources.properties</samp> and - add the line highlighted <a href="rseSamplesResources4.html">here</a>. - </li> - - <li type="i">Now you can run again. Right click on the <samp>Teams</samp> subsystem, to see the new actions for - creating filters:<br> - <IMG border="0" src="NewFilterActions.gif"> - <IMG border="0" src="TeamFilterWizard.gif"><br><br> - <IMG border="0" src="DeveloperFilterWizard.gif"><br><br> - - Create a team filter and a developer filter, and notice the new icons:<br> - <IMG border="0" src="NewFilterIcons.gif"><br><br> - - Now right-click on a team filter and select Change, and then do the same for a developer filter:<br> - <IMG border="0" src="TeamFilterDialog.gif"> - <IMG border="0" src="DeveloperFilterDialog.gif"><br> - </li> - - </ol> - </li> -</ol> - - -<br><br><br> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/testFilter.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/testFilter.gif Binary files differdeleted file mode 100755 index 38008bb54..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/testFilter.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/testRename.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/testRename.gif Binary files differdeleted file mode 100755 index 8c1f64b2c..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/testRename.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorials.html b/rse/doc/org.eclipse.rse.doc.isv/guide/tutorials.html deleted file mode 100755 index fe3fb0ce2..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/tutorials.html +++ /dev/null @@ -1,41 +0,0 @@ -<!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 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > -<title>Tutorials</title> -<link rel="stylesheet" type="text/css" HREF="../book.css"> -</head> - -<body bgcolor="#ffffff"> -<h1>Tutorials</h1> -<p>This section walks through the tutorials that demonstrate how to use the RSE <a href="Extensions.html">extension points</a> to -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.subsystemConfigurations</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"> -Target Management download site</a> or directly from the RSE <b>Update Site</b>. In fact, -the simplest way to get the examples is to choose <I>Help > Software Updates > -Find and Install</I> from the Workbench, get the Examples installed, and then choose -<I>File > Import... > Plug-in development > Plug-ins and Fragments</I>. -Choose the <tt>org.eclipse.rse.examples.tutorial</tt> plug-in and import it with -source folders.</p> -<p>In addition to providing the ready-made code, the tutorial also shows you -how to actally create the Eclipse plug-in project (Please bear with us if the -instructions do not 100% match the latest code due to recent refactorings). -The tutorial starts out by showing -you how to <A href="tutorial/pdeProject.html">create an Eclipse plug-in -project</A>, using the Plug-in Development Environment. While any Eclipse plug-in -project will do, there are benefits to using the RSE-supplied <A - href="api/plugin/uiPluginAPI.html">base class</A> for your project, and other RSE-supplied -infrastructure such as<A href="api/messages/uiMessageAPI.html"> messages</A>, and the many other user interface base classes and re-usable <A - href="api/uiAPI.html">user interface classes</A> supplied by -the RSE core plug-in project. The tutorial step for creating a plug-in project sets up your project for using these. -</p> -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/usingAPIs.html b/rse/doc/org.eclipse.rse.doc.isv/guide/usingAPIs.html deleted file mode 100755 index 9fe91adf7..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/usingAPIs.html +++ /dev/null @@ -1,31 +0,0 @@ -<!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">
-<title>Using the Remote System Explorer API</title>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 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">
-</head>
-
-<body bgcolor="#ffffff">
-<h1>Using the Remote Systems Explorer API</h1>
-<p>In addition to all the programming API provided by Eclipse, the Remote System Explorer itself
-comes with numerous classes and interfaces that may be of value to programmers extending the RSE.
-Typically, these are used in conjunction with the <a href="Extensions.html">extension points</a>
-defined by the RSE.
-<p>
-The API set supplied by the RSE can be roughly partitioned into three areas:
-<ol>
-<li><a href="api/uiAPI.html">User interface</a> support, to make it easier to author plug-ins that extend or use the RSE.
-<li><a href="api/resourceAPI.html">Remote resources</a> support, to enable access to remote resources via IBM-supplied subsystems.
-<li><a href="api/modelAPI.html">Model</a> support, to enable traversal of the RSE model, to access connections, subsystem factories, subsystems, filters, and so on.
-</ol>
-</p>
-<p>
-This guide will introduce the capabilities of the API, leaving the programming details to the
-reference section.
-
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/view_RS.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/view_RS.gif Binary files differdeleted file mode 100755 index 8ee06ea76..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/view_RS.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/view_pulldown.gif b/rse/doc/org.eclipse.rse.doc.isv/guide/view_pulldown.gif Binary files differdeleted file mode 100755 index 5b8aa81c0..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/view_pulldown.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/icons/developer.gif b/rse/doc/org.eclipse.rse.doc.isv/icons/developer.gif Binary files differdeleted file mode 100755 index 9dae955d0..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/icons/developer.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/icons/developerFilter.gif b/rse/doc/org.eclipse.rse.doc.isv/icons/developerFilter.gif Binary files differdeleted file mode 100755 index aaf308445..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/icons/developerFilter.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/icons/team.gif b/rse/doc/org.eclipse.rse.doc.isv/icons/team.gif Binary files differdeleted file mode 100755 index 510a75377..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/icons/team.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/icons/teamFilter.gif b/rse/doc/org.eclipse.rse.doc.isv/icons/teamFilter.gif Binary files differdeleted file mode 100755 index a8091af8f..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/icons/teamFilter.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.isv/notices.html b/rse/doc/org.eclipse.rse.doc.isv/notices.html deleted file mode 100755 index 6c70b9c62..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/notices.html +++ /dev/null @@ -1,22 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 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">
- <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
- <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2006.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/options.txt b/rse/doc/org.eclipse.rse.doc.isv/options.txt deleted file mode 100755 index 0b7b26b2e..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/options.txt +++ /dev/null @@ -1,191 +0,0 @@ --quiet --encoding "iso-8859-1" --charset "iso-8859-1" --sourcepath "../org.eclipse.rse.connectorservice.dstore/src -;../org.eclipse.rse.connectorservice.local/src -;../org.eclipse.rse.connectorservice.ssh/src -;../org.eclipse.rse.core/persistence -;../org.eclipse.rse.core/src -;../org.eclipse.rse.dstore.security/src -;../org.eclipse.rse.eclipse.filesystem/src -;../org.eclipse.rse.files.ui/src -;../org.eclipse.rse.logging/src -;../org.eclipse.rse.processes.ui/src -;../org.eclipse.rse.services/src -;../org.eclipse.rse.services/clientserver -;../org.eclipse.rse.services.dstore/src -;../org.eclipse.rse.services.dstore/miners -;../org.eclipse.rse.services.files.ftp/src -;../org.eclipse.rse.services.local/src -;../org.eclipse.rse.services.ssh/src -;../org.eclipse.rse.shells.ui/src -;../org.eclipse.rse.subsystems.files.core/src -;../org.eclipse.rse.subsystems.files.dstore/src -;../org.eclipse.rse.subsystems.files.ftp/src -;../org.eclipse.rse.subsystems.files.local/src -;../org.eclipse.rse.subsystems.files.ssh/src -;../org.eclipse.rse.subsystems.processes.core/src -;../org.eclipse.rse.subsystems.processes.dstore/src -;../org.eclipse.rse.subsystems.processes.local/src -;../org.eclipse.rse.subsystems.shells.core/src -;../org.eclipse.rse.subsystems.shells.dstore/src -;../org.eclipse.rse.subsystems.shells.local/src -;../org.eclipse.rse.subsystems.shells.ssh/src -;../org.eclipse.rse.ui/filters -;../org.eclipse.rse.ui/model -;../org.eclipse.rse.ui/UI -;../org.eclipse.rse.ui/subsystems -;../org.eclipse.rse.ui/systems" --d reference/api --classpath @rt@ -;../org.eclipse.dstore.core/@dot -;../org.eclipse.dstore.core/bin -;../org.eclipse.dstore.extra/@dot -;../org.eclipse.dstore.extra/bin --breakiterator --tag generated:X --tag lastgen:X --tag model:X --tag ordered:X --use --splitIndex --windowtitle "RSE API Specification" --doctitle "RSE API Specification" --header "<b>RSE</b><br>Release 1.0" --bottom "Copyright (c) IBM Corporation and others 2000, 2006. All Rights Reserved." --group "RSE Core Plug-in Packages" "org.eclipse.rse.core;org.eclipse.rse.core.*" --group "RSE UI Plug-in Packages" "org.eclipse.rse.ui;org.eclipse.rse.ui.*" --link http://java.sun.com/j2se/1.5/docs/api --linkoffline ./../../../org.eclipse.platform.doc.isv/reference/api @javadoc.link.location@/platform/reference/api/ --linkoffline ./../../../org.eclipse.dstore.doc.isv/reference/api ../org.eclipse.dstore.doc.isv/reference/api --link http://bundles.osgi.org/javadoc/r4 - -org.eclipse.rse.connectorservice.dstore -org.eclipse.rse.connectorservice.dstore.util -org.eclipse.rse.connectorservice.local -org.eclipse.rse.connectorservice.ssh -org.eclipse.rse.core -org.eclipse.rse.core.comm -org.eclipse.rse.core.filters -org.eclipse.rse.core.model -org.eclipse.rse.core.references -org.eclipse.rse.core.servicesubsystem -org.eclipse.rse.core.subsystems -org.eclipse.rse.core.subsystems.util -org.eclipse.rse.dstore.security -org.eclipse.rse.dstore.security.preference -org.eclipse.rse.dstore.security.util -org.eclipse.rse.dstore.security.widgets -org.eclipse.rse.dstore.security.wizards -org.eclipse.rse.dstore.universal.miners -org.eclipse.rse.dstore.universal.miners.command -org.eclipse.rse.dstore.universal.miners.command.patterns -org.eclipse.rse.dstore.universal.miners.environment -org.eclipse.rse.dstore.universal.miners.filesystem -org.eclipse.rse.dstore.universal.miners.processes -org.eclipse.rse.eclipse.filesystem -org.eclipse.rse.eclipse.filesystem.ui.actions -org.eclipse.rse.files.ui -org.eclipse.rse.files.ui.actions -org.eclipse.rse.files.ui.compare -org.eclipse.rse.files.ui.dialogs -org.eclipse.rse.files.ui.propertypages -org.eclipse.rse.files.ui.resources -org.eclipse.rse.files.ui.search -org.eclipse.rse.files.ui.view -org.eclipse.rse.files.ui.widgets -org.eclipse.rse.files.ui.wizards -org.eclipse.rse.filters -org.eclipse.rse.logging -org.eclipse.rse.logging.performance -org.eclipse.rse.logging.ui -org.eclipse.rse.model -org.eclipse.rse.persistence -org.eclipse.rse.persistence.dom -org.eclipse.rse.processes.ui -org.eclipse.rse.processes.ui.actions -org.eclipse.rse.processes.ui.dialogs -org.eclipse.rse.processes.ui.propertypages -org.eclipse.rse.processes.ui.view -org.eclipse.rse.services -org.eclipse.rse.services.clientserver -org.eclipse.rse.services.clientserver.archiveutils -org.eclipse.rse.services.clientserver.java -org.eclipse.rse.services.clientserver.messages -org.eclipse.rse.services.clientserver.processes -org.eclipse.rse.services.clientserver.processes.handlers -org.eclipse.rse.services.clientserver.search -org.eclipse.rse.services.clientserver.util.tar -org.eclipse.rse.services.dstore -org.eclipse.rse.services.dstore.files -org.eclipse.rse.services.dstore.processes -org.eclipse.rse.services.dstore.rmtservice -org.eclipse.rse.services.dstore.search -org.eclipse.rse.services.dstore.shells -org.eclipse.rse.services.dstore.util -org.eclipse.rse.services.files -org.eclipse.rse.services.files.ftp -org.eclipse.rse.services.local -org.eclipse.rse.services.local.files -org.eclipse.rse.services.local.processes -org.eclipse.rse.services.local.search -org.eclipse.rse.services.local.shells -org.eclipse.rse.services.processes -org.eclipse.rse.services.search -org.eclipse.rse.services.shells -org.eclipse.rse.services.ssh -org.eclipse.rse.services.ssh.files -org.eclipse.rse.services.ssh.shell -org.eclipse.rse.shells.ui -org.eclipse.rse.shells.ui.actions -org.eclipse.rse.shells.ui.propertypages -org.eclipse.rse.shells.ui.view -org.eclipse.rse.subsystems.files.core -org.eclipse.rse.subsystems.files.core.model -org.eclipse.rse.subsystems.files.core.servicesubsystem -org.eclipse.rse.subsystems.files.core.subsystems -org.eclipse.rse.subsystems.files.core.util -org.eclipse.rse.subsystems.files.dstore -org.eclipse.rse.subsystems.files.dstore.model -org.eclipse.rse.subsystems.files.dstore.old -org.eclipse.rse.subsystems.files.dstore.subsystem -org.eclipse.rse.subsystems.files.ftp -org.eclipse.rse.subsystems.files.ftp.connectorservice -org.eclipse.rse.subsystems.files.ftp.model -org.eclipse.rse.subsystems.files.local -org.eclipse.rse.subsystems.files.local.model -org.eclipse.rse.subsystems.files.ssh -org.eclipse.rse.subsystems.processes.core -org.eclipse.rse.subsystems.processes.core.subsystem -org.eclipse.rse.subsystems.processes.core.subsystem.impl -org.eclipse.rse.subsystems.processes.dstore -org.eclipse.rse.subsystems.processes.local -org.eclipse.rse.subsystems.processes.servicesubsystem -org.eclipse.rse.subsystems.shells.core -org.eclipse.rse.subsystems.shells.core.model -org.eclipse.rse.subsystems.shells.core.subsystems -org.eclipse.rse.subsystems.shells.core.subsystems.servicesubsystem -org.eclipse.rse.subsystems.shells.dstore -org.eclipse.rse.subsystems.shells.dstore.model -org.eclipse.rse.subsystems.shells.local -org.eclipse.rse.subsystems.shells.local.model -org.eclipse.rse.subsystems.shells.ssh -org.eclipse.rse.ui -org.eclipse.rse.ui.actions -org.eclipse.rse.ui.dialogs -org.eclipse.rse.ui.filters -org.eclipse.rse.ui.filters.actions -org.eclipse.rse.ui.filters.dialogs -org.eclipse.rse.ui.messages -org.eclipse.rse.ui.open -org.eclipse.rse.ui.operations -org.eclipse.rse.ui.propertypages -org.eclipse.rse.ui.validators -org.eclipse.rse.ui.view -org.eclipse.rse.ui.view.monitor -org.eclipse.rse.ui.view.scratchpad -org.eclipse.rse.ui.view.search -org.eclipse.rse.ui.view.team -org.eclipse.rse.ui.widgets -org.eclipse.rse.ui.widgets.services -org.eclipse.rse.ui.wizards diff --git a/rse/doc/org.eclipse.rse.doc.isv/plugin.properties b/rse/doc/org.eclipse.rse.doc.isv/plugin.properties deleted file mode 100755 index 31afcd44f..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/plugin.properties +++ /dev/null @@ -1,12 +0,0 @@ -############################################################################### -# Copyright (c) 2000, 2006 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### -pluginName=RSE Developer Guide -providerName=Eclipse.org diff --git a/rse/doc/org.eclipse.rse.doc.isv/plugin.xml b/rse/doc/org.eclipse.rse.doc.isv/plugin.xml deleted file mode 100755 index 4dcbae222..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/plugin.xml +++ /dev/null @@ -1,43 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> - -<!-- ===================================================== --> -<!-- Declare the documentation for the RSE ISV Guide --> -<!-- We will declare only one infoset (book) --> -<!-- ===================================================== --> - -<plugin> - - -<!-- ============================================================================= --> -<!-- Define primary TOC --> -<!-- ============================================================================= --> - - <extension point="org.eclipse.help.toc"> - <toc file="toc.xml" primary="true"/> - <index path="index/"/> - </extension> - -<!-- ============================================================================= --> -<!-- Define TOCs --> -<!-- ============================================================================= --> - - <extension point="org.eclipse.help.toc"> - <toc file="topics_Guide.xml"/> - <toc file="topics_Reference.xml"/> - <toc file="topics_Questions.xml"/> - <toc file="topics_Samples.xml"/> - </extension> - -<!-- ============================================================================= --> -<!-- Define Javadoc locations --> -<!-- ============================================================================= --> - <extension point="org.eclipse.pde.core.javadoc"> - <javadoc path="reference/api"> - <plugin id="org.eclipse.rse.core" /> - <plugin id="org.eclipse.rse.services" /> - <plugin id="org.eclipse.rse.ui" /> - </javadoc> - </extension> - -</plugin> diff --git a/rse/doc/org.eclipse.rse.doc.isv/questions/index.html b/rse/doc/org.eclipse.rse.doc.isv/questions/index.html deleted file mode 100755 index 9596b5129..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/questions/index.html +++ /dev/null @@ -1,39 +0,0 @@ -<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<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 http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="IBM">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>RSE Questions Index</title>
-</head>
-<body>
-<h1>RSE Questions Index</h1>
-<h2> RSE Services Layer</h2>
-<ul>
- <li><a href="../guide/rse_int_services.html">What is available in the RSE Services Layer
- API Packages?</a> </li>
-</ul>
-<h2> RSE Subsystems Layer</h2>
-<ul>
- <li><a href="../guide/rse_int_subsystems.html">What is available in the RSE Subsystems Layer
- API Packages?</a> </li>
-</ul>
-<h2> RSE Files</h2>
-<ul>
- <li><a href="../guide/rse_int_files.html">What is available in the RSE Files packages?</a>
- </li>
-</ul>
-<h2> RSE Shells</h2>
-<ul>
- <li><a href="../guide/rse_int_shells.html">What is available in the RSE Shells packages?</a>
- </li>
-</ul>
-<h2> RSE Processes</h2>
-<ul>
- <li><a href="../guide/rse_int_processes.html">What is available in the RSE Processes packages?</a>
- </li>
-</ul>
-
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/reference/.cvsignore b/rse/doc/org.eclipse.rse.doc.isv/reference/.cvsignore deleted file mode 100644 index 9e5bfb42d..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/reference/.cvsignore +++ /dev/null @@ -1 +0,0 @@ -api
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/reference/extension-points/.cvsignore b/rse/doc/org.eclipse.rse.doc.isv/reference/extension-points/.cvsignore deleted file mode 100644 index 9c59eabff..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/reference/extension-points/.cvsignore +++ /dev/null @@ -1 +0,0 @@ -org_eclipse_*.html 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 deleted file mode 100755 index 4686f958f..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/reference/extension-points/index.html +++ /dev/null @@ -1,31 +0,0 @@ -<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> -<html> -<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 http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -<title>RSE Extension Points</title> -<link rel="stylesheet" type="text/css" HREF="../../book.css"> -</head> -<body> -<h1>RSE Extension Points</h1> -<p>The following extension points can be used to extend the capabilities of the - RSE infrastructure: </p> -<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> - <li><a href="org_eclipse_rse_ui_newConnectionWizardDelegates.html">org.eclipse.rse.ui.newConnectionWizardDelegates</a></li> - <li><a href="org_eclipse_rse_ui_persistenceProviders.html">org.eclipse.rse.ui.persistenceProviders</a></li> - <li><a href="org_eclipse_rse_ui_popupMenus.html">org.eclipse.rse.ui.popupMenus</a></li> - <li><a href="org_eclipse_rse_ui_propertyPages.html">org.eclipse.rse.ui.propertyPages</a></li> - <li><a href="org_eclipse_rse_ui_remoteSystemsViewPreferencesActions.html">org.eclipse.rse.ui.remoteSystemsViewPreferencesActions</a></li> - <li><a href="org_eclipse_rse_ui_subsystemConfigurations.html">org.eclipse.rse.ui.subsystemConfigurations</a></li> -</ul> - -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/reference/misc/index.html b/rse/doc/org.eclipse.rse.doc.isv/reference/misc/index.html deleted file mode 100755 index 23f76241b..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/reference/misc/index.html +++ /dev/null @@ -1,20 +0,0 @@ -<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<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 http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="IBM">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Other Reference Information</title>
-</head>
-<body>
-<h1>Other Reference Information</h1>
-<p>The following specifications, white papers, and design notes describe various
- aspects of the remote development tooling. </p>
-<ul>
- <li><a href="overview-rse.html">Map of Eclipse Remote System Explorer Plug-ins</a>
- </li>
-</ul>
-
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/reference/misc/overview-rse.html b/rse/doc/org.eclipse.rse.doc.isv/reference/misc/overview-rse.html deleted file mode 100755 index 1cfe3cf77..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/reference/misc/overview-rse.html +++ /dev/null @@ -1,40 +0,0 @@ -<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html>
-<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 http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="IBM">
-<title>RSE Overview - Map of RSE Plug-ins</title>
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1>RSE Overview - Map of RSE Plug-ins</h1>
-<p>The Remote System Explorer provides a comprehensive environment for managing remote resources and processes </p>
-<p>The Remote System Explorer tooling itself is divided up into a number of separate
- plug-ins. The following table shows which API packages are found in which plug-ins as of
-Eclipse 3.0. This table is useful
- for determining which plug-ins a given plug-in should include as prerequisites.
-</p>
-<table border="1" width="80%" align="center">
- <tbody>
- <tr>
- <td><b>API Package</b></td>
- <td><b>Required plug-in id</b></td>
- </tr>
- <tr>
- <td><tt>org.eclipse.rse.core[.*]</tt></td>
- <td><tt>org.eclipse.rse.core</tt></td>
- </tr>
- <tr>
- <td><tt>org.eclipse.rse.ui[.*]</tt></td>
- <td><tt>org.eclipse.rse.ui</tt></td>
- </tr>
- <tr>
- <td><tt>junit.*</tt></td>
- <td><tt>org.junit</tt></td>
- </tr>
- </tbody>
-</table>
-
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.isv/reference/misc/runtime-options.html b/rse/doc/org.eclipse.rse.doc.isv/reference/misc/runtime-options.html deleted file mode 100644 index 5c9baaa54..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/reference/misc/runtime-options.html +++ /dev/null @@ -1,42 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> -<html> - -<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="Author" content="IBM"> -<meta http-equiv="Content-Language" content="en-us"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> -<title>Remote System Explorer runtime options</title> -</head> - -<body> - -<h1>Remote System Explorer runtime options</h1> -<p>Version 1.0 - Last revised September 20, 2006</p> -<p>The Remote System Explorer (RSE) is configurable through System properties. Many of these -properties can be used to specify initial RSE settings.</p> - -<h2>System properties</h2> -<p>The following System properties are used by RSE.</p> -<p>Properties can be set in the following ways:</p> -<ul> - <li>use -DpropName=propValue as a VM argument to the Java VM</li> - <li>set the desired property in the config.ini file in the appropriate configuration - area</li> -</ul> -<dl> - <dt><a name="showNewConnectionPrompt" id="showNewConnectionPrompt"></a>rse.showNewConnectionPrompt</dt> - <dd>whether to show the New Connection prompt in RSE views by default. "True" or "false".</dd> - - <dt><a name="showLocalConnection" id="showLocalConnection"></a>rse.showLocalConnection</dt> - <dd>whether to create and show a Local connection by default when RSE starts with a new worspace. "True" or "false".</dd> - - <dt><a name="enableSystemTypes" id="enableSystemTypes"></a>rse.enableSystemTypes</dt> - <dd>a comma-separated list of system types to enable by default. This property can be used to limit the system types in RSE.</dd> - - <dt><a name="showProfilePage" id="showProfilePage"></a>rse.showProfilePage</dt> - <dd>whether to show a New Profile wizard by default when creating a new connection for the first time. "True" or "false". If this is "false", a new profile with the hostname is created without asking the user.</dd> -</dl> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.isv/samples/samples.html b/rse/doc/org.eclipse.rse.doc.isv/samples/samples.html deleted file mode 100644 index 52193a151..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/samples/samples.html +++ /dev/null @@ -1,15 +0,0 @@ -<!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>Installing The Examples</title> -</head> - -<body> -<h1>Installing The Examples -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/schema.css b/rse/doc/org.eclipse.rse.doc.isv/schema.css deleted file mode 100755 index 4efbf2672..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/schema.css +++ /dev/null @@ -1,66 +0,0 @@ -H6.CaptionFigColumn#header {
- font-size:16px;
- display:inline
-}
-
-P.Note#copyright {
- font-size: smaller;
- font-style: normal;
- color: #336699;
- display:inline;
- margin-top: 3.000000pt;
- margin-bottom: 11.000000pt;
- margin-right: 0.000000pt;
- margin-left: 0.000000pt;
-}
-
-P.Code#dtd {
- color: #800000;
- margin-top: 0.000000pt;
- margin-bottom: 0.000000pt;
- margin-right: 0.000000pt;
- margin-left: 10.000000pt;
-}
-
-P.Code#dtdAttlist {
- color: #800000;
- margin-top: 0.000000pt;
- margin-bottom: 0.000000pt;
- margin-right: 0.000000pt;
- margin-left: 20.000000pt;
-}
-
-P.Code#tag {
- color: #000080;
- display:inline;
- margin-top: 0.000000pt;
- margin-bottom: 0.000000pt;
- margin-right: 0.000000pt;
- margin-left: 0.000000pt;
-}
-
-P.Code#cstring {
- color: #008000;
- display:inline;
- margin-top: 0.000000pt;
- margin-bottom: 0.000000pt;
- margin-right: 0.000000pt;
- margin-left: 0.000000pt;
-}
-
-.ConfigMarkup#elementDesc {
- color: black;
- margin-top: 0.000000pt;
- margin-bottom: 0.000000pt;
- margin-right: 0.000000pt;
- margin-left: 10.000000pt;
-}
-
-.ConfigMarkup#attlistDesc {
- color: black;
- margin-top: 0.000000pt;
- margin-bottom: 0.000000pt;
- margin-right: 0.000000pt;
- margin-left: 32.000000pt;
-}
-
diff --git a/rse/doc/org.eclipse.rse.doc.isv/toc.xml b/rse/doc/org.eclipse.rse.doc.isv/toc.xml deleted file mode 100755 index e48700d5c..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/toc.xml +++ /dev/null @@ -1,21 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define the top level topics -->
-<!-- ============================================================================= -->
-
-<toc label="RSE Developer Guide">
- <topic label="Guide" href="guide/rse_int.html">
- <link toc="topics_Guide.xml" />
- <anchor id="guide_additions"/>
- </topic>
- <topic label="Reference">
- <link toc="topics_Reference.xml" />
- <anchor id="reference_additions"/>
- </topic>
- <topic label="Questions Index" href="questions/index.html">
- <link toc="topics_Questions.xml" />
- <anchor id="questions_additions"/>
- </topic>
- <topic label="Legal" href="notices.html"/>
-</toc>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/topics_Guide.xml b/rse/doc/org.eclipse.rse.doc.isv/topics_Guide.xml deleted file mode 100755 index c1356f383..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/topics_Guide.xml +++ /dev/null @@ -1,35 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the main guide -->
-<!-- ============================================================================= -->
-<toc label="Guide">
- <topic label="RSE Architecture" href="guide/rse_int_architecture.html">
- <topic label="Overview" href="guide/rse_int_overview.html"/>
- <topic label="Artifacts" href="guide/Artifacts.html"/>
- <topic label="Model" href="guide/Model.html"/>
- <topic label="Services" href="guide/rse_int_services.html"/>
- <topic label="Subsystems" href="guide/rse_int_subsystems.html"/>
- <topic label="Connector Services" href="guide/rse_int_connectorservices.html"/>
- <topic label="Hosts" href="guide/rse_int_hosts.html"/>
- <topic label="User Interface" href="guide/rse_int_ui.html"/>
- </topic>
- <topic label="Using the RSE API" href="guide/usingAPIs.html">
- <topic label="RSE User Interface API" href="guide/api/uiAPI.html" />
- <topic label="RSE Remote Resource API" href="guide/api/resourceAPI.html" />
- <topic label="RSE Model API" href="guide/api/modelAPI.html" />
- </topic>
- <topic label="Plugging into the RSE" href="guide/plugin.html">
- <topic label="Extensions" href="guide/Extensions.html"/>
- <topic label="Plugging in a Popup Menu" href="guide/plugin/popup.html" />
- <topic label="Plugging in a Property Page" href="guide/plugin/propertypage.html" />
- <topic label="Plugging in a System Type" href="guide/plugin/systemtype.html" />
- <topic label="Plugging in a Subsystem" href="guide/plugin/subsystem.html" />
- <topic label="Relevant Eclipse Extension Points" href="guide/plugin/other.html" />
- </topic>
- <topic label="Tutorials" href="guide/tutorials.html">
- <topic label="Creating a Remote Resource Property Page" href="guide/tutorial/propertypage.html" />
- <topic label="Creating a Subsystem Configuration" href="guide/tutorial/subsystem.html" />
- <topic label="Creating a Remote Resource Popup Menu Action" href="guide/tutorial/popup.html" />
- </topic>
-</toc>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/topics_Questions.xml b/rse/doc/org.eclipse.rse.doc.isv/topics_Questions.xml deleted file mode 100755 index 62fe26b51..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/topics_Questions.xml +++ /dev/null @@ -1,7 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the questions index -->
-<!-- ============================================================================= -->
-<toc label="Questions">
-</toc>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/topics_Reference.xml b/rse/doc/org.eclipse.rse.doc.isv/topics_Reference.xml deleted file mode 100755 index fcb4e4dd3..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/topics_Reference.xml +++ /dev/null @@ -1,190 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- ============================================================================= --> -<!-- Define topics for the references --> -<!-- ============================================================================= --> -<toc label="Reference"> - - <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" /> - <topic label="org.eclipse.rse.ui.newConnectionWizardDelegates" href="reference/extension-points/org_eclipse_rse_ui_newConnectionWizardDelegates.html" /> - <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.remoteSystemsViewPreferencesActions" href="reference/extension-points/org_eclipse_rse_ui_remoteSystemsViewPreferencesActions.html" /> - <topic label="org.eclipse.rse.ui.subsystemConfigurations" href="reference/extension-points/org_eclipse_rse_ui_subsystemConfigurations.html" /> - <anchor id="rse-extension-points-ref" /> - </topic> - - <topic label="Other reference information"> - <topic label="Runtime options" href="reference/misc/runtime-options.html" /> - </topic> - - <topic label="Remote Systems API Reference By Topic"> - <topic label="Core"> - <topic label="org.eclipse.rse.core" href="reference/api/org/eclipse/rse/core/package-summary.html" /> - <topic label="org.eclipse.rse.core.comm" href="reference/api/org/eclipse/rse/core/comm/package-summary.html" /> - <topic label="org.eclipse.rse.core.servicessubsystem" href="reference/api/org/eclipse/rse/core/servicessubsystem/package-summary.html" /> - <topic label="org.eclipse.rse.core.subsystems" href="reference/api/org/eclipse/rse/core/subsystems/package-summary.html" /> - <topic label="org.eclipse.rse.core.subsystems.util" href="reference/api/org/eclipse/rse/core/subsystems/util/package-summary.html" /> - </topic> - <topic label="Logging"> - <topic label="org.eclipse.rse.logging" href="reference/api/org/eclipse/rse/logging/package-summary.html"/> - <topic label="org.eclipse.rse.logging.ui" href="reference/api/org/eclipse/rse/logging/ui/package-summary.html"/> - <topic label="org.eclipse.rse.logging.performance" href="reference/api/org/eclipse/rse/logging/performance/package-summary.html"/> - </topic> - <topic label="Model and Persistence"> - <topic label="org.eclipse.rse.core.model" href="reference/api/org/eclipse/rse/core/model/package-summary.html"/> - <topic label="org.eclipse.rse.model" href="reference/api/org/eclipse/rse/model/package-summary.html"/> - <topic label="org.eclipse.rse.core.filters" href="reference/api/org/eclipse/rse/core/filters/package-summary.html"/> - <topic label="org.eclipse.rse.references" href="reference/api/org/eclipse/rse/references/package-summary.html"/> - <topic label="org.eclipse.rse.persistence" href="reference/api/org/eclipse/rse/persistence/package-summary.html"/> - <topic label="org.eclipse.rse.persistence.dom" href="reference/api/org/eclipse/rse/persistence/dom/package-summary.html"/> - </topic> - <topic label="Common Client and Server Helpers"> - <topic label="org.eclipse.rse.services.clientserver" href="reference/api/org/eclipse/rse/services/clientserver/package-summary.html"/> - <topic label="org.eclipse.rse.services.clientserver.java" href="reference/api/org/eclipse/rse/services/clientserver/java/package-summary.html"/> - <topic label="org.eclipse.rse.services.clientserver.messages" href="reference/api/org/eclipse/rse/services/clientserver/messages/package-summary.html"/> - <topic label="org.eclipse.rse.services.clientserver.processes.handlers" href="reference/api/org/eclipse/rse/services/clientserver/processes/handlers/package-summary.html"/> - <topic label="org.eclipse.rse.services.clientserver.processes" href="reference/api/org/eclipse/rse/services/clientserver/processes/package-summary.html"/> - <topic label="org.eclipse.rse.services.clientserver.search" href="reference/api/org/eclipse/rse/services/clientserver/search/package-summary.html"/> - <topic label="org.eclipse.rse.services.clientserver.archiveutils" href="reference/api/org/eclipse/rse/services/clientserver/archiveutils/package-summary.html"/> - <topic label="org.eclipse.rse.services.clientserver.util.tar" href="reference/api/org/eclipse/rse/services/clientserver/util/tar/package-summary.html"/> - </topic> - <topic label="Basic Services Layer"> - <topic label="org.eclipse.rse.services" href="reference/api/org/eclipse/rse/services/package-summary.html"/> - <topic label="org.eclipse.rse.services.files" href="reference/api/org/eclipse/rse/services/files/package-summary.html"/> - <topic label="org.eclipse.rse.services.files.ftp" href="reference/api/org/eclipse/rse/services/files/ftp/package-summary.html"/> - <topic label="org.eclipse.rse.services.processes" href="reference/api/org/eclipse/rse/services/processes/package-summary.html"/> - <topic label="org.eclipse.rse.services.search" href="reference/api/org/eclipse/rse/services/search/package-summary.html"/> - <topic label="org.eclipse.rse.services.shells" href="reference/api/org/eclipse/rse/services/shells/package-summary.html"/> - </topic> - <topic label="Services Implementations"> - <topic label="org.eclipse.rse.services.local" href="reference/api/org/eclipse/rse/services/local/package-summary.html"/> - <topic label="org.eclipse.rse.services.local.files" href="reference/api/org/eclipse/rse/services/local/files/package-summary.html"/> - <topic label="org.eclipse.rse.services.local.processes" href="reference/api/org/eclipse/rse/services/local/processes/package-summary.html"/> - <topic label="org.eclipse.rse.services.local.shells" href="reference/api/org/eclipse/rse/services/local/shells/package-summary.html"/> - <topic label="org.eclipse.rse.services.local.search" href="reference/api/org/eclipse/rse/services/local/search/package-summary.html"/> - <topic label="org.eclipse.rse.services.dstore" href="reference/api/org/eclipse/rse/services/dstore/package-summary.html"/> - <topic label="org.eclipse.rse.services.dstore.files" href="reference/api/org/eclipse/rse/services/dstore/files/package-summary.html"/> - <topic label="org.eclipse.rse.services.dstore.processes" href="reference/api/org/eclipse/rse/services/dstore/processes/package-summary.html"/> - <topic label="org.eclipse.rse.services.dstore.shells" href="reference/api/org/eclipse/rse/services/dstore/shells/package-summary.html"/> - <topic label="org.eclipse.rse.services.dstore.rmtservice" href="reference/api/org/eclipse/rse/services/dstore/rmtservice/package-summary.html"/> - <topic label="org.eclipse.rse.services.dstore.search" href="reference/api/org/eclipse/rse/services/dstore/search/package-summary.html"/> - <topic label="org.eclipse.rse.services.dstore.util" href="reference/api/org/eclipse/rse/services/dstore/util/package-summary.html"/> - <topic label="org.eclipse.rse.services.ssh" href="reference/api/org/eclipse/rse/services/ssh/package-summary.html"/> - <topic label="org.eclipse.rse.services.ssh.files" href="reference/api/org/eclipse/rse/services/ssh/files/package-summary.html"/> - <topic label="org.eclipse.rse.services.ssh.shell" href="reference/api/org/eclipse/rse/services/ssh/shell/package-summary.html"/> - </topic> - <topic label="DStore Security and Miners"> - <topic label="org.eclipse.rse.dstore.security" href="reference/api/org/eclipse/rse/dstore/security/package-summary.html"/> - <topic label="org.eclipse.rse.dstore.security.preference" href="reference/api/org/eclipse/rse/dstore/security/preference/package-summary.html"/> - <topic label="org.eclipse.rse.dstore.security.util" href="reference/api/org/eclipse/rse/dstore/security/util/package-summary.html"/> - <topic label="org.eclipse.rse.dstore.security.widgets" href="reference/api/org/eclipse/rse/dstore/security/widgets/package-summary.html"/> - <topic label="org.eclipse.rse.dstore.security.wizards" href="reference/api/org/eclipse/rse/dstore/security/wizards/package-summary.html"/> - <topic label="org.eclipse.rse.dstore.universal.miners.command" href="reference/api/org/eclipse/rse/dstore/universal/miners/command/package-summary.html"/> - <topic label="org.eclipse.rse.dstore.universal.miners.command.patterns" href="reference/api/org/eclipse/rse/dstore/universal/miners/command/patterns/package-summary.html"/> - <topic label="org.eclipse.rse.dstore.universal.miners.environment" href="reference/api/org/eclipse/rse/dstore/universal/miners/environment/package-summary.html"/> - <topic label="org.eclipse.rse.dstore.universal.miners.filesystem" href="reference/api/org/eclipse/rse/dstore/universal/miners/filesystem/package-summary.html"/> - <topic label="org.eclipse.rse.dstore.universal.miners" href="reference/api/org/eclipse/rse/dstore/universal/miners/package-summary.html"/> - <topic label="org.eclipse.rse.dstore.universal.miners.processes" href="reference/api/org/eclipse/rse/dstore/universal/miners/processes/package-summary.html"/> - </topic> - <topic label="Connector Service Implementations"> - <topic label="org.eclipse.rse.connectorservice.dstore" href="reference/api/org/eclipse/rse/connectorservice/dstore/package-summary.html"/> - <topic label="org.eclipse.rse.connectorservice.dstore.util" href="reference/api/org/eclipse/rse/connectorservice/dstore/util/package-summary.html"/> - <topic label="org.eclipse.rse.connectorservice.local" href="reference/api/org/eclipse/rse/connectorservice/local/package-summary.html"/> - <topic label="org.eclipse.rse.connectorservice.ssh" href="reference/api/org/eclipse/rse/connectorservice/ssh/package-summary.html"/> - </topic> - <topic label="File Subsystem"> - <topic label="org.eclipse.rse.subsystems.files.core" href="reference/api/org/eclipse/rse/subsystems/files/core/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.core.model" href="reference/api/org/eclipse/rse/subsystems/files/core/model/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.core.servicesubsystem" href="reference/api/org/eclipse/rse/subsystems/files/core/servicesubsystem/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.core.subsystems" href="reference/api/org/eclipse/rse/subsystems/files/core/subsystems/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.core.util" href="reference/api/org/eclipse/rse/subsystems/files/core/util/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.dstore.model" href="reference/api/org/eclipse/rse/subsystems/files/dstore/model/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.dstore.old" href="reference/api/org/eclipse/rse/subsystems/files/dstore/old/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.dstore" href="reference/api/org/eclipse/rse/subsystems/files/dstore/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.dstore.subsystem" href="reference/api/org/eclipse/rse/subsystems/files/dstore/subsystem/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.ftp.connectorservice" href="reference/api/org/eclipse/rse/subsystems/files/ftp/connectorservice/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.ftp.model" href="reference/api/org/eclipse/rse/subsystems/files/ftp/model/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.ftp" href="reference/api/org/eclipse/rse/subsystems/files/ftp/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.local.model" href="reference/api/org/eclipse/rse/subsystems/files/local/model/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.local" href="reference/api/org/eclipse/rse/subsystems/files/local/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.files.ssh" href="reference/api/org/eclipse/rse/subsystems/files/ssh/package-summary.html"/> - </topic> - <topic label="Process Subsystem"> - <topic label="org.eclipse.rse.subsystems.processes.core" href="reference/api/org/eclipse/rse/subsystems/processes/core/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.processes.core.subsystem.impl" href="reference/api/org/eclipse/rse/subsystems/processes/core/subsystem/impl/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.processes.core.subsystem" href="reference/api/org/eclipse/rse/subsystems/processes/core/subsystem/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.processes.dstore" href="reference/api/org/eclipse/rse/subsystems/processes/dstore/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.processes.local" href="reference/api/org/eclipse/rse/subsystems/processes/local/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.processes.servicesubsystem" href="reference/api/org/eclipse/rse/subsystems/processes/servicesubsystem/package-summary.html"/> - </topic> - <topic label="Shell Subsystem"> - <topic label="org.eclipse.rse.subsystems.shells.core" href="reference/api/org/eclipse/rse/subsystems/shells/core/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.shells.core.model" href="reference/api/org/eclipse/rse/subsystems/shells/core/model/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.shells.core.subsystems" href="reference/api/org/eclipse/rse/subsystems/shells/core/subsystems/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.shells.core.subsystems.servicesubsystem" href="reference/api/org/eclipse/rse/subsystems/shells/core/subsystems/servicesubsystem/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.shells.dstore.model" href="reference/api/org/eclipse/rse/subsystems/shells/dstore/model/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.shells.dstore" href="reference/api/org/eclipse/rse/subsystems/shells/dstore/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.shells.local.model" href="reference/api/org/eclipse/rse/subsystems/shells/local/model/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.shells.local" href="reference/api/org/eclipse/rse/subsystems/shells/local/package-summary.html"/> - <topic label="org.eclipse.rse.subsystems.shells.ssh" href="reference/api/org/eclipse/rse/subsystems/shells/ssh/package-summary.html"/> - </topic> - <topic label="User Interface"> - <topic label="org.eclipse.rse.ui" href="reference/api/org/eclipse/rse/ui/package-summary.html"/> - <topic label="org.eclipse.rse.ui.actions" href="reference/api/org/eclipse/rse/ui/actions/package-summary.html"/> - <topic label="org.eclipse.rse.ui.dialogs" href="reference/api/org/eclipse/rse/ui/dialogs/package-summary.html"/> - <topic label="org.eclipse.rse.ui.filters.actions" href="reference/api/org/eclipse/rse/ui/filters/actions/package-summary.html"/> - <topic label="org.eclipse.rse.ui.filters.dialogs" href="reference/api/org/eclipse/rse/ui/filters/dialogs/package-summary.html"/> - <topic label="org.eclipse.rse.ui.filters" href="reference/api/org/eclipse/rse/ui/filters/package-summary.html"/> - <topic label="org.eclipse.rse.ui.messages" href="reference/api/org/eclipse/rse/ui/messages/package-summary.html"/> - <topic label="org.eclipse.rse.ui.open" href="reference/api/org/eclipse/rse/ui/open/package-summary.html"/> - <topic label="org.eclipse.rse.ui.operations" href="reference/api/org/eclipse/rse/ui/operations/package-summary.html"/> - <topic label="org.eclipse.rse.ui.propertypages" href="reference/api/org/eclipse/rse/ui/propertypages/package-summary.html"/> - <topic label="org.eclipse.rse.ui.validators" href="reference/api/org/eclipse/rse/ui/validators/package-summary.html"/> - <topic label="org.eclipse.rse.ui.view.monitor" href="reference/api/org/eclipse/rse/ui/view/monitor/package-summary.html"/> - <topic label="org.eclipse.rse.ui.view" href="reference/api/org/eclipse/rse/ui/view/package-summary.html"/> - <topic label="org.eclipse.rse.ui.view.scratchpad" href="reference/api/org/eclipse/rse/ui/view/scratchpad/package-summary.html"/> - <topic label="org.eclipse.rse.ui.view.search" href="reference/api/org/eclipse/rse/ui/view/search/package-summary.html"/> - <topic label="org.eclipse.rse.ui.view.team" href="reference/api/org/eclipse/rse/ui/view/team/package-summary.html"/> - <topic label="org.eclipse.rse.ui.widgets" href="reference/api/org/eclipse/rse/ui/widgets/package-summary.html"/> - <topic label="org.eclipse.rse.ui.widgets.services" href="reference/api/org/eclipse/rse/ui/widgets/services/package-summary.html"/> - <topic label="org.eclipse.rse.ui.wizards" href="reference/api/org/eclipse/rse/ui/wizards/package-summary.html"/> - </topic> - <topic label="File UI"> - <topic label="org.eclipse.rse.files.ui" href="reference/api/org/eclipse/rse/files/ui/package-summary.html"/> - <topic label="org.eclipse.rse.files.ui.actions" href="reference/api/org/eclipse/rse/files/ui/actions/package-summary.html"/> - <topic label="org.eclipse.rse.files.ui.compare" href="reference/api/org/eclipse/rse/files/ui/compare/package-summary.html"/> - <topic label="org.eclipse.rse.files.ui.dialogs" href="reference/api/org/eclipse/rse/files/ui/dialogs/package-summary.html"/> - <topic label="org.eclipse.rse.files.ui.propertypages" href="reference/api/org/eclipse/rse/files/ui/propertypages/package-summary.html"/> - <topic label="org.eclipse.rse.files.ui.resources" href="reference/api/org/eclipse/rse/files/ui/resources/package-summary.html"/> - <topic label="org.eclipse.rse.files.ui.search" href="reference/api/org/eclipse/rse/files/ui/search/package-summary.html"/> - <topic label="org.eclipse.rse.files.ui.view" href="reference/api/org/eclipse/rse/files/ui/view/package-summary.html"/> - <topic label="org.eclipse.rse.files.ui.widgets" href="reference/api/org/eclipse/rse/files/ui/widgets/package-summary.html"/> - <topic label="org.eclipse.rse.files.ui.wizards" href="reference/api/org/eclipse/rse/files/ui/wizards/package-summary.html"/> - </topic> - <topic label="Process UI"> - <topic label="org.eclipse.rse.processes.ui" href="reference/api/org/eclipse/rse/processes/ui/package-summary.html"/> - <topic label="org.eclipse.rse.processes.ui.actions" href="reference/api/org/eclipse/rse/processes/ui/actions/package-summary.html"/> - <topic label="org.eclipse.rse.processes.ui.dialogs" href="reference/api/org/eclipse/rse/processes/ui/dialogs/package-summary.html"/> - <topic label="org.eclipse.rse.processes.ui.propertypages" href="reference/api/org/eclipse/rse/processes/ui/propertypages/package-summary.html"/> - <topic label="org.eclipse.rse.processes.ui.view" href="reference/api/org/eclipse/rse/processes/ui/view/package-summary.html"/> - </topic> - <topic label="Shell UI"> - <topic label="org.eclipse.rse.shells.ui" href="reference/api/org/eclipse/rse/shells/ui/package-summary.html"/> - <topic label="org.eclipse.rse.shells.ui.actions" href="reference/api/org/eclipse/rse/shells/ui/actions/package-summary.html"/> - <topic label="org.eclipse.rse.shells.ui.propertypages" href="reference/api/org/eclipse/rse/shells/ui/propertypages/package-summary.html"/> - <topic label="org.eclipse.rse.shells.ui.view" href="reference/api/org/eclipse/rse/shells/ui/view/package-summary.html"/> - </topic> - </topic> - <topic label="Remote Systems API Reference All Packages" href="reference/api/overview-summary.html"> - </topic> -</toc>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.isv/topics_Samples.xml b/rse/doc/org.eclipse.rse.doc.isv/topics_Samples.xml deleted file mode 100755 index 7d833dae9..000000000 --- a/rse/doc/org.eclipse.rse.doc.isv/topics_Samples.xml +++ /dev/null @@ -1,9 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the samples -->
-<!-- ============================================================================= -->
-<toc label="Examples" >
- <topic label="Installing the Examples" href="samples/samples.html" />
- <anchor id="examples"/>
-</toc>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/.project b/rse/doc/org.eclipse.rse.doc.user/.project deleted file mode 100755 index 21a245ce6..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.rse.doc.user</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/rse/doc/org.eclipse.rse.doc.user/META-INF/MANIFEST.MF b/rse/doc/org.eclipse.rse.doc.user/META-INF/MANIFEST.MF deleted file mode 100755 index 139357595..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/META-INF/MANIFEST.MF +++ /dev/null @@ -1,8 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.rse.doc.user; singleton:=true -Bundle-Version: 1.0.0.qualifier -Bundle-Vendor: %providerName -Bundle-Localization: plugin -Eclipse-LazyStart: false diff --git a/rse/doc/org.eclipse.rse.doc.user/about.html b/rse/doc/org.eclipse.rse.doc.user/about.html deleted file mode 100755 index 460233046..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/about.html +++ /dev/null @@ -1,28 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/> -<title>About</title> -</head> -<body lang="EN-US"> -<h2>About This Content</h2> - -<p>June 2, 2006</p> -<h3>License</h3> - -<p>The Eclipse Foundation makes available all content in this plug-in ("Content"). Unless otherwise -indicated below, the Content is provided to you under the terms and conditions of the -Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available -at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>. -For purposes of the EPL, "Program" will mean the Content.</p> - -<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is -being redistributed by another party ("Redistributor") and different terms and conditions may -apply to your use of any object code in the Content. Check the Redistributor's license that was -provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise -indicated below, the terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p> - -</body> -</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/book.css b/rse/doc/org.eclipse.rse.doc.user/book.css deleted file mode 100755 index 157414c6c..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/book.css +++ /dev/null @@ -1 +0,0 @@ -@import "../PRODUCT_PLUGIN/book.css";
diff --git a/rse/doc/org.eclipse.rse.doc.user/build.properties b/rse/doc/org.eclipse.rse.doc.user/build.properties deleted file mode 100755 index b362f9bc4..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/build.properties +++ /dev/null @@ -1,24 +0,0 @@ -############################################################################### -# Copyright (c) 2005, 2006 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -# Martin Oberhuber (WindRiver) - Add Getting Started Guide -############################################################################### -bin.includes = META-INF/,\ - plugin.xml,\ - about.html,\ - concepts/,\ - images/,\ - plugin.properties,\ - ref/,\ - tasks/,\ - book.css,\ - notices.html,\ - toc.xml,\ - gettingstarted/ -
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/concepts/cbegin.html b/rse/doc/org.eclipse.rse.doc.user/concepts/cbegin.html deleted file mode 100755 index d47ca9247..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/concepts/cbegin.html +++ /dev/null @@ -1,66 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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 Connections</title>
-</head>
-<body id="cbegin">
-<a name="cbegin"><!-- --></a>
-<h1 class="topictitle1">Remote System Explorer Connections</h1>
-<div>
-<p>When you first open the Remote System Explorer, you are not
-connected to
-any system except your local workstation. To connect to a remote
-server,
-you need to define a connection. A connection is a TCP/IP network
-connection
-to your server, that enables you to access, edit, run, compile, and
-debug items on the server. When you define a connection, you select the
-type of connection you want, specify the
-name or IP address of the remote system and you also give the
-connection itself
-a unique name that acts as a label in your workspace so that you can
-easily
-connect and disconnect. These actions are performed in the Remote
-System Explorer. </p>
-<p>When you open the workbench for the first time, you
-need to define a profile,
-define a connection, and then connect to a server. When you connect,
-the workbench prompts you for your user ID and password on that server
-so
-that you can access the folders and files on that server.</p>
-<p>Note: Make sure you have started the server programs on your
-remote system. These programs depend on the kind of system you
-are connecting to. See the appropriate tasks below for the recommended
-ways to configure and start your server.</p>
-<p>When you have a connection, you can organize your data using <a
- href="cfilters.html">filters,
-filter pools, and filter pool references</a>, which list a set of
-folders and files from your server in the Remote Systems view. </p>
-<p>You can use the Remote System Explorer to access files on many
-kinds
-of servers, such as Linux, UNIX, Windows, or your local workstation. If
-you have the appropriate IBM products installed you can also connect to
-iSeries and zSeries servers. See the
-links below for information on how to connect to these other kinds of
-servers.</p>
-</div>
-<div>
-<p><b class="relconceptshd">Related concepts</b><br/>
-<a href="cfilters.html" title="">Remote System Explorer filters, filter
-pools, and filter pool references</a><br/>
-<a href="cprofile.html" title="">Remote System Explorer Profiles</a><br/>
-<a href="cuniversal.html">Universal Systems</a><br/>
-</p>
-<p><b class="reltaskshd">Related tasks</b><br/>
-<a href="../tasks/tbeginlinux.html" title="">Connecting to a remote
-Linux or UNIX server</a><br/>
-<a href="../tasks/tbeginwindows.html" title="">Connecting to a remote
-Windows server</a><br/>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/concepts/cfilters.html b/rse/doc/org.eclipse.rse.doc.user/concepts/cfilters.html deleted file mode 100755 index c8197d730..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/concepts/cfilters.html +++ /dev/null @@ -1,118 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> -<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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 filters, filter pools, and filter pool references</title> -</head> - -<body id="cfilters"> -<a name="cfilters"><!-- --></a> -<h1 class="topictitle1">Remote System Explorer filters, filter pools, -and filter pool references</h1> -<div> -<p>The Remote System Explorer is a set of local client tools you use to -organize -how you want to work with the resources such as folders and files on -your -remote server. The following graphic serves as an introduction to -some of the main components of the Remote System Explorer:<br/> -<img src="../images/ModelRSE.gif" alt=""/><br/> -</p> -<div class="p">In the Remote System Explorer perspective, you query -your server -to list and perform actions upon remote resources such as folders and -files. You perform -these tasks on these remote resources by using <i>filters</i> that -show these resources at your workstation.<br/> -</div> -<p>The Remote System Explorer perspective is designed to allow you to -manipulate the resources directly on the remote system. The -actions that are available depend on the type of system you are -connecting to and the way the resource is recognized. For -example, your selections can define -a filter string to find all files that match *.c in a particular -directory. </p> -<div class="p">When you access the list by expanding the filter, you -can see all the files that match that filter and you can perform -actions (such as editing, compiling, running, and debugging) against -these files. -<div class="note"><span class="notetitle">Note: </span>You can drag -and drop filters from one subsystem or filter -pool to another. However, if you drag a filter into another filter, the -filter strings from the source filter are added to the ones already in -the target -filter.</div> -</div> -<p id="cfilters__poolsdesc"><a name="cfilters__poolsdesc"><!-- --></a>If -you have been using the Remote System Explorer for some -time, your workspace might contain too many filters to navigate easily. -Or, -you might just want to keep groups of filters separate if, for example, -you -need to represent two distinct environments in the Remote System -Explorer, -regardless of how many filters you have. In either case, you can group -filters -into <i>filter pools</i>. </p> -<p>For example, one filter pool could contain filters for an accounts -receivable -program while another contains filters for a payroll program. Or, if -you -have two different environments on your server: a production -environment and a test environment, you can define a distinct -environment and set of filters for each. </p> -<p id="cfilters__poolsdesc2"><a name="cfilters__poolsdesc2"><!-- --></a>Without -filter pools, all of your filters appear together -in all connections. When you create filter pools, however, any filter -you -create within that filter pool is distinct to that connection, and will -not -appear in any other connections. (See the related links for more -information -about filter pools.)</p> -<p id="cfilters__filterstrings"><a name="cfilters__filterstrings"><!-- --></a>You -can share filter pools among many connections through -the use of a <i>filter pool reference</i>. A filter pool reference is -a mechanism -that displays a filter pool from one connection in any other -connection, so -that when you make a change to the original filter pool, your change is -reflected -your filter pool reference.</p> -<p>All connections, filters, filter pools, and so on, belong to a -Remote System Explorer <i>profile</i>, that you define during your -first connection -to a server. You might wonder what happens to your filters or filter -pools if you delete a connection, especially if you have filters shared -among -two or more connections. Rest assured that the filters are not deleted, -since -filters actually belong to profiles, and not connections.<br/> -</p> -<p>Keep in mind that if you need to have an entirely new configuration -of filter pools, filters and connection in the Remote System Explorer, -you can always create a new profile. See -the related links for more information.</p> -</div> -<div> -<!-- TODODeferred -<p><b class="relconceptshd">Related concepts</b><br/> -<a href="cuseractions.html" title="">User actions (user options)</a><br/> -<a href="cremcompile.html" title="">Compiling</a><br/> -</p> ---> -<p><b>Related Tasks</b><br/> -<a href="../tasks/tmanagepools.html" title="">Configuring filter pools</a><br/> -<a href="../tasks/tmanageedit.html" - title="You can change the properties for any filter by opening the filter's properties sheet. You can also add new filter strings to a filter from this sheet. For example, if you have a filter that lists all *.rpgle source members, you can add an additional filter string that will display all *.cblle source members as well.">Changing -filters</a><br/> -<a href="../tasks/tmanagedel.html" title="">Deleting filters</a><br/> -<a href="../tasks/tbeginsecprofile.html" title="">Creating a second -profile</a><br/> -</p> -</div> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.user/concepts/cprofile.html b/rse/doc/org.eclipse.rse.doc.user/concepts/cprofile.html deleted file mode 100755 index 699abb1e0..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/concepts/cprofile.html +++ /dev/null @@ -1,104 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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 Profiles</title>
-</head>
-<body id="cprofile">
-<a name="cprofile"><!-- --></a>
-<h1 class="topictitle1">Remote System Explorer Profiles</h1>
-<div>
-<p>When you define your first connection to your remote server, you
-will also define
-your first profile. All Remote System Explorer resources such as
-connections,
-filters, and filter pools are owned by a profile. Profiles help you
-manage these resources when you have a lot of connections. The Remote
-System Explorer creates
-a unique profile per team member (that person's <span
- style="font-style: italic;">private profile</span>), plus a common
-profile called <i>Team</i>.
-You can also create your own profiles. </p>
-<div class="p">Profiles contain:
-<ul>
- <li>Connections -- including subsystem properties. User IDs and
-passwords are not shared.</li>
- <li>Filters, filter pools, and filters pool references</li>
- <li>User-defined actions</li>
- <li>Compile commands</li>
-</ul>
-</div>
-<p>Profiles can be active, or inactive. By default, only your private
-profile
-and the Team profile are active. The Remote System Explorer displays
-all connections
-from all active profiles and, within a connection, allows filter pools
-to
-be referenced from any active profile. Further, the user actions and
-compile
-commands shown in the right-click menu for a remote resource are from
-all
-active profiles.</p>
-<p>Your first profile will be for your local workstation. When you
-complete
-the steps for your first connection, you can decide whether to use your
-personal
-profile or the Team profile so that you can share resources and
-information
-with other people.</p>
-<div class="p">Placing all connection and filter data in a profile
-shared by the team
-assists in team support, since all connections, filter pools, and team
-profiles
-can be shared among team members. You can use the Team view to control
-which
-profiles display in your workspace by making the profiles active.
-<div class="note"><span class="notetitle">Note: </span>Making
-a profile active or inactive does not affect your teammates. For
-example,
-you can choose not to display one of your own profiles in your
-workspace,
-but a teammate can make that profile active in his or her workspace.
-You will
-see the profiles you or your teammates have made inactive in the Team
-view when you perform a synchronization with the repository in which
-the profiles are stored. See topics in the help contents and
-links
-below about team support for more information on profiles and shared
-data.</div>
-</div>
-<p>To reduce collisions when you synchronize the user IDs and the
-ordering of
-resources in a profile are stored locally on your workstation. To
-participate
-in team support, you need to synchronize with, and upload your profiles
-to a central repository. Use the <a href="../tasks/tteamsup.html">Team
-view</a> to
-share source and profile information with other team members, and to
-synchronize
-that information with the repository. Everything except your user ID
-will
-then be stored on the server, and any developer can obtain profile
-resources
-from the central server. </p>
-</div>
-<div>
-<p><b class="relconceptshd">Related concepts</b><br/>
-<a href="cfilters.html" title="">Remote System Explorer filters, filter
-pools, and filter pool references</a><br/>
-<a href="cbegin.html" title="">Remote System Explorer Connections</a><br/>
-<a href="cteam.html" title="">Team support</a><br/>
-</p>
-<p><b class="reltaskshd">Related tasks</b><br/>
-<a href="../tasks/tteamsup.html" title="">Using team support</a><br/>
-<a href="../tasks/tteamsup1.html" title="">Working with profiles and
-team support</a><br/>
-<a href="../tasks/tbeginsecprofile.html" title="">Creating a second
-profile</a><br/>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/concepts/cremcompile.html b/rse/doc/org.eclipse.rse.doc.user/concepts/cremcompile.html deleted file mode 100755 index 8278d329e..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/concepts/cremcompile.html +++ /dev/null @@ -1,60 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Compiling</title>
-</head>
-
-<body id="cremcompile">
-<a name="cremcompile"><!-- --></a>
-<h1 class="topictitle1">Compiling Programs</h1>
-<div>
-<p>You can run a compile command on a server from the Remote System
-Explorer perspective. When you compile, the workbench determines
-the source type of the file, and then runs
-the last used compile command for that type. However, you can always
-change
-this behavior through Remote Systems preferences (see the related
-links).</p>
-<p>You can also compile multiple resources listed in a filter by
-holding down the CTRL key and clicking on all the members
-you want to compile, right-click to access the compile menu, and then
-select the compile command you wish to run. The workbench determines
-what order to compile these resources according to the preferences you
-specify for that workspace.</p>
-<div class="p">Note that multiple file compilation is disabled if:
-<ul>
- <li>One or more of the selected source types are not compatible.</li>
- <li>The selected resources are not from the same connection.</li>
-</ul>
-</div>
-<p>A compile command is always associated with a particular source
-type. It consists of an identifier and a command string that will be
-run on the
-server. Each profile in the Remote System Explorer has a set of
-source member types,
-and each source type has a set of compile commands associated with
-them. You
-can add source types to a profile and add compile commands to a source
-type.</p>
-<p>IBM supplies a number
-of default compile commands for common file types and you can also add
-your own. Since compile commands are owned by a profile they can
-be shared using team support.</p>
-<p>See the related topics below for more information.</p>
-</div>
-<div>
-<p><b class="reltaskshd">Related concepts</b><br/>
-<a href="cprofile.html"><span style="text-decoration: underline;">Profiles</span></a><br/>
-<a href="crunremcmds.html">Commands and Shells</a><br/>
-</p>
-<p><b class="relrefhd">Related reference</b><br/>
-<a href="../ref/rrsepref.html" title="">Preferences</a><br/>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/concepts/crunremcmds.html b/rse/doc/org.eclipse.rse.doc.user/concepts/crunremcmds.html deleted file mode 100755 index b80a30d08..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/concepts/crunremcmds.html +++ /dev/null @@ -1,43 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Shells and commands in the Remote Systems view</title>
-</head>
-
-<body id="crunremcmds">
-<a name="crunremcmds"><!-- --></a>
-<h1 class="topictitle1">Shells and commands in the Remote Systems view</h1>
-<div>
-<p>You can use the Remote Commands view to run and interact with commands
-and command shells on universal systems. A universal system includes Windows,
-Linux, and UNIX system types.<br/>
-</p>
-<p>Specifically, use the view to: </p>
-<ul>
- <li>Run commands in a command shell</li>
- <li>Display and interpret the output of a program</li>
- <li>Enter input to a program</li>
- <li>Display and manage different commands and shells from the same
-view. Multiple commands can be run in a single shell (one command at a time per
-shell), multiple shells may be run on a single system, and multiple systems may be
-running shells.</li>
-</ul>
-<p>Whenever a command shell is launched or a command is run from within
-Remote System Explorer, the Remote Commands view is used to display the output
-and provide a way to work with that output. </p>
-</div>
-<div>
-<p><b class="reltaskshd">Related tasks</b><br/>
-<a href="../tasks/truncmdsview.html" title="">Running and viewing
-commands and shells using the Remote Commands view</a><br/>
-<a href="../tasks/twrkcmdshl.html" title="In the Remote Systems view, you can launch a shell to perform commands in the iSeries Integrated File System (IFS).">Working
-with command shells</a><br/>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/concepts/cteam.html b/rse/doc/org.eclipse.rse.doc.user/concepts/cteam.html deleted file mode 100755 index 06fc46578..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/concepts/cteam.html +++ /dev/null @@ -1,71 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> -<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Team support</title> -</head> -<body id="cteam"> -<a name="cteam"><!-- --></a> -<h1 class="topictitle1">Team support</h1> -<div> -<p>The team support model works with shared repositories that store -version-managed resources on servers that are accessible to the entire team. Usually -you would share the folders and files of an Eclipse project. Each -team member sends their changes to the repository, and receives changes -that -were made by a team member from the repository. While the Remote System -Explorer -is not project-based, (it is designed for direct access to remote -resources), -there is a single project created for all the non-remote resources that -the -Remote System Explorer manages. Profiles are stored in that project and -so everything that belongs to a profile can be -shared with your teammates.</p> -<div class="p" id="cteam__profilelist"><a name="cteam__profilelist"><!-- --></a>Profiles -contain: -<ul> - <li>Connections -- including various subsystem properties. User IDs -and passwords are not shared.</li> - <li>Filters, filter pools, and filters pool references</li> - <li>User-defined actions</li> - <li>Compile commands</li> -</ul> -</div> -<p> Use the Team view of the Remote System Explorer perspective to -associate -and synchronize the project named RemoteSystemsConnection that contains -these profiles with a repository. After -synchronizing with the repository, you will receive all the shared -Remote System -Explorer resources from your team, including their profiles. You then -use the <b>Reload Remote System Explorer</b> action, located on the -pop-up menu, to make the Remote System Explorer know about these -changes. You can also, of course, quit and restart the -workbench. See the related tasks for more information.</p> -<p>Any resources received that are in a profile that you have already -active, such -as Team, will immediately be available and accessible to you. However, -resources -in other profiles will not be available unless you choose to make those -profiles -active. If you use multiple workstations, team support can also be used -to -make your own private configurations of filters, filter pools, and -connections available on all the workstations by making -your profile active on each workstation.</p> -</div> -<div> -<p><b class="relconceptshd">Related concepts</b><br/> -<a href="cprofile.html" title="">Remote System Explorer Profiles</a><br/> -</p> -<p><b class="reltaskshd">Related tasks</b><br/> -<a href="../tasks/tteamsup.html" title="">Using team support</a><br/> -<a href="../tasks/tteamsup1.html" title="">Working with profiles and team support</a><br/> -</p> -</div> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.user/concepts/cuniversal.html b/rse/doc/org.eclipse.rse.doc.user/concepts/cuniversal.html deleted file mode 100755 index b9f44ff41..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/concepts/cuniversal.html +++ /dev/null @@ -1,54 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2003, 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>Linux, UNIX, and Windows host access</title>
-</head>
-
-<body>
-<a name="cuniversal"><!-- --></a>
-<h1 class="topictitle1">Universal Systems</h1>
-<div>
-<p>At a minimum the Remote System Explorer provides access to
-Linux,
-UNIX, and Windows systems. These are called "universal" systems
-since their file and command systems are quite similar. You can
-export,
-import, explore remote files, and run remote
-commands on all of these system types.
-You can also drag/drop and copy/paste between
-two systems of the same or different type.
-For example, you can drag and drop a file
-from your Windows host to your Linux host,
-from one Linux host to another, or from one
-file in your Linux host to another file in
-the same host.</p>
-<p>The Remote System Explorer can also provide access to other types of
-systems if the support is installed in the workbench. Examples of
-such systems might be IBM iSeries or zSeries server systems.<br/>
-</p>
-<p>Expand the topics in the help contents or click the following links
-for
-information on Universal host access:<br/>
-</p>
-</div>
-<div>
-<p><b>Related concepts</b><br clear="all"/>
-<a href="crunremcmds.html">Shells and commands in the Remote Systems view</a><br clear="all"/>
-</p>
-<p><b>Related tasks</b><br clear="all"/>
-<a href="../tasks/tbeginlinux.html">Connecting to a remote Linux or UNIX host</a><br clear="all"/>
-<a href="../tasks/tbeginwindows.html">Connecting to a remote Windows host</a><br clear="all"/>
-<a href="../tasks/tbeginsecond.html">Creating a second connection to aremote host</a><br clear="all"/>
-<a href="../tasks/tbegindelete.html">Deleting a connection</a><br clear="all"/>
-<a href="../tasks/tbegindiscon.html">Disconnecting from a remote host</a><br clear="all"/>
-<a href="../tasks/ttablecopy.html">Copying and pasting in the Remote System Explorer</a><br clear="all"/>
-<a href="../tasks/ttabledrag.html">Dragging and dropping items in the Remote System Explorer</a><br clear="all"/>
-<a href="../tasks/tbeginenv.html">Configuring environment variablesupport for connections</a>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/concepts/cuseractions.html b/rse/doc/org.eclipse.rse.doc.user/concepts/cuseractions.html deleted file mode 100755 index eda38a272..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/concepts/cuseractions.html +++ /dev/null @@ -1,48 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>User actions (user options)</title>
-</head>
-
-<body id="cuseractions">
-<a name="cuseractions"><!-- --></a>
-<h1 class="topictitle1">User actions (user options)</h1>
-<div>
-<p>User actions are server commands that you define on the <b>Work
-With
-User Actions</b> window, and will run against resources such as files
-and folders on your server.</p>
-<div class="p">Each user action has:
-<ul>
- <li>A unique name. </li>
- <li>A command (that might have substitution variables). The user
-action may also
-specify how the command is to be run on the server.</li>
- <li>Substitution variables that are replaced with information from
-the resource (such as its name) when
-the command is run.</li>
- <li>An optional comment used to describe the action in more detail.</li>
- <li>Various options to affect what happens when the command is run;
-for example,
-whether to prompt first.</li>
- <li>One or more file types that limit the action to specific types of
-remote resources. For example, a command to start a program that
-searches text files could be limited to just text files. The action is
-only shown
-for remote objects which is one of the specified types.</li>
-</ul>
-</div>
-</div>
-<div>
-<p><b class="reltaskshd">Related tasks</b><br/>
-<a href="../tasks/tworkuseract.html" title="">Managing user actions
-(user options)</a><br/>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g1installing.html b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g1installing.html deleted file mode 100644 index 21def5b6e..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g1installing.html +++ /dev/null @@ -1,48 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> -<meta name="copyright" content="Copyright (c) 2006 Wind River Systems, Inc. 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>Installing the RSE</title> -</head> -<body id="g1installing"> -<a name="g1installing"><!-- --></a> -<h1 class="topictitle1">Installing the Remote System Explorer</h1> -<div> -The simplest way to get RSE is via the Update Manager: From your running instance -of Eclipse 3.2, choose <i>Help > Software Updates > Find and Install...</i>. -Choose "Search for New Features to Install", and add a new Remote Site named -"RSE" and pointing to <a href="http://download.eclipse.org/dsdp/tm/updates/"> -http://download.eclipse.org/dsdp/tm/updates/</a>. -Select the RSE SDK feature, and perform the update process as usual.</p> - -<p>If you prefer manual installation, you can download RSE SDK from the -DSDP <a href="http://download.eclipse.org/dsdp/tm/downloads/">Target -Management Download Site</a> and extract it into your installation of -Eclipse 3.2 or later, or link it as product extension. -<p>Start Eclipse Workbench, and choose <i>Window > Open Perspective > -Other > Remote System Explorer</i>.</p> -</div> - -<div> -<!-- -<p><b class="relconceptshd">Related concepts</b><br/> -<a href="../concepts/cbegin.html" title="">Remote System Explorer Connections</a><br/> -</p> -<p><b class="reltaskshd">Related tasks</b><br/> ---> -<p><b class="reltaskshd">Follow-up tasks</b><br/> -<a href="g2firststeps.html" title="">First Steps with the Remote System Explorer</a><br/> -<a href="../tasks/tbeginlinux.html" title="">Setting up a dstore server</a><br/> -<!-- -<a href="../tasks/tbeginwindows.html" title="">Connecting to a remote -Windows server</a><br/> ---> -<a href="gusing.html" title="">Using Remote System Explorer Connections</a><br/> -<a href="gxtending.html" title="">Extending Remote System Explorer</a><br/> -</p> -</div> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g2firststeps.html b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g2firststeps.html deleted file mode 100644 index 031a14bcb..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g2firststeps.html +++ /dev/null @@ -1,61 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> -<meta name="copyright" content="Copyright (c) 2006 Wind River Systems, Inc. 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>First Steps with RSE</title> -</head> -<body id="g2firststeps"> -<a name="g2firststeps"><!-- --></a> -<h1 class="topictitle1">First Steps with the Remote System Explorer</h1> -<div> -Even without an actual connection to a remote system, you can start experimenting -with the Remote System Explorer UI on the local host, which is shown by default -under the <i>Local</i> node: -<ul> - <li>Browse the Filesystem, choose <i>contextmenu > show in Table</i>, and - observe the Properties view.</li> - <li>Create a new <a href="../concepts/cfilters.html">Filter</a> to show - specific resources in the file system only.</li> - <li>Launch an <a href="../concepts/crunremcmds.html">RSE Shell</a> - (Shells node > Launch) - <ul><li>In the Shell, perform commands such as ls, dir, ps, gcc, make and see - the output interpreted</li> - <li>Use Ctrl+Space Content Assist on the shell command entry field</li> - </ul></li> -</ul> -For operations on an actual remote system, you can either -<ul> - <li>use the "<b>SSH Only</b>" system type (<i>New > Other > Remote System Explorer > Connection</i>), or</li> - <li>start a <a href="../tasks/tbeginlinux.html">dstore server daemon</a> - on the remote system and use any of the other connection types.</li> -</ul> -<p>RSE is a framework that supports plugging in many different communication protocols. -By default, the dstore, FTP and ssh protocol plug-ins are provided, with dstore being -the richest in features.<br/> -Dstore requires a server to run on the remote system. There are several methods to -get a server launched for a particular user, the most easy one to set up is the -daemon method.</p> -</div> - -<div> -<p><b class="reltaskshd">Follow-up tasks</b><br/> -<a href="../tasks/tbeginlinux.html" title="">Setting up a dstore server</a><br/> -<a href="gusing.html" title="">Using Remote System Explorer Connections</a><br/> -<a href="gxtending.html" title="">Extending Remote System Explorer</a><br/> -</p> -<p><b class="relconceptshd">Related concepts</b><br/> -<a href="../concepts/cbegin.html" title="">Remote System Explorer Connections</a><br/> -<a href="../concepts/cfilters.html" title="">Remote System Explorer filters, filter -pools, and filter pool references</a><br/> -<a href="../concepts/cuniversal.html">Universal Systems</a><br/> -<a href="../tasks/tbeginlinux.html" title="">Connecting to a remote -Linux or UNIX server</a><br/> -<a href="../tasks/tbeginwindows.html" title="">Connecting to a remote -Windows server</a><br/> -</p> -</div> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g_start.html b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g_start.html deleted file mode 100644 index 9b4836bd3..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g_start.html +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> -<meta name="copyright" content="Copyright (c) 2006 Wind River Systems, Inc. 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>Getting Started with RSE</title> -</head> -<body id="gstart"> -<a name="gstart"><!-- --></a> -<h1 class="topictitle1">Getting Started with the Remote System Explorer</h1> -<div> -<p>The Remote System Explorer (RSE) is a perspective and toolkit in Eclipse -Workbench, that allows you to connect and work with a variety of remote -systems. With the predefined plug-ins, You can look at remote file systems, -transfer files between hosts, do remote search, execute commands and work -with processes.</p> -<p>Additional capabilities may be added by Software Vendors by providing new -<i>System Types</i>, <i>Services</i> and <i>Subsystem implementations</i> -for specific remote access protocols or resource kinds respectively. The framework -helps by providing lots of predefined re-usable components, like persistence -mechanisms, filtering and team sharing.</p> -<a href="../images/RSESample.gif"> -<!-- <img src="../images/RSESample.gif" alt="A sample RSE session" width="917" height="659"/><br/> ---> -<img src="../images/RSESample_small.gif" alt="A sample RSE session" width="459" height="330"/><br/> -</a> -<p>Here is a screenshot of a sample session with RSE (Click on the picture to -enlarge it). -This tutorial will guide you quickly through the most prominent features of -the Remote System Explorer: -<ul> - <li><a href="g1installing.html" title="">Installing the Remote System Explorer</a></li> - <li><a href="g2firststeps.html" title="">First Steps with the Remote System Explorer</a></li> - <li><a href="gusing.html" title="">Using Remote System Explorer Connections</a></li> - <li><a href="gxtending.html" title="">Extending Remote System Explorer</a></li> -</ul> - -</div> - -<div> -<p><b class="relconceptshd">Related concepts</b><br/> -<a href="../concepts/cbegin.html" title="">Remote System Explorer Connections</a><br/> -</p> -<!-- -<p><b class="reltaskshd">Related tasks</b><br/> -<a href="../tasks/tbeginlinux.html" title="">Connecting to a remote -Linux or UNIX server</a><br/> -<a href="../tasks/tbeginwindows.html" title="">Connecting to a remote -Windows server</a><br/> -</p> ---> -</div> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/gusing.html b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/gusing.html deleted file mode 100644 index e4f9f8dd0..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/gusing.html +++ /dev/null @@ -1,69 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> -<meta name="copyright" content="Copyright (c) 2006 Wind River Systems, Inc. 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>Using Remote Connections</title> -</head> -<body id="gusing"> -<a name="gusing"><!-- --></a> -<h1 class="topictitle1">Using Remote Connections</h1> -<div> -Here are a few tasks that help you get acquainted with RSE. All tasks assume that you have -switched to the Remote System Explorer Perspective in your Workbench. Some of the tasks -can not be performed on all system types, although RSE tries to provide a consistent UI -across many different kinds of remote systems.. -<ul> - <li>In the RSE Perspective, Remote Systems View, press the <b>New Connection</b> button.<ul> - <li>Note: In the Preferences, you can enable displaying available new connection types in the RSE tree.</li></ul></li> - <li>Select the desired system type<ul> - <li>Coose system type "SSH Only" for ssh servers, or any other for dstore.</li></ul></li> - <li>Enter an IP address for a remote system running an ssh server or dstore server. - A connection name will be suggested automatically, but can be changed.<ul> - <li>You can also run a dstore server on the local machine for testing. In this case, - type "localhost" as address.</li> - <li>You can press Finish right away, the wizard defaults are usually fine.</li></ul></li> - <li>Fill in the username / password dialog.<ul> - <li>Note: For ssh, if you have private keys, the password here is just a dummy. - Enter anything and save it. You can setup ssh private key authentication through - the <b>Team > CVS > SSH2 Connection Method</b> Preference page.</li></ul></li> - <li><b>Browse remote files</b>, or open remote shells.<ul> - <li>You can <b>drag and drop</b> files between local and remote file systems, between editors and any view. - Files are transferred as needed.</li> - <li>On dstore, you can browse into remote archives (*.zip, *.tar) without having to transfer the entire contents. This works thanks - to "miners" on the remote side. Custom miners can be plugged into the dstore server.<br> - Note: Some tar formats currently fail to work. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139207">bug 139207</a>.</li> - <li>On dstore, you can choose <b>Search > Remote...</b>.<ul> - <li>The dstore miners support searching a remote file system - without having to transfer any data.</li></ul></li> - <li>On dstore, when the remote system is Linux, AIX or Other Unix:<ul> - <li>Browse remote <b>Processes</b>.</li> - <li>Select "My Processes" and choose context menu > <b>Monitor</b>. - <li>Enable polling, choose a short wait time. See processes appear and vanish as you perform commands in a remote shell.</li></ul></li> -</ul> -</div> - -<div> -<p><b class="reltaskshd">Follow-up tasks</b><br/> -<a href="gxtending.html" title="">Extending Remote System Explorer</a><br/> -</p> - -<p><b class="relconceptshd">Related concepts</b><br/> -<a href="../concepts/cbegin.html" title="">Remote System Explorer Connections</a><br/> -<a href="../concepts/cfilters.html" title="">Remote System Explorer filters, filter -pools, and filter pool references</a><br/> -<a href="../concepts/crunremcmds.html" title="">Shells and commands in the -Remote Systems view</a><br/> -</p> -<p><b class="reltaskshd">Related tasks</b><br/> -<a href="../tasks/ttablecopy.html" title="">Copying and pasting in the Remote System Explorer</a><br/> -<a href="../tasks/truncmdsview.html" title="">Running and viewing -commands and shells using the Remote Commands view</a><br/> -<a href="../tasks/twrkcmdshl.html" title="">Working with command shells</a><br/> -<a href="../tasks/tmanagesearch.html" title="">Search for text and files on remote servers</a><br/> -</p> -</div> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/gxtending.html b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/gxtending.html deleted file mode 100644 index 136353105..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/gxtending.html +++ /dev/null @@ -1,45 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> -<meta name="copyright" content="Copyright (c) 2006 Wind River Systems, Inc. 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>Extending Remote System Explorer</title> -</head> -<body id="gxtending"> -<a name="gxtending"><!-- --></a> -<h1 class="topictitle1">Extending Remote System Explorer</h1> -<div> -<p>There are numerous ways how developers and software vendors can extend the -capabilities of the Remote System Explorer. Please look at the -<a href="../../org.eclipse.rse.doc.isv/guide/rse_int_architecture.html">RSE Developer Guide</a> to learn about adding subsystems, -remote property pages or additional popup actions. The developer guide -holds extensive -<a href="../../org.eclipse.rse.doc.isv/guide/tutorials.html">tutorials</a>, -<a href="../../org.eclipse.rse.doc.isv/guide/rse_int_architecture.html">overview documentation</a> and -reference</a>.</p> - -<p>Users can configure and customize the Remote System Explorer through -<!-- TODODeferred -User actions, Compile Commands and ---> -<a href="../ref/rrsepref.html">Preferences</a> and connection setup -<a href="../concepts/cteam.html">shared in a team</a>. -</div> - -<div> -<p><b class="relconceptshd">Related concepts</b><br/> -<a href="../concepts/cfilters.html" title="">Remote System Explorer filters, filter -pools, and filter pool references</a><br/> -<a href="../concepts/cteam.html" title="">Team support</a><br/> -</p> -<!-- -<p><b class="reltaskshd">Related tasks</b><br/> -<a href="../tasks/truncmdsview.html" title="">Running and viewing -commands and shells using the Remote Commands view</a><br/> ---> -</p> -</div> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.user/images/ModelRSE.gif b/rse/doc/org.eclipse.rse.doc.user/images/ModelRSE.gif Binary files differdeleted file mode 100755 index 9426bc1d9..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/images/ModelRSE.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.user/images/RSESample.gif b/rse/doc/org.eclipse.rse.doc.user/images/RSESample.gif Binary files differdeleted file mode 100644 index 4ddb991f3..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/images/RSESample.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.user/images/RSESample_small.gif b/rse/doc/org.eclipse.rse.doc.user/images/RSESample_small.gif Binary files differdeleted file mode 100644 index 9f72e4cd2..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/images/RSESample_small.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.user/images/gsarrow.gif b/rse/doc/org.eclipse.rse.doc.user/images/gsarrow.gif Binary files differdeleted file mode 100755 index c48660dbe..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/images/gsarrow.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.user/images/navigator.jpg b/rse/doc/org.eclipse.rse.doc.user/images/navigator.jpg Binary files differdeleted file mode 100755 index 08ef7717e..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/images/navigator.jpg +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.user/images/newconnection_wiz.gif b/rse/doc/org.eclipse.rse.doc.user/images/newconnection_wiz.gif Binary files differdeleted file mode 100755 index 63f3d1b37..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/images/newconnection_wiz.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.user/images/pw.jpg b/rse/doc/org.eclipse.rse.doc.user/images/pw.jpg Binary files differdeleted file mode 100755 index 8c5a47757..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/images/pw.jpg +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.user/images/search.gif b/rse/doc/org.eclipse.rse.doc.user/images/search.gif Binary files differdeleted file mode 100755 index f0461093c..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/images/search.gif +++ /dev/null diff --git a/rse/doc/org.eclipse.rse.doc.user/notices.html b/rse/doc/org.eclipse.rse.doc.user/notices.html deleted file mode 100755 index 6c70b9c62..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/notices.html +++ /dev/null @@ -1,22 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 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">
- <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
- <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2006.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/plugin.properties b/rse/doc/org.eclipse.rse.doc.user/plugin.properties deleted file mode 100755 index b918b6280..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/plugin.properties +++ /dev/null @@ -1,18 +0,0 @@ -################################################################################ -# Copyright (c) 2006 IBM Corporation and others. All rights reserved. -# This program and the accompanying materials are made available under the terms -# of the Eclipse Public License v1.0 which accompanies this distribution, and is -# available at http://www.eclipse.org/legal/epl-v10.html -# -# Initial Contributors: -# The following IBM employees contributed to the Remote System Explorer -# component that contains this file: David McKnight, Kushal Munir, -# Michael Berger, David Dykstal, Phil Coulthard, Don Yantzi, Eric Simpson, -# Emily Bruner, Mazen Faraj, Adrian Storisteanu, Li Ding, and Kent Hawley. -# -# Contributors: -# {Name} (company) - description of contribution. -################################################################################ - -pluginName = RSE User Guide -providerName = Eclipse.org diff --git a/rse/doc/org.eclipse.rse.doc.user/plugin.xml b/rse/doc/org.eclipse.rse.doc.user/plugin.xml deleted file mode 100755 index 00f2e242f..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/plugin.xml +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!--
-Copyright (c) 2006 IBM Corporation and others. All rights reserved.
-This program and the accompanying materials are made available under the terms
-of the Eclipse Public License v1.0 which accompanies this distribution, and is
-available at http://www.eclipse.org/legal/epl-v10.html
-
-Initial Contributors:
-The following IBM employees contributed to the Remote System Explorer
-component that contains this file: David McKnight, Kushal Munir,
-Michael Berger, David Dykstal, Phil Coulthard, Don Yantzi, Eric Simpson,
-Emily Bruner, Mazen Faraj, Adrian Storisteanu, Li Ding, and Kent Hawley.
-
-Contributors:
-{Name} (company) - description of contribution.
--->
-<plugin>
- <extension point="org.eclipse.help.toc">
- <toc file="toc.xml" primary="true" />
- </extension>
-</plugin>
-
diff --git a/rse/doc/org.eclipse.rse.doc.user/ref/rrsepref.html b/rse/doc/org.eclipse.rse.doc.user/ref/rrsepref.html deleted file mode 100755 index c56274820..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/ref/rrsepref.html +++ /dev/null @@ -1,79 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Accessing Remote System Explorer preferences</title>
-</head>
-<body id="rrsepref">
-<a name="rrsepref"><!-- --></a>
-<h1 class="topictitle1">Accessing Remote System Explorer preferences</h1>
-<div>
-<div class="p">
-<p class="sectiontitle">Purpose</p>
-The Remote System Explorer has settings that
-you can customize in a preference page. The name of the category is
-Remote Systems and it appears
-in the tree view of the Preferences window. </div>
-<div class="p">
-<div class="skipspace">
-<table cellpadding="4" cellspacing="0" summary="" frame="border"
- border="1" rules="all">
- <tbody>
- <tr>
- <td valign="top"><b>Option</b></td>
- <td valign="top"><b>Description</b></td>
- <td valign="top"><b>Default</b></td>
- </tr>
- <tr>
- <td valign="top">Default System Type</td>
- <td valign="top">Defines the default system type that will be used when creating a new connection.</td>
- <td valign="top">none<br/></td>
- </tr>
- <tr>
- <td valign="top">Default user ID for each system type</td>
- <td valign="top">Specifies a default user ID for a non-local system type.
-If you do not set the default user ID at the connection level, then the User
-ID that you specify here will be used. Note: Changing the user ID on the
-Preferences dialog affects all connections and subsystems that inherit it.</td>
- <td valign="top">Off</td>
- </tr>
- <tr>
- <td valign="top">Show connection names prefixed by profile name</td>
- <td valign="top">Select this to display connection names in the
-Remote System Explorer tree view as profile.connection.</td>
- <td valign="top">Off</td>
- </tr>
- <tr>
- <td valign="top">Show filter pools in Remote Systems view</td>
- <td valign="top">Select this to show filter pools when expanding a subsystem.
-When this is not selected, expanding a subsystem will display the filters.</td>
- <td valign="top">Off</td>
- </tr>
- <tr>
- <td valign="top">Show "New Connection" prompt in Remote Systems view</td>
- <td valign="top">The <img src="../images/newconnection_wiz.gif" alt=""/> New
-Connection option is displayed in the Remote Systems view so that you can
-create a new connection.</td>
- <td valign="top">On</td>
- </tr>
- <tr>
- <td valign="top">Re-open Remote Systems view to previous state</td>
- <td valign="top">Select this to automatically open previously expanded
-connections on start-up.</td>
- <td valign="top">On</td>
- </tr>
- <tr>
- <td valign="top">Cascade user actions by profile</td>
- <td valign="top">The <span><b>Work With</b> > <b>User Actions</b></span> menu will cascade according to active profile.</td>
- <td valign="top">Off</td>
- </tr>
- </tbody>
-</table>
-</div>
-</div>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/ref/rsearch.html b/rse/doc/org.eclipse.rse.doc.user/ref/rsearch.html deleted file mode 100755 index 6781c791d..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/ref/rsearch.html +++ /dev/null @@ -1,86 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Using search parameters with special characters</title>
-</head>
-
-<body id="rtablesub"><a name="rtablesub"><!-- --></a>
-<h1 class="topictitle1">Using search parameters with special characters</h1>
-<div>
-<div class="p">You can use special characters such as ?, *, and \, when searching
-for files and strings, based on the following rules.
-</div>
-<div class="p">
-<div class="skipspace">
-<table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all">
-<tbody>
-<tr>
-<td valign="top"><b>Option</b></td>
-<td valign="top"><b>Description</b></td>
-</tr>
-<tr>
-<td valign="top">*</td>
-<td valign="top">Searches all items. </td>
-</tr>
-<tr>
-<td valign="top">abc*</td>
-<td valign="top">Searches for items that begin with the characters abc,
-for example, abcd or abctest.</td>
-</tr>
-<tr>
-<td valign="top">*abc</td>
-<td valign="top">Searches for items ending with the characters abc, for example, dabc or testabc.</td>
-</tr>
-<tr>
-<td valign="top">*b*</td>
-<td valign="top">Searches for items that have the character b anywhere in the name.</td>
-</tr>
-<tr>
-<td valign="top">a*c</td>
-<td valign="top">Searches for items that begin with the character a and end with the character c.</td>
-</tr>
-<tr>
-<td valign="top">"a*"</td>
-<td valign="top">Searches for items within quotation marks that start
-with the character a, for example, "a," "ab," or "ad." Note that when you
-use quotation marks, the specification becomes case sensitive.</td>
-</tr>
-<tr>
-<td valign="top">abc?</td>
-<td valign="top">Searches for four-character items that begin with the
-characters abc and have a single fourth character, for example, abcd.</td>
-</tr>
-<tr>
-<td valign="top">?abc</td><td valign="top">Searches for four-character items that begin with a
-single character and end in abc, for example, dabc.</td>
-</tr>
-<tr>
-<td valign="top">?b?</td>
-<td valign="top">Searches for three-character items that have a b in the middle, for example, abc.</td>
-</tr>
-<tr>
-<td valign="top">a?c</td>
-<td valign="top">Searches for three-character items that have the character a and c with a single character in between.</td>
-</tr>
-<tr>
-<td valign="top">ab?</td>
-<td valign="top">Searches for three-character items that start with ab and end in a third single character, for example, abc.</td>
-</tr>
-<tr>
-<td valign="top">a\* or a\?</td>
-<td valign="top">Searches for characters where the * and ? are interpreted
-literally, for example, a* or a?. The slash represents an escape character.
-To use a slash literally, enter \\.</td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tarchive.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tarchive.html deleted file mode 100755 index b1478acf0..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tarchive.html +++ /dev/null @@ -1,182 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Managing archived files</title>
-</head>
-
-<body id="tarchive"><a name="tarchive"><!-- --></a>
-<h1 class="topictitle1">Managing archived files</h1>
-<div class="p">
-<p>You can work with archived files and folders in the Remote System Explorer.</p>
-<p>Use the Remote Systems view perform the following actions with archived files:
-<ul>
-<li><a href="#tarchive__browse">Browse files in an archive</a></li>
-<li><a href="#tarchive__copy">Copy, paste, and move archives</a></li>
-<li><a href="#tarchive__drag">Drag and drop files between archives</a></li>
-<li><a href="#tarchive__create">Create files and folders within an archive</a></li>
-<li><a href="#tarchive__delete">Delete archives</a></li>
-<li><a href="#tarchive__extract">Extract files from an archive</a></li>
-<li><a href="#tarchive__add">Add files to an archive</a></li>
-<li><a href="#tarchive__search">Search for content within an archive</a></li>
-<li><a href="#tarchive__convert">Convert archives of a different types into one type</a></li>
-</ul>
-</p>
-</div>
-<div class="p">
-<p>Pick from the following:
-<table border="1" frame="hsides" rules="rows" cellpadding="4" cellspacing="0" summary="" class="skipspace">
-<tbody>
-<tr>
-<th align="left" valign="bottom" id="d0e45">Task</th>
-<th align="left" valign="bottom" id="d0e47">Description</th>
-</tr>
-<tr id="tarchive__browse">
-<td align="left" valign="top" id="d0e50" headers="d0e45"><b>Browsing:</b></td>
-<td align="left" valign="top" headers="d0e47 d0e50">To browse and open
-files in an archive, click the plus sign beside the archive to display the
-contents. Continue to expand folders within the archive or double-click any
-file to open it in the default editor. Save files as you normally would and
-they are saved in the archive. In the properties view, note the addition of
-"#archive#" to the path of the file, to indicate how the file exists inside
-the archive.</td>
-</tr>
-<tr id="tarchive__copy">
-<td align="left" valign="top" id="d0e55" headers="d0e45"><b>Copying and pasting:</b></td>
-<td align="left" valign="top" headers="d0e47 d0e55">To copy
-and paste files, or move them from one location to another, right-click a
-file or folder inside an archive and select <b>Copy</b> or <b>Move</b>. (When
-you select <b>Move</b> instead of <b>Copy</b>, you delete the file in the
-original location, to move it to a new one.) Using the window that opens,
-you can paste the item to any archived, or unarchived location by expanding
-the tree-view to any specific location, and clicking <b>OK</b>. Note that
-you can perform this action across different connections as well.</td>
-</tr>
-<tr id="tarchive__drag">
-<td align="left" valign="top" id="d0e75" headers="d0e45"><b>Dragging and dropping:</b></td>
-<td align="left" valign="top" headers="d0e47 d0e75">You can
-drag and drop files between archives, from an archive to an unarchived location,
-or from an unarchived location into an archive. Expand both the original and
-destination locations in the Remote Systems view, click the item you want
-to move, and drag it with your cursor to the new location. Note that you can
-perform this action across different connections as well.</td>
-</tr>
-<tr id="tarchive__create">
-<td align="left" valign="top" id="d0e80" headers="d0e45"><b>Creating:</b></td>
-<td align="left" valign="top" headers="d0e47 d0e80">To create files and
-folders inside an archive, or to create a new archive, right-click any folder
-in the archive, or the root level archive itself, and select:
-<ul>
-<li><b>New > File</b> to create a normal file within the archive. You can
-also select the file type to be an archive, whereby you can create an archive
-inside of an archive.</li>
-<li><b>New > Folder</b> to create a normal folder within the archive. Then
-right-click your virtual folder to create more folders or files.</li>
-</ul>
-</td>
-</tr>
-<tr id="tarchive__delete">
-<td align="left" valign="top" id="d0e94" headers="d0e45"><b>Deleting:</b></td>
-<td align="left" valign="top" headers="d0e47 d0e94">To delete a file
-or folder from inside an archive, simply right-click the item and select <b>Delete</b>,
-or hit the Delete key. </td>
-</tr>
-<tr id="tarchive__extract">
-<td align="left" valign="top" id="d0e102" headers="d0e45"><b>Extracting:</b></td>
-<td align="left" valign="top" headers="d0e47 d0e102">You have two options
-when extracting files. You can either extract to a new folder within your
-current directory (by selecting <a href="#tarchive__extract1"><b>Extract
-to <i>xyz</i></b></a> where <i>xyz</i> is your current directory) or browse
-to a specific extraction directory (by selecting <a href="#tarchive__extract2"><b>Extract
-To . . .</b></a>). You can also select multiple archives and perform the
-same actions.
-<ul>
-<li id="tarchive__extract1"><a name="tarchive__extract1"><!-- --></a>
-To extract the contents of an archive to a new folder within
-your current directory, right-click your archive and select <b>Extract to <i>xyz</i></b> where <i>xyz</i> is
-the name of your current directory. If your archive was named "MyArchive.zip"
-then the extraction will create a new folder within your current directory
-called "MyArchive" and all of the files will be placed in the new folder in
-their proper structure. Click <b>OK</b>. If you want, use the right-click
-menu to rename the new folder.</li>
-<li id="tarchive__extract2"><a name="tarchive__extract2"><!-- --></a>
-To extract the contents of an archive to a location other
-than the current directory, right-click your archive and select <b>Extract
-To</b>.
-<ol>
-<li>A dialog box displays, presenting a tree view of all drives, files, and
-folders defined in the Remote Systems view. Expand any location in the tree
-view to define the directory location where you want to extract the contents
-of your archive. </li>
-<li>(Optional) You can select a directory, and press the <b>Details</b> button
-to see a list of properties for that location. </li>
-<li>(Optional) You can expand <b>New Connection</b> to define a new connection
-to a location where you want to extract the files.</li>
-<li>(Optional) When you extract the contents of an archive to a destination
-directory, the files and directories in the archive are copied directly to
-that destination. You are prompted to overwrite or rename duplicate files
-in the target directory.</li>
-<li>Click <b>OK</b>.</li>
-</ol>
-</li>
-</ul>
-</td></tr><tr id="tarchive__add"><td align="left" valign="top" id="d0e159" headers="d0e45">
-<b>Adding files to an archive:</b></td>
-<td align="left" valign="top" headers="d0e47 d0e159">To
-add files and folder to an archive, select one or more files/folders, right-click,
-and select <b>Add to Archive</b>.
-<ol>
-<li>A dialog box displays, presenting a tree view of all drives, files, and
-folders defined in the Remote Systems view.</li>
-<li>To create a new archive for the selected files and folders
-<ol type="a">
-<li>Expand any location in the tree view to define the location for the new
-archive.</li>
-<li>Specify a name for the archive in the <b>File name</b> field.</li>
-<li>Specify an <b>Archive type</b> from the drop-down list.</li>
-</ol>
-To add files and folders to an <i>existing</i> archive:
-<ol type="a">
-<li>Select the existing archive's parent folder in the tree view.</li>
-<li>Specify a name for the archive in the <b>File name</b> field.</li>
-<li>Specify an <b>Archive type</b> from the drop-down list.</li>
-</ol>
-</li>
-<li>Click <b>OK</b>.</li>
-</ol>
-The selected files/folders are copied to the root directory in the new
-archive location</td>
-</tr>
-<tr id="tarchive__search">
-<td align="left" valign="top" id="d0e208" headers="d0e45">
-<b>Searching for content inside an archive:</b></td>
-<td align="left" valign="top" headers="d0e47 d0e208">
-To search for files within an archive, right-click the archive, select <b>Search</b>,
-and complete the dialog box to specify what kinds of files and folder you
-want to find. Note that if you begin your search on a normal, unarchived directory
-that contains an archive, the default behaviour is <i>not</i> to search the
-archive. You need to explicitly start from the archive itself to search for
-contents within that archive.</td>
-</tr>
-<tr id="tarchive__convert">
-<td align="left" valign="top" id="d0e219" headers="d0e45">
-<b>Converting archives:</b></td>
-<td align="left" valign="top" headers="d0e47 d0e219">To convert
-archives from one type (.zip, .jar, or .tar) to another, select one or more
-archives, right-click, and select <b>Convert</b>. A Convert Archive dialog
-box opens for each archive you selected. In the dialog box, select a new archive
-type from the <b>Archive Type</b> drop-down list to convert the selected archive.
-You can also, optionally, specify a new location and new name for your archive,
-by selecting a location in the tree view and entering a new name in the <b>File
-name</b> field. Click <b>OK</b>.</td>
-</tr>
-</tbody>
-</table>
-</p>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbegindelete.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbegindelete.html deleted file mode 100755 index 0214acfa2..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbegindelete.html +++ /dev/null @@ -1,33 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Deleting a connection</title>
-</head>
-
-<body id="tbegindelete">
-<a name="tbegindelete"><!-- --></a>
-<h1 class="topictitle1">Deleting a connection</h1>
-<div>
-<div class="p">Deleting a connection to a remote server does not delete
-any elements
-on the server. The action deletes your specific configuration for that
-connection,
-including your filters, filter pools, user actions, compile actions,
-saved
-commands, and named types.
-<p>To delete a connection, in the Remote Systems
-view, right-click your connection and select <b>Delete</b>.</p>
-</div>
-</div>
-<div>
-<p><b class="reltaskshd">Related tasks</b><br/>
-<a href="tbegindiscon.html" title="">Disconnecting from a remote server</a><br/>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbegindeleteprofile.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbegindeleteprofile.html deleted file mode 100755 index 7b52d4d2b..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbegindeleteprofile.html +++ /dev/null @@ -1,33 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Deleting a profile</title>
-</head>
-
-<body id="tbegindelete">
-<a name="tbegindelete"></a>
-<h1 class="topictitle1">Deleting a profile</h1>
-<div>
-<div class="p">Deleting a profile does not delete any elements on the
-server. The
-action only deletes your specific configuration (connections, filters,
-and
-user actions) for that profile. To delete a profile:</div>
-<ol>
- <li><span>Click the Menu button <img src="../images/gsarrow.gif" alt=""/> on the toolbar for the Remote Systems view.</span></li>
- <li><span>Select <b>Delete Profile > <i>name of profile</i></b>.</span></li>
- <li><span>Click <b>Yes</b>.</span></li>
-</ol>
-</div>
-<div>
-<p><b class="reltaskshd">Related tasks</b><br/>
-<a href="tbeginsecprofile.html" title="">Creating a second profile</a><br/>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbegindiscon.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbegindiscon.html deleted file mode 100755 index 2b5411d05..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbegindiscon.html +++ /dev/null @@ -1,60 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Disconnecting from a remote server</title>
-</head>
-
-<body id="tbegindiscon">
-<a name="tbegindiscon"></a>
-<h1 class="topictitle1">Disconnecting from a remote server</h1>
-<div>
-<div class="p">To disconnect from a remote server in the Remote Systems
-view, right-click one of the subsystems displayed under your connection
-name
-and select <b>Disconnect</b>, or close the workbench.
-</div>
-<div class="p">
-<p>If you choose to close the workbench in order to disconnect, it
-notifies you of any outstanding communications requests. However, any
-tools
-launched from the workbench that run externally from the Remote System
-Explorer
-communications server, such as an external remote editor, are not
-affected because they
-have their own communication connection.</p>
-<p>You can monitor and change
-the properties of your connection in the Properties view of the Remote
-System
-Explorer perspective. Some values are read-only, and you can change
-others,
-such as the description or the server name. Although each Remote System
-Explorer
-subsystem maintains its own list of properties, three properties
-(connected
-or disconnected, port, and user ID) are shared among all subsystems. If
-you
-change any of these properties in one subsystem, the other subsystems
-reflect
-the change.</p>
-<p>Select a subsystem and check the Properties view to see
-the shared properties for all of your subsystems. For example, the
-Connected
-value is Yes or No for all of your subsystems under one connection. If
-you
-have difficulties connecting and disconnecting from the server, see the
-related link for troubleshooting information.</p>
-</div>
-</div>
-<div>
-<p><b class="reltaskshd">Related tasks</b><br/>
-<a href="tbegindelete.html" title="">Deleting a connection</a><br/>
-<br/>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginenv.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginenv.html deleted file mode 100755 index 3789823fb..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginenv.html +++ /dev/null @@ -1,67 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Configuring environment variable support for connections</title>
-</head>
-
-<body id="tbeginenv">
-<a name="tbeginenv"></a>
-<h1 class="topictitle1">Configuring environment variable support for connections</h1>
-<div>
-<p>Environment variables are set for the remote job process
-when you first connect to a remote system. This means that the results
-of setting the variables are shown in the Commands view.
-If the system type you are using is case sensitive (UNIX for example),
-then the environment variables will also be case sensitive. Spaces and
-equals signs (=) are only allowed in the value for the environment
-variable, not in
-its name.</p>
-<p>You can define environment variables for all Remote System Explorer
-connection types that support them (Windows, Linux, UNIX, and other
-system types that are installed).</p>
-<p>If you change an environment variable while the Remote System
-Explorer is connected to a
-remote server, the change does not take affect until you disconnect and
-reconnect.</p>
-<p>Although environment variables are set in subsystem properties
-pages, the Remote System Explorer stores
-them globally by connection.</p>
-<p>If you need to specify different environment variables or user IDs
-for a particular remote system, you can do so by defining multiple
-connections to that
-remote system and then defining the environment variables on the file
-subsystem for each
-connection.</p>
-<p>To configure environment variables:
-</p>
-<ol>
- <li><span>Create a connection to a server if necessary.</span></li>
- <li><span>Expand your connection name in the Remote Systems view.</span></li>
- <li><span>Right-click on a file subsystem and select <b>Properties</b>.</span></li>
- <li><span>Click <b>Environment Variables</b> and configure the variables as needed.</span>
- <ul>
- <li>To add an environment variable, click <b>Add</b>. Enter a
-name and value for this variable, and click<b>OK</b>.</li>
- <li>To change an environment variable, select the variable in the
-table and modify the name or value directly. To use a dialog box,
-select the variable and click <b>Change</b>. The name and value of the
-current variable
-are pre-filled in the dialog box. Overwrite whichever field you want to
-change and click <b>OK</b>.</li>
- <li>To remove a variable, click the variable to select it and
-click <b>Remove</b>.</li>
- <li>To move a variable up in the list, click the variable to
-select it and click <b>Move up</b>.</li>
- <li>To move a variable down in the list, click the variable to
-select it and click <b>Move down</b>.</li>
- </ul>
- </li>
-</ol>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginlinux.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginlinux.html deleted file mode 100755 index 26551230a..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginlinux.html +++ /dev/null @@ -1,178 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> - -<head> -<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> -<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Connecting to a remote Linux or UNIX server</title> -</head> - -<body id="tbeginlinux"> -<a name="tbeginlinux"><!-- --></a> -<h1 class="topictitle1">Connecting to a remote Linux or UNIX server</h1> -<p>The following documentation explains how to install the Linux or UNIX server -code, start the server daemon, and make a connection to a remote Linux -or UNIX server. Look <a href="tbeginwindows.html">here</a> for setting up -a server on <a href="tbeginwindows.html">Windows</a>.</p> -<div> -<div class="p"> -<p><b>Prerequisites</b></p> -<p>To use the Remote System Explorer communications server daemon you need -to install Perl. Using the daemon helps eliminate some of the manual steps -when you connect to the server.</p> -<p><b>Installing the server code</b></p> -<div class="p"> -<ol> -<li> -Find the package that contains the server. -The server code is usually packaged with the containing product and you should refer to that -product's documentation for finding and installing the server package. -The server is also available, however, on the Eclipse DSDP -<a href="http://download.eclipse.org/dsdp/tm/downloads/">Target Management download site</a> -as the package <b>rseserver-<version>-<os>.tar</b>. For example, rseserver-1.0-linux.tar contains the release 1.0 server -for Linux. There are servers for Linux, AIX, a generic Unix version that can be tailored to your particular flavor -of Unix, and an experimental Mac OS X version.</li> -<li>Ensure that Perl is installed.</li> -<li>Ensure that a Java Runtime Environment (JRE) version 1.4 or higher is installed. -An IBM, Sun or equivalent JRE is required; The gcj-based jvm shipped with most Linux -distributions does not work. If in doubt, run the command <br/><tt>java -version</tt> (see -below) and check if there is a reference to gcj. You can download a Sun JRE from -<a href="http://java.sun.com">http://java.sun.com</a>.</li> -<li>Create a directory where you want to install the server code. The remainder -of these instructions will assume the directory /opt/rseserver (suitable for -team sharing), but you are free to use any directory.</li> -<li>Upload the server package to this directory. You can use FTP.</li> -<li>Switch to the /opt/rseserver directory by typing: -<pre>cd /opt/rseserver</pre> -</li> -<li>Run the following command in the /opt/rseserver directory to extract the -server code from the package appropriate to your operating system. For linux this command is: -<pre>tar -xf rseserver-1.0-linux.tar</pre> -</li> -</ol> -</div> - -<p><b>Starting the server</b></p> -<div class="p">You can start the RSE communications -server with the server daemon, or manually. Before starting the server, make -sure the Java command is in your path, you can do this by running the following -command:<pre>java -version</pre> -</div> -<div class="p">You should see something -similar to the following:<pre>java version "1.4.1" -Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1) -Classic VM (build 1.4.1, J2RE 1.4.1 IBM build cxppc321411-20040301 (JIT enabled: jitc))</pre> -</div> -<div class="p">If -you receive a "command not found" error, then try creating a symbolic link -to the java command in /usr/bin by running the following command:<pre>ln -s /opt/IBMJava2-141/jre/bin/java /usr/bin/java</pre> -</div> -<div class="p"><b>To start the server with the server daemon</b> -<ol> -<li>Ensure that you are running using the root user ID. (If the daemon is -not run under root, it will be unable to authenticate connecting users.) Run -the following commands:<pre>su -l root -cd /opt/rseserver -perl ./daemon.pl [daemonPort] [serverPortRange]</pre> -</li> -</ol> -Note that the server daemon runs on port 4035 by default. You can pass the optional -daemonPort argument to force a different port if you want.<br/> -If your daemon runs behind a firewall, you may want to specify the optional -<i>serverPortRange</i> argument to restrict selected server ports to the -range given:<pre> -perl ./daemon.pl 4035 10000-10010</pre> - -<p><b>To start the server manually</b></p> -<div class="p">If you do not have root access on a remote machine, you can -start the server manually for your particular user id only. Run -the following commands:<pre>cd /opt/rseserver -perl ./server.pl [port]</pre> -These commands run the server.pl -script located in the /opt/rseserver directory. The port parameter to the server.pl script is -optional. If you do not specify a port, then the server will pick the first -one available and print the port number to standard out. By default, it is -usually 4033. If you would like to use a different port, you will then have -to enter this port number in port property for the Files subsystem for your -connection in the Remote System Explorer (see <span class="uicontrol">Connecting to the -Remote Server</span>, below). Otherwise, you do not need to change this -property.</div> -<div class="p"><div class="note"> -Note: When you connect RSE to the server, the server will terminate as -soon as you disconnect the client. The daemon, however, will not terminate. -</div></div> - -<p><b>Rexec Server Launcher</b></p> -<div class="p">If you have Rexec access enabled to your remote system, you -can also have the server started automatically by an Rexec command from the -client, when you connect. To do so, use the Server Launcher Properties in -the New Connection Wizard. -</div> -<p><b>Running the daemon at startup</b></p> -<div class="p">You might instead want -to configure the daemon to run at start up for Linux. To do so, you need to -append a call to the daemon to your startup script. Add the following lines -to the bottom of the /etc/rc.d/rc.local file:<pre>cd /opt/rseserver -perl ./daemon.pl &</pre> -</div> -<p><b>SSL Encryption and Firewalls</b></p> -<div class="p">By default the RSE Dstore connection is unencrypted. You -can, however, configure it to use SSL encryption. -<p>Because all dstore data transfer is done through a single TCP/IP -connection, the connection can also be tunneled through an ssh channel. -In fact, the same ssh channel can also be used to start the server, -like in the following example: -<pre> -ssh -l moberhuber build.eclipse.org -L27127:build.eclipse.org:27127 \ - "sh -c 'cd ~/rseserver/latest; perl ./server.pl 27127'" -</pre> -Here, the RSE Server is started on port 27127 through an ssh connection, -and at the same time port 27127 is forwarded through ssh to the local -host. You can now connect RSE to localhost:27127, and the connection -will transparently be forwarded to the remote system. -</div> -</div> -</div><br></br> -<p><b>Connecting to the Remote Server</b></p> -<div class="p">To make a connection -to your remote server:</div> -<ol> - <li><span>Switch to the Remote System Explorer perspective. From the workbench -menu, click <span class="menucascade"><span class="uicontrol">Window </span> > <span class="uicontrol">Open Perspective </span> > <span class="uicontrol">Remote System Explorer</span></span>.</span></li> - <li><span>In the Remote Systems view, <b>New Connection</b> is automatically -expanded to show the various remote systems you can connect to through the -Remote System Explorer. Expand <b>Linux</b> or <b>Unix</b> to -invoke the new connection dialog box and configure a connection.</span></li> - <li><span>Enter a name for your first profile and click <b>Next</b>. (This -step only occurs if you have never defined a connection before.)</span></li> - <li><span>Enter a connection name. This name displays in your tree view and -must be unique to the profile.</span></li> - <li><span>Enter the name or TCP/IP address of your Linux server in the <b>Host -name</b> field, for example, LINUX_A.</span></li> - <li><span>(Optional) Enter a <b>Description</b>. The description appears -in the Properties view after the connection is created.</span></li> - <li><span>Click <b>Finish</b> to define your system. </span></li> -</ol> -<div class="skipspace"> -<div class="attention"><span class="attentiontitle">Attention: </span>To check your port number, right-click your -connection or subsystem from the Remote Systems view and select <b>Properties</b>. -Click <b>Subsystem</b> to view the relevant information. If your port is "0," -then your Remote System Explorer communications server will pick any free -port on the server. If you specified a port number when starting the server, -you need to enter it here, for example, to work with a firewall.</div> -</div> -<div class="p"> -<div class="note"></div> -</div> -</div> -<div> -<p><b class="reltaskshd">Related tasks</b> -<a href="tbeginwindows.html" title="">Connecting to a remote Windows -server</a> -<!-- TODO SSL configuration --> -</p> -</div> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginpass.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginpass.html deleted file mode 100755 index b8ac794f4..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginpass.html +++ /dev/null @@ -1,52 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Saving passwords on your local PC</title>
-</head>
-
-<body>
-<h1>Saving passwords for remote systems</h1>
-<p>When you use the Remote System Explorer,
-you can save passwords for remote systems
-on your local PC. The stored passwords are
-then retrieved whenever a password is required
-to connect. When you save your password for
-a particular remote system, you will not
-be prompted to sign on when you try to connect
-to that system. </p>
-<p>When you first try to connect to a remote
-system, you will be prompted with the following
-dialog:</p>
-<img src="../images/pw.jpg"></img>
-<p>To save this password on your local PC:</p>
-<ol>
- <li>Enter your user ID</li>
- <li>Enter your password</li>
- <li>Select <b>Save user ID</b></li>
- <li>Select <b>Save password</b></li>
-</ol>
-<p>The next time that you connect to the remote
-system, you will not be prompted to sign
-on again.</p>
-<p><b>Note</b>: If you still want to be prompted for your
-user ID and password, right-click on the
-subsystem and select <b>Connect</b>. </p>
-<h2>Adding, changing, and removing stored passwords</h2>
-<p>You can use the password information page
-to add, change, and remove stored passwords
-for remote systems:</p>
-<ol>
- <li>Select <b>Window</b> -> <b>Preferences</b></li>
- <li>Expand <b>Remote Systems</b></li>
- <li>Select <b>Passwords</b></li>
-</ol>
-<p>Use the Add, Change, and Remove buttons to
-manage your password information for remote
-systems. </p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginsecond.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginsecond.html deleted file mode 100755 index df4b86dd0..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginsecond.html +++ /dev/null @@ -1,36 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Creating a second connection to a remote server</title>
-</head>
-
-<body id="tbeginsecond"><a name="tbeginsecond"></a>
-<h1 class="topictitle1">Creating a second connection to a remote server</h1>
-<div class="p">
-<p>In the Remote System Explorer, you can create a second connection
-to the same, or a different type of server, such as Linux, UNIX, or Windows.
-You can also create a second connection to the same server with a separate job
-environment, for example, to specify different environment variables or different user IDs.</p>
-To create a second connection:
-</div>
-<div>
-<ol>
-<li><span>In the Remote Systems view, expand <b>New Connection</b>.</span></li>
-<li><span>Click the plus sign beside the type of server you to which you want to make a second connection. For example, Linux, UNIX, or Windows.</span></li>
-<li><span>Complete the dialog as you normally would, making sure that you give your new connection a unique name.</span></li>
-</ol>
-</div>
-<div>
-<p><b class="reltaskshd">Related tasks</b><br />
-<a href="tbeginenv.html" title="">Configuring environment variable support for connections</a><br/>
-<a href="tbeginwindows.html" title="">Connecting to a remote Windows server</a><br/>
-<a href="tbeginlinux.html" title="">Connecting to a remote Linux or UNIX server</a><br/>
-</p>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginsecprofile.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginsecprofile.html deleted file mode 100755 index 06de9db68..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginsecprofile.html +++ /dev/null @@ -1,27 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Creating a second profile</title>
-</head>
-
-<body id="tbeginsecprofile">
-<a name="tbeginsecprofile"></a>
-<h1 class="topictitle1">Creating a second profile</h1>
-<p>You might want to create a second profile for connections and data that belong to a particular version of a software release, and are
-shared by all team members.</p>
-<p>To create a second profile:
-<ol>
-<li>Click the Menu button <img src="../images/gsarrow.gif" alt=""/> on the toolbar for the Remote Systems view and select <b>New profile</b>.</li>
-<li>Specify a name for the new profile and click <b>Finish</b>.</li>
-</ol>
-</p>
-<p><b class="reltaskshd">Related tasks</b><br/>
-<a href="tbegindeleteprofile.html" title="">Deleting a profile</a><br/>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginwindows.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginwindows.html deleted file mode 100755 index 1e2f7be46..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginwindows.html +++ /dev/null @@ -1,123 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> - -<head> -<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> -<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Connecting to a remote Windows server</title> -</head> - -<body id="tbeginlinux"> -<a name="tbeginlinux"></a> -<h1 class="topictitle1">Connecting to a remote Windows server</h1> -<div> -<p>The following documentation explains how to install the Windows server -code, start the server daemon, and make a connection to a remote Windows -server. Look <a href="tbeginlinux.html">here</a> for setting up -a server on <a href="tbeginlinux.html">Linux, General UNIX or Mac</a>, -and additional configuration options.</p> -<div class="p"> -<p><b>Installing the server code</b></p> -<div class="p"> -<ol> -<li> -Create a directory where you want to install the server code. The -remainder of these instructions will assume the directory name and location is -C:\rseserver, but you are free to use any directory you choose.</li> -<li>Find the package that contains the server. -The server code is usually packaged with a containing product and you should refer to that -product's documentation for finding and installing the server package. -The server is also available, however, on the Eclipse DSDP -<a href="http://download.eclipse.org/dsdp/tm/downloads/">Target Management download site</a> -as the package <b>rseserver-<version>-<os>.zip</b>. For example, rseserver-1.0-windows.zip contains the release 1.0 server -for Windows.</li> -<li>Copy the rseserver.zip to the C:\rseserver directory (this could be on a different machine).</li> -<li>Using an unzip utility to extract the server code to the C:\rseserver directory.</li> -</ol> -</div> -<p><b>Starting the server</b></p> -<p>You can start the RSE communications server with the server manually, or with a daemon.</p> - -<div class="p"><b>To start the server with a the server daemon:</b> -<ol> -<li>Simply double click the <code>daemon.bat</code> program to start a server daemon.</li> -<li>You can edit the <code>daemon.bat</code> file to change properties for the daemon, -like a specific daemon port to use or to force a port range for the server -(in order to comply with firewalls).</li> -</ol> -<blockquote> -<p>Note that the server daemon <b>does not</b> enforce any user -authentication. If you run the server daemon, any user can connect to the machine, work -with the file system and run commands. -<span style="font-weight: bold;">Use of the server daemon on Windows systems is not recommended</span>. -</p> -The server daemon runs on port 4035 by default. You can pass the optional -daemonPort argument to force a different port if you want.<br/> -If your daemon runs behind a firewall, you may want to specify the optional -<i>serverPortRange</i> argument to restrict selected server ports to the -range given:<pre> -daemon.bat 4035 10000-10010</pre> -</blockquote> -</div> - -<div class="p"><b>To start the server manually:</b> -<ol> -<li>Simply double click on the <code>server.bat</code> program to start a -dstore server. The server will pick the first port available and print -the port number. By default, it is usually 4033. -You will then have to enter this port number in port property for the -Files subsystem for your connection in the Remote System Explorer.</li> -<li>For security reasons, the server will only wait a limited time -until a client connects (12000 seconds by default).</li> -<li>In order to start the server with an exactly specified port or -timeout, open a Windows command prompt and enter: -<pre> -c:<br/> -cd \rseserver<br/> -server.bat [port] [timeout] -</pre> -</li> -<li>When you connect RSE to the server, the server will terminate as soon as you -disconnect the client. The daemon, however, will not terminate.</li> -</ol> -</div> -</div> - -<div class="p"><b>To connect to a remote Windows server:</b> -<ol> -<li><span>Switch to the Remote System Explorer perspective.</span></li> -<li><span>In the Remote Systems view, <b>New Connection</b> is -automatically be expanded to show the various remote systems you can connect to -through the Remote System Explorer. Expand <b>Windows</b> to invoke a dialog -and configure a connection.</span></li> -<li><span>Enter a name for your first profile and click <b>Next</b>. -(This step only occurs if you have never defined a connection before.)</span></li> -<li><span>Enter a connection name. This name displays in your tree -view and must be unique to the profile.</span></li> -<li><span>Enter the name or TCP/IP address of your Windows server in -the <b>Host Name</b> field, for example, jsandler.</span></li> -<li><span>Enter a <b>Description</b>(optional); the description -appears in the Properties view after the connection is created.</span></li> -<li><span>Click <b>Finish</b> to define your system. </span></li> -</ol> -</div> - -<div class="p"> -<div class="note"><span class="notetitle">Note: </span>To check your -port number, right-click your connection or subsystem -from the Remote Systems view and select <b>Properties</b>. Click <b>Subsystem</b> -to see the relevant information. If your port is "0," then your Remote -System Explorer communications server will pick any free port on the Windows -server. If you specified a port number when starting the server, you need to -enter it here, for example, to work with a firewall.</div> -</div> -</div> -<div> -<p><b class="reltaskshd">Related tasks</b><br/> -<a href="tbeginlinux.html" title="">Connecting to a remote Linux or UNIX server</a><br/> -</p> -</div> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbuild.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbuild.html deleted file mode 100755 index 080588f99..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbuild.html +++ /dev/null @@ -1,40 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Exporting resources to a remote file system</title>
-</head>
-
-<body id="tremoexp"><a name="tremoexp"><!-- --></a>
-<h1 class="topictitle1">Building programs on a remote system</h1>
-<div>
-<p>A configuration in the External Tools dialog lets you build programs on remote systems.</p>
-<div class="p">To build programs on a remote system:</div>
-<ol>
-<li><span>Select <span><b>Run</b> > <b>External Tools</b> > <b>External Tools</b></span> from the workbench menu bar. The External Tools dialog opens.</span></li>
-<li><span>Right click on <b>Remote Build</b> and select <b>New</b>. A remote build configuration is created.</span></li>
-<li><span>Choose the connection for the remote system or create a new one.</span></li>
-<li><span>Type the build command or browse the file system to find the build command</span></li>
-<li><span>Type or select the working directory. This is the directory where the command will be run.</span></li>
-<li><span>Enter the arguments to the build command.</span></li>
-<li><strong>Optional: </strong><span>Select the checkbox to specify that there is an associated project with this
-build command. If the command operates on a set of remote files (for example, a command such as 'make'), the Remote System
-Explorer will interpret any errors or other messages and allow you to double click on them to open the source.
-Specifying this option means the Remote System Explorer will open the source from a local project (that is, it will
-not open the remote source). This is useful if you are developing a program from a local project.</span></li>
-<li><strong>Optional: </strong><span>Select the checkbox to specify that local files should be exported before the
-build command is executed. This is useful if you are developing your remote application from a local project. In such
-cases, you would export the files from the workspace to the remote system using the <b>Remote file system</b> export wizard.
-That wizard lets you save the settings of the export to a file. The settings file contains information about which
-files were exported and various export options. You can specify this settings file here. This configuration will use
-the settings file to do the export and when the export is completed it will execute the build command. This ensures
-that the local source you are working on is always sent to the remote system before the build takes place.</span></li>
-<li><span>Click on <b>Apply</b> to save the configuration. Click on <b>Run</b> to execute it.</span></li>
-</ol>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tedittype.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tedittype.html deleted file mode 100755 index a06b55d08..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tedittype.html +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Editing an existing type</title>
-</head>
-
-<body id="tedittype"><a name="tedittype"><!-- --></a>
-<h1 class="topictitle1">Editing an existing type</h1>
-<div>
-<div class="p">To edit an existing type: </div>
-<ol>
-<li><span>In the Remote Systems view, right-click on a file subsystem, and select <span><b>Work With </b> > <b>Named
-Types</b></span>.</span></li>
-<li><span>On the Work With Named Types window, expand <b>Object </b> or <b>Member</b>.</span></li>
-<li><span>Select your defined type from the list. You cannot edit any IBM-supplied types.</span></li>
-<li><span>Make the required changes.</span></li>
-<li><span>Click <b>Apply</b>.</span></li>
-</ol>
-</div>
-<div>
-<p><b class="relconceptshd">Related concepts</b><br />
-<a href="../concepts/cuseractions.html" title="">User actions (user options)</a><br />
-</p>
-<p><b class="reltaskshd">Related tasks</b><br />
-<a href="tremtype.html" title="">Removing an existing type</a><br />
-</p>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagedel.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagedel.html deleted file mode 100755 index 6d62b018f..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagedel.html +++ /dev/null @@ -1,29 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2003, 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>Deleting filters in the Remote Systems view</title>
-</head>
-
-<body>
-<a name="tmanagedel"></a>
-<h1 class="topictitle1">Deleting filters</h1>
-<div>
-<div class="p">Deleting a filter does not delete any elements that you
-managed with
-that filter. The action only deletes your specific configuration for
-that
-filter. To delete a filter:</div>
-<ol>
- <li><span>In the Remote Systems view, expand your connection, and
-then expand <b>Files</b>. </span></li>
- <li><span>Right-click your filer and select <b>Delete</b>.</span>
- </li>
-</ol>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanageedit.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tmanageedit.html deleted file mode 100755 index ad2cc1dc5..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanageedit.html +++ /dev/null @@ -1,42 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2003, 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>Changing filters</title>
-</head>
-
-<body>
-<a name="tmanageedit"></a>
-<h1 class="topictitle1">Changing filters</h1>
-<div>
-<div class="p">You can change a filter if you want to alter
-the host items that it displays in the Remote
-Systems view. When you change a filter, you
-can also add extra conditions to what is
-filtered. For example, if you have a filter
-that displays all files of type *.c, you
-may also want to add an additional filter string that
-will display files of type *.h also. To change
-a filter:</div>
-<ol>
-<li><span>In the Remote Systems view, expand your connection name,
-and then expand <b>Files</b> to see a list of filters.</span></li>
-<li><span>Right-click the filter and select <b>Change</b>.</span></li>
-<li><span>In the pop-up window, edit the conditions that are filtered
-and click <b>Apply</b>.</span>
-<ul>
-<li>If you want to add extra conditions, as described in the
-introduction to this topic, click <b>New filter string</b> and complete the dialog.
-Click <b>Create</b>.</li>
-</ul>
-</li>
-<li><span>Click <b>OK</b>.</span></li>
-</ol>
-<div class="p"></div>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagemem.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagemem.html deleted file mode 100755 index fbafbb5ea..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagemem.html +++ /dev/null @@ -1,32 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2003, 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>Creating file filters</title>
-</head>
-
-<body>
-<h1>Creating file filters</h1>
-<p>File filters list a set of files and folders from your host in the Remote Systems view.</p>
-<ol>
-<li>In the Remote Systems view, expand your connection and then expand <b>Files</b>.</li>
-<li>Right-click <b>Files</b>, or your filter pool, and select <b>New</b> > <b>Filter</b>.</li>
-<li>Browse, specify, or select from the <b>Fold</b> drop-down list the folder that contains the appropriate files and folders.</li>
-<li>Enter a generic or specific file name in the <b>File name filter</b> field. The default is * (asterisk). You can, for example, enter s* to list all files that start with s.</li>
-<li>(Optional) To select a specific file type, enter the type in the <b>File types</b> field, or click <b>Select</b> to select from all known file types.</li>
-<li>Use the <b>Show files only</b> check box to select whether you want to list only files.</li>
-<li>Click <b>Next</b>.</li>
-<li>Enter a name for your filter and select the profile that you want to use. Use an individually created profile to keep your work private, or select the Team profile to share with others.</li>
-<p>Note: Filters are named so that the Remote System Explorer can save them for future use.</p>
-<li>Click <b>Next </b>to see more text information about the filter or click <b>Finish</b>.</li>
-</ol>
-Your new file filter is displayed in the Remote Systems view under Files.
-<p><b>Related tasks</b><br/>
-<a href="tmanageedit.html">Changing filters</a><br/>
-<a href="tmanagepools.html">Configuring filter pools</a></p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagepools.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagepools.html deleted file mode 100755 index 4b4e1a1c9..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagepools.html +++ /dev/null @@ -1,73 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Configuring filter pools</title>
-</head>
-
-<body id="tmanagepools">
-<a name="tmanagepools"></a>
-<h1 class="topictitle1">Configuring filter pools</h1>
-<div>
-<div class="p">
-<p>If you have been using the Remote System Explorer for some
-time, your workspace might contain too many filters to navigate easily.
-Or,
-you might just want to keep groups of filters separate if, for example,
-you
-need to represent two distinct server environments in the Remote System
-Explorer,
-regardless of how many filters you have. In either case, you can group
-filters
-into <i>filter pools</i>. </p>
-<p>All filters live in filter pools, but these remain hidden unless you choose
-to manage them explicitly. If you do not manage them yourself the Remote
-System Explorer manages them for you and all of your filters appear together
-in all connections. When you create filter pools, however, any filter you
-create within that filter pool is only present in connections that reference
-that filter pool, and will not appear in any other connections. (See the
-related links for more information about filter pools.)</p>
-To illustrate the
-use of filter pools,</div>
-<ol>
- <li><span>Click the menu button <img src="../images/gsarrow.gif" alt=""/> on
-the toolbar for the Remote Systems view, and select <b>Show Filter
-Pools</b>.</span></li>
- <li><span>Expand the <span style="font-weight: bold;">Local </span>system
-and the <span style="font-weight: bold;">Local Files</span> subsystem,
-and you can now see your filters
-listed under <b><i>Connection name</i> Filter Pool</b>.</span></li>
- <li><span>Right-click <b>Local Files</b> and select <b>New >
-Filter Pool</b>.</span></li>
- <li><span>Enter a pool name and click <b>Finish</b>. (You do not
-need to
-change your profile selection.) Your new filter pool displays
-underneath your
-connection.</span></li>
- <li><span>Right-click your new filter pool and select <b>New >
-Filter</b><b></b>.</span></li>
- <li><span>Complete the wizards as you normally would (see related
-tasks).
-When you are finished, you can see your new filters displayed in your
-new filter pool.</span></li>
-</ol>
-<div class="p">If you decide not to see the filter pools anymore, click
-the menu
-button <img src="../images/gsarrow.gif" alt=""/> on the toolbar for the
-Remote
-Systems view, and select <b>Show Filter Pools</b> again to deselect
-the check
-mark.</div>
-</div>
-<div>
-<p><b class="relconceptshd">Related concepts</b><br></br>
-<a href="../concepts/cfilters.html" title="">Remote System Explorer
-filters, filter pools, and filter pool references</a><br></br>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagepoolsref.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagepoolsref.html deleted file mode 100755 index 052d38fcc..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagepoolsref.html +++ /dev/null @@ -1,57 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Configuring filter pool references</title>
-</head>
-
-<body id="tmanagepools"><a name="tmanagepools"><!-- --></a>
-<h1 class="topictitle1">Configuring filter pool references</h1>
-<div>
-<div class="p">
-<p>You can share filter pools among many connections through
-the use of a <i>filter pool reference</i>. A filter pool reference is a mechanism
-that displays a filter pool from one connection in any other connection, so
-that when you make a change to the original filter pool, your change is reflected
-your filter pool reference.</p>
-<div class="p">Before
-you create a filter pool reference, ensure that you have already completed
-the following (see related tasks for more information):
-<ul>
-<li>You have defined more than one connection to the same server</li>
-<li>You have defined more than one filter pool</li>
-<li>You have enabled <b>Show Filter Pools</b> from the Remote Systems view toolbar</li>
-</ul>
-</div>
-<p>To use filter pools references:</p>
-<ol>
-<li><span>In the Remote Systems view, expand the connection where you want
-to display a filter pool that exists in another connection.</span></li>
-<li><span>Right-click on a file subsystem and select <b>New > Filter Pool
-Reference > <i>your profile</i> > <i>name of pool</i></b>.</span></li>
-<li><span>Look under that subsystem again and you will see the filter
-pool reference.</span></li>
-</ol>
-<div class="p">To delete a filter pool reference, right-click it and select <b>Remove
-reference</b>. You can also move your filter pools up and down with the
-right-click menu.
-</div>
-</div>
-<div>
-<p>
-<b class="relconceptshd">Related concepts</b><br />
-<a href="../concepts/cfilters.html" title="">Remote System Explorer filters, filter pools, and filter pool references</a><br />
-</p>
-<p>
-<b class="reltaskshd">Related tasks</b><br />
-<a href="tmanagepools.html" title="">Configuring filter pools</a><br />
-<a href="tbeginsecond.html" title="">Creating a second connection to a remote server</a><br />
-</p>
-</div>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagesearch.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagesearch.html deleted file mode 100755 index ce85912fc..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tmanagesearch.html +++ /dev/null @@ -1,94 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Search for text and files on remote servers</title>
-</head>
-
-<body id="tmanagesearch"><a name="tmanagesearch"><!-- --></a>
-<h1 class="topictitle1">Search for text and files on remote servers</h1>
-<div>
-<p>You can search for text strings and files on any remote server
-or file system, including Linux, UNIX, and Windows systems.</p>
-<div class="p">There are three main ways you can search for files and text strings
-on remote servers, depending on your goal:
-<ul>
-<li>Search for text strings within a file</li>
-<li>Search for text strings and/or files within a folder</li>
-<li>Search for text strings, files, and/or folders within a remote file system</li>
-</ul>
-To search for files, text strings, and folders:
-<ol>
-<li>In the Remote Systems view, expand your iSeries, Linux, UNIX, or Windows
-connection until you reach the folder, file, or file system that you want
-to search. Select the containing item by clicking on the item.</li>
-<li>Right-click and select <b>Search</b>. Or, click <b>Search > Remote</b> from
-the workbench menu. Or, for the keyboard shortcut, enter CTRL+H. All of these
-actions will invoke the Search window. </li>
-<li>In the Remote Search window, click the Remote Search tab if it is not
-already in focus. You can now search for text strings, files, and/or folders,
-with the option to use powerful Regular Expressions, in addition normal and
-variable expressions, such as a*b. See <a href="../ref/rsearch.html">Using
-search parameters with special characters</a> for more information. Regular
-Expressions might be most familiar to Linux and Unix users.
-For more information on Regular Expressions, see
-<a href="http://www.english.uga.edu/humcomp/perl/regex2a.html" target="_blank">http://www.english.uga.edu/humcomp/perl/regex2a.html.</a>
-<ul>
-<li>To search for strings, in the <b>Search string</b> field, enter the string
-that you want to search for, whether it be from a file, a folder, or an entire
-file system. Select the <b>Case sensitive</b> or <b>Regular expression</b> check
-boxes if they apply. Leave this field as an asterisk (*) if you do not want
-to search for strings. You can use commas to specify more than one type of
-string to search for. For example, you could enter "*.c, *.java, b?a.txt,
-" and so on.</li>
-<li>To search for files, in the <b>File name patterns</b> field, enter the
-name of the file you are looking for. Check the <b>Regular expression</b> check
-box if this option applies. Leave this field as an asterisk (*) if you do
-not want to search for files. You can use commas to specify more than one
-type of folder to search for. You can also click <b>Browse</b> to select file
-extensions to search for.</li>
-</ul>
-<div class="note"><span class="notetitle">Note: </span>
-You cannot edit the contents of the <b>Folder</b> field; however,
-you can click the <b>Browse</b> button to browse to and specify another folder.
-If the <b>Folder</b> field is empty, you need to browse to a particular folder
-before you can launch the search.
-</div>
-</li>
-<li>Click <b>Search</b>.</li>
-</ol>
-The matching strings and/or files display in the Remote Search view.
-The view updates itself as more matches are found and you can click the <b>Stop</b> button
-if you want to stop the search process. The view shows the strings and/or
-files that you searched for, with the matches listed beneath in a tree-view
-structure. For example, if you searched the file "README.txt" for the following
-string, "*bin*", then the Remote Search results view might look like this:
-<p><br /><img src="../images/search.gif" alt="" /><br /></p>
-<div class="p">To manipulate the set
-of search results:
-<ul>
-<li>Right-click the parent items of the tree, in this example, "README.txt",
-and you can select any of the regular Remote Systems options, for example, <b>Open
-With</b>, <b>Rename</b>, <b>Properties</b>, and so on.</li>
-<li>Right-click any line beneath the parent search item in the tree, in this
-example, "bin/rmid and jre/bin/rmid":
-<ul>
-<li>Select <b>Copy</b> to copy the path as you see it to your clipboard.</li>
-<li>Select <b>Go to</b> to open the file in an editor, which highlights the matching text. You can double-click on any line to perform the same action.</li>
-</ul>
-</li>
-</ul>
-</div>
-</div>
-</div>
-<div>
-<p><b class="relrefhd">Related reference</b><br />
-<a href="../ref/rsearch.html" title="">Using search parameters with special characters</a><br />
-</p>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tremoexp.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tremoexp.html deleted file mode 100755 index 1204d7e90..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tremoexp.html +++ /dev/null @@ -1,45 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Exporting resources to a remote file system</title>
-</head>
-
-<body id="tremoexp"><a name="tremoexp"><!-- --></a>
-<h1 class="topictitle1">Exporting resources to a remote file system</h1>
-<div>
-<p>A page in the Export wizard enables you to export resources from the workspace to a remote file system.</p>
-<div class="p">To export resources from the workspace:</div>
-<ol>
-<li><span>Select <span><b>File</b> > <b>Export</b></span> from the workbench menu bar. The Export wizard opens.</span></li>
-<li><span>Select <b>Remote file system</b>. Click <b>Next</b>.
-The Remote file system page opens.</span></li>
-<li><span>Use the left and right panes to select resources to export. Choose
-individual resources from the right pane, or entire folders from the left
-one.</span></li>
-<li><span>In the <b>Folder</b> field, select or browse for
-the destination folder.</span></li>
-<li><strong>Optional: </strong><span>Select the check box to overwrite (without
-prompting) files of the same name in the remote folder.</span></li>
-<li><span>Select one of the radio buttons to either replicate the workspace
-folder structure in the remote system or create only the actual folders you
-have selected.</span></li>
-<li><strong>Optional: </strong><span>Select the check box to save the settings of this
-export to a file. You can later right click on the file in the Navigator or other views
-and export the same set of files without having to use the export wizard.</span>
-<ul><li><strong>Optional: </strong><span>Deselect the checkbox to export only the set of files
-that have changed since the last export. This is selected by default. It ensures that only files
-that have changed since the last export will be exported next time and provides better performance.</span></li>
-</ul>
-</li>
-<li><span>When you have specified the destination directory, click <b>Finish</b> to
-export the resources to the remote system.</span>
-</li>
-</ol>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tremoimp.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tremoimp.html deleted file mode 100755 index 16e3a88e9..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tremoimp.html +++ /dev/null @@ -1,33 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Importing resources from a remote file system</title>
-</head>
-
-<body id="tremoimp"><a name="tremoimp"><!-- --></a>
-<h1 class="topictitle1">Importing resources from a remote file system</h1>
-<div>
-<p>A page in the Import wizard enables you to import resources from a remote file system to the workspace.</p>
-<div class="p">To import resources to the workspace:</div>
-<ol>
-<li><span>Select <span><b>File</b> > <b>Import</b></span> from the menu bar. The Import wizard opens.</span></li>
-<li><span>Select <b>Remote file system.</b> Click <b>Next</b>.
-The Remote file system page opens.</span></li>
-<li><span>Select or type a source folder, or click <b>Browse</b> to
-select a folder from the <b>Browse For Folder</b> window. </span> Note that you can create a connection from this window.</li><li><span>Use the left and right panes to select resources to import. Choose
-individual resources from the right pane, or entire folders from the left
-one. You can select files from multiple projects.</span></li>
-<li><span>In the second <b>Folder</b> field, specify the
-destination for the imported resources.</span></li>
-<li><strong>Optional: </strong><span>Select the check box to overwrite (without prompting) files of the same name in the workspace.</span></li>
-<li><span>Select one of the radio buttons to either replicate the remote folder structure in the workspace or create only the actual folders you have selected.</span></li>
-<li><span>When you have specified the source and destination, click <b>Finish</b> to import the resources to the workspace.</span></li>
-</ol>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tremtype.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tremtype.html deleted file mode 100755 index e80fbb76a..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tremtype.html +++ /dev/null @@ -1,31 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Removing an existing type</title>
-</head>
-
-<body id="tremtype"><a name="tremtype"><!-- --></a>
-<h1 class="topictitle1">Removing an existing type</h1>
-<div>
-<div class="p">To remove an existing type: </div>
-<ol>
-<li><span>In the Remote Systems view, right-click on a subsystem, and select <span><b>Work With </b> > <b>Named Types</b></span>.</span></li>
-<li><span>On the Work With Named Types window, expand <b>Object</b> or <b>Member</b>.</span></li>
-<li><span>Select your defined type from the list. You cannot remove any IBM-supplied types.</span></li>
-<li><span>Click <b>Remove</b>.</span></li>
-</ol>
-</div>
-<div>
-<p><b class="relconceptshd">Related concepts</b><br />
-<a href="../concepts/cuseractions.html" title="">User actions (user options)</a><br />
-</p><p><b class="reltaskshd">Related tasks</b><br />
-<a href="tedittype.html" title="">Editing an existing type</a><br />
-</p>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/truncmdsview.html b/rse/doc/org.eclipse.rse.doc.user/tasks/truncmdsview.html deleted file mode 100755 index c382004b6..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/truncmdsview.html +++ /dev/null @@ -1,55 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Running and viewing commands and shells using the Remote Commands view </title>
-</head>
-
-<body id="truncmdsview"><a name="truncmdsview"><!-- --></a>
-<h1 class="topictitle1">Running and viewing commands and shells using the Remote Commands view </h1>
-<div>
-<div class="p">You can open a shell for your local and remote systems, from the
-Remote System Explorer, <p><b>Opening the Remote Commands view and launching
-a command shell</b></p>
-<p>In the Remote System Explorer, switch to the Remote
-Commands view by clicking <b>Window > Show View > Remote Commands</b> from
-the menu bar. To open a new shell in the Remote Commands view, click the down
-arrow in the view and select <b>Launch shell</b>. To launch a new shell for
-another connection requires that an existing shell for that connection is
-selected in the view. Otherwise, the shell must be launched from the Remote
-Systems, Remote System Details, or the Remote Commands view.</p>
-<p><b>Working with shells</b></p>
-<p> When the Remote Commands view is open, you can work
-with shells. When you work with a shell, you are working with a shell that
-preserves its environment across commands. The environment for all commands
-in the shell may change in response to your input. For example, if you type
-<pre>cd ..</pre>
-you change the working directory for that shell.</p>
-<p><b>Viewing output in an editor</b></p>
-<p>You can double-click a line of output to open
-it in an editor. For example, if you encounter an error while running a command,
-you can double-click the error and the editor opens the source to the line
-of code where the parser found a problem.</p>
-<p><b>Closing shells</b></p>
-<p>The <b>Cancel shell</b> toolbar item is enabled when the currently displayed shell or command
-is active. Press <b>Cancel Shell</b>, to terminate that process.
-If the shell is active, it cancels the shell before removing it from the view.</p>
-<p><b>Content assist</b></p>
-<p>The Remote Commands view supports content assist. You can press CTRL+space to complete file names
-or environment variable names while you type commands.</p>
-<p></p>
-</div>
-</div>
-<div>
-<p><b class="relconceptshd">Related concepts</b><br />
-<a href="../concepts/crunremcmds.html" title="">Shells and commands in the Remote Systems view</a><br />
-</p><p><b class="reltaskshd">Related tasks</b><br />
-<a href="twrkcmdshl.html" title="">Working with command shells</a><br />
-</p>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/ttablecopy.html b/rse/doc/org.eclipse.rse.doc.user/tasks/ttablecopy.html deleted file mode 100755 index 807074c65..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/ttablecopy.html +++ /dev/null @@ -1,37 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Copying and pasting in the Remote System Explorer</title>
-</head>
-
-<body>
-<h1>Copying and pasting in the Remote System Explorer</h1>
-<p>You can copy and paste files not only between
-files and folders, but between different
-host systems as well. For example, you can
-copy a file from one folder on your host
-to another, or from one type of system to
-another. You can select multiple files as
-well. However, there are guidelines for what
-kinds of items you can and cannot copy and
-paste. In the Remote Systems view, expand
-the two connections (that represent the two
-hosts) until you see the file that you want
-to copy and the location on the other host
-where you want to paste the file.</p>
-<p>To copy and paste:</p>
-<ol>
-<li>Right-click the original file to select it and select <b>Copy</b>.</li>
-<li>Navigate through the directories and files until you find the place where you want to paste the file.</li>
-<li>Right-click on the parent file that contains the files where you want to paste your file, and select <b>Paste</b>.</li>
-</ol>
-<p><b>Related tasks</b><br/>
-<a href="ttabledrag.html">Dragging and dropping items in the Remote System Explorer</a><br/>
-</p>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/ttabledrag.html b/rse/doc/org.eclipse.rse.doc.user/tasks/ttabledrag.html deleted file mode 100755 index 70095e99f..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/ttabledrag.html +++ /dev/null @@ -1,48 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2003, 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>Dragging and dropping items in the Remote System Explorer</title>
-</head>
-
-<body>
-<a name="ttabledrag"></a>
-<h1 class="topictitle1">Dragging and dropping items in the Remote System Explorer</h1>
-<div>
-<div class="p">
-<div class="p">You can drag and drop files between different
-hosts, such as Local, Linux, UNIX, or Windows.
-Additionally, you can drag and drop items
-within one view; for example, in the Remote
-Systems view, or you can drag and drop items
-between views; for example, from the Remote
-Systems view to the Remote Systems Details
-view. When you drag and drop items, you copy,
-rather than cut, the item that you move.
-If you want to remove an item completely
-and put it in another location, drag and
-drop the item first, and then delete the
-item from the original location.</div>
-<p>To drag and drop files or objects:<br/>
-</p>
-<ol>
-<li>In the Remote Systems view, expand the two connections (that
-represent the two hosts) until you see the file you want to copy and the location
-on the other host where you want to paste the file. Or, open two
-views that contain the item and the destination.</li>
-<li>Click the item once to select it, hold down the left mouse button
-while you drag the item to the desired location, and then release the button.</li>
-</ol>
-</div>
-</div>
-<div>
-<p><b>Related tasks</b><br clear="all"/>
-<a href="ttablecopy.html" title="">Copying and pasting in the Remote System Explorer</a><br clear="all"/>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup.html deleted file mode 100755 index fd193f8ad..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup.html +++ /dev/null @@ -1,137 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Using team support</title>
-</head>
-
-<body id="tteamsup">
-<a name="tteamsup"><!-- --></a>
-<h1 class="topictitle1">Using team support</h1>
-<div>
-<div class="p">You can use any Eclipse-enabled repository from any
-vendor. The following
-information describes project-sharing using Concurrent Versions System
-(CVS) support that comes with Eclipse. Steps and user interface
-elements will differ depending on the repository
-support that you have installed.
-<div class="note"><span class="notetitle">Note: </span>When you
-synchronize your RemoteSystemsConnection project with the repository
-the first time, you will see many files in conflict.
-This is because it takes one synchronization to properly align
-the server's encoded version information with your local files. This
-happens only once and you can just receive all of the incoming changes
-and your local workspace will then be synchronized with the server. You
-might also find inactive profiles that belong to other teammates in the Team
-view after you synchronize with the central server. You can choose whether
-or not to activate these profiles in the Team view if you want to see the
-profile's contents in the Remote System Explorer on your local workstation.</div>
-<p>In a team programming environment, team members do work in their own workbench,
-isolated from others. Eventually they will want to share their work with
-their teammates. The Remote System Explorer allows them to share
-their connections, filter pools, and filters. To share these resources:</p>
-</div>
-<ol>
-<li class="skipspace">In the Remote System Explorer perspective, select the Team tab which by
- default is located in the same pane as the Remote Systems view. This
- will bring the Team view to the front of the Remote System Explorer.
- You can also use the <img src="../images/gsarrow.gif" title="" alt="menu" style="width: 24px; height: 23px;"/>
-button on the Remote Systems view and select the <span style="font-weight: bold;">Work
-With Profiles</span> action.<span> </span></li>
-<li class="skipspace"><span>Expand <b>RemoteSystemsConnections</b>. The profiles that you have defined, as well as the Team profile, are displayed. The Team profile is created by the Remote System Explorer to use for sharing connections, filter pools, and filters if you do not want to share them in a profile that you create and manage.</span></li>
-<li class="skipspace"><span>Right-click on <b>RemoteSystemsConnections</b>
-and select <span><b>Team</b> > <b>Share Project</b></span> . </span></li>
-<li class="skipspace"><span>Select <b>CVS</b> and click <b>Next</b>.</span></li>
-<li class="skipspace"><span>Select <b>Use existing repository
-location </b> if you have already defined a CVS repository. Select <b>Create a new
-repository</b> location if you need to define a CVS repository (this
-information should be available from the person who configured the CVS
-repository on the server). To create a CVS repository definition:</span>
- <ol type="a">
- <li class="skipspace"><span>In the <b>Host</b> field, type the
-address of the server, for example mymachine.com. </span></li>
- <li class="skipspace"><span>In the <b>Repository path</b> field,
-type the path to the repository on the server, for example /home/test, d:/test. </span></li>
- <li class="skipspace"><span>In the <b>User</b> field, type the
-user name to use to connect to the repository. </span></li>
- <li class="skipspace"><span>In the <b>Password</b> field, type
-the password for the user name. </span></li>
- <li class="skipspace"><span>From the <b>Connection Type</b>
-list, select the authentication protocol of the CVS server. There are three
-connection methods that come with the Eclipse CVS client: </span>
- <ul>
- <li><b>pserver</b>: A CVS specific connection method. </li>
- <li><b>extssh</b> : An SSH 1.0 client included with the workbench. </li>
- <li><b>ext</b>: The CVS ext connection method that uses an
-external tool such as SSH to connect to the repository. The tool used
-by ext is configured in the<span><b>Team</b> > <b>CVS</b> > <b>EXT
-Connection Method</b></span> preference page. </li>
- </ul>
- </li>
- <li class="skipspace"><span>If the server uses a custom port,
-enable <b>Use Port</b> and
-enter the port number. </span></li>
- </ol>
- </li>
- <li class="skipspace"><span>Click <b>Finish</b>. The repository
-location is
-created. The <span style="font-weight: bold;">RemoteSystemsConnections</span> project will be created remotely and the Synchronize view will open and
- allow you to commit its resources to the server. If the project already
- exists remotely, the Synchronize view will show conflicts on any files
- that exist both locally and remotely. If the </span><span><span
- style="font-weight: bold;">RemoteSystemsConnections</span> </span><span>project
-already exists in the repository when you first share it, there may be
-many conflicts. Generally, these are not real conflicts, but simply considered
-conflicts on the first synchronize because there is no local CVS information for the
-resources in your workspace.
-If you have not created any resources in your Team profile, you can
-safely send or receive all of the conflicting files. If you have created
-resources in your Team profile, you should check each conflicting file to ensure
-there really are no differences, and if there are, resolve them by merging.</span></li>
- <li class="skipspace"><span>To synchronize your resources with those
-in the associated repository, right-click on the <span style="font-weight: bold;">RemoteSystemsConnection
- </span>project, and select <span><b>Team</b> > <b>Synchronize
-with Repository</b></span>.</span></li>
- <li class="skipspace"><span>After sharing or synchronizing, and
-receiving incoming resources from the repository, right-click on the <span
- style="font-weight: bold;">RemoteSystemsConnection </span>project,
-and select <b>Reload Remote System Explorer</b>. This refreshes
-the Remote System Explorer and Team view to reflect the new or changed
-resources.</span></li>
-</ol>
-</div>
-<div class="nested1" id="tviewproject"><a name="tviewproject"><!-- --></a>
-<h2 class="topictitle2">Viewing the project resources in the Navigator
-view</h2>
-<div>
-<div class="p">The Navigator view provides a hierarchical view of all
-the resources in the workspace. From here, you can view the contents of the projects
-that are shared, including the <span style="font-weight: bold;">RemoteSystemsConnection
-</span>project, and select team-related actions on particular
-resources. By default, the Navigator view is included in the Resources perspective.
-To add it to the current perspective,
-<ol>
- <li>Select <span><b>Window</b> > <b>Show View</b> > <b>Other</b></span>.</li>
- <li>Expand <b>Basic.</b> </li>
- <li>Select <b>Navigator.</b></li>
-</ol>
-</div>
-<div class="p"><img src="../images/navigator.jpg" alt=""/></div>
-</div>
-<div>
-<p><b class="relconceptshd">Related concepts</b><br/>
-<a href="../concepts/cteam.html" title="">Team support</a><br/>
-<a href="../concepts/cprofile.html" title="">Remote System Explorer
-Profiles</a><br/>
-</p>
-<p><b class="reltaskshd">Related tasks</b><br/>
-<a href="tteamsup1.html" title="">Working with profiles and team support</a><br/>
-</p>
-</div>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup1.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup1.html deleted file mode 100755 index bfbcd2285..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup1.html +++ /dev/null @@ -1,84 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> - -<head> -<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> -<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Working with profiles and team support</title> -</head> - -<body id="tteamsup1"> -<a name="tteamsup1"></a> -<h1 class="topictitle1">Working with profiles and team support</h1> -<div> -<div class="p">All connections, filter data, user actions, and compile -commands belong to profiles. Profiles can be shared by team members for the purpose of -team development. You can work with your profiles in the Team view to enable -greater control over team-sharable elements in the Remote System Explorer. -<div class="note"><span class="notetitle">Note: </span>Because -the Remote Systems view only displays connections, filters, user -actions, and compile commands from active profiles, you need to be in the Team -view to work with or activate your non-active profiles. -</div> -</div> -<div class="p">To manage your team profiles: -<div class="p"> -<ol> -<li>In the Remote Systems perspective, select the Team tab which by -default is located in the same pane as the Remote Systems view. -This will bring the Team view to the front of the Remote System -Explorer. You can also use the -<img src="../images/gsarrow.gif" title="" alt="menu" style="width: 24px; height: 23px;"/> -button on the Remote Systems view and select the <span style="font-weight: bold;">Work With Profiles</span> -action.<br/> - </li> - <li>In the Team view, expand the root element, <b>RemoteSystemsConnections</b>, -to see a list of your profiles. - <ul> - <li>To create a profile, right-click on the root element in the -Team view, and select <b>New > Profile</b> and complete the dialog box for the -profile.</li> - <li>To activate or deactivate a profile, right-click the profile -and select <b>Active</b> (if it is deactivated) or <b>Not active</b> (if it is active).</li> - <li>To duplicate a profile in the view, right-click the profile -and select <b>Duplicate</b>. This action copies all of the profile's connections, filters, user -actions, and compile commands.</li> - <li>To rename a profile, right-click the profile and select <b>Rename</b>.</li> - </ul> - </li> - <li>In the Team view, you can also expand your profiles to view -connections, filter pools, user actions, and compile commands that belong to each -profile. Right-click on any of your specific filters, user actions, and so on, -to open a <b>Work with</b> window. These are the same actions available in the -Remote Systems view. To work with filter pools, for example, right-click one -of your filters, and select <b>Work with filter pools</b>. Keep in mind that -the Remote Systems view is the more ideal environment to manipulate filters, -filter pools, compile commands, user actions, and so on. The Team view is designed to -manage profiles, and view the elements that belong to each profile. The Remote -Systems view is designed for you to work with all the items that belong to your -active profiles. It includes a greater number of right-click and menu options -for a development-focused approach.</li> - <li>When you have finished working with your profiles, switch back to -the Remote Systems view, by clicking the Remote Systems tab, to continue -working with active profile artifacts, or remain in the Team view to -<a href="tteamsup.html">synchronize your profiles with the repository</a>.</li> -</ol> -</div> -</div> -</div> -<div> -<p><b class="relconceptshd">Related concepts</b><br/> -<a href="../concepts/cteam.html" title="">Team support</a><br/> -<a href="../concepts/cprofile.html" title="">Remote System Explorer Profiles</a><br/> -</p> -<p><b class="reltaskshd">Related tasks</b><br/> -<a href="tteamsup.html" title="">Using team support</a><br/> -<!-- TODODeferred after RSE 1.0 -<a href="tworkuseract.html" title="">Managing user actions (user options)</a><br/> ---> -</p> -</div> -</body> -</html> diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tworkuseract.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tworkuseract.html deleted file mode 100755 index b59e32df9..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tworkuseract.html +++ /dev/null @@ -1,75 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Managing user actions (user options)</title>
-</head>
-
-<body id="tworkuseract">
-<a name="tworkuseract"></a>
-<h1 class="topictitle1">Managing user actions (user options)</h1>
-<div>
-<div class="p">To create a new action or change an existing action:</div>
-<ol>
-<li><span>In the Remote Systems view, expand the connection
-containing the kinds of resources you want to act on,
-navigate to the subsystem that would contain those resources, and
-select <b>Work with > User actions</b>.
-You can also right-click on a file in one of your filters, and select <b>User
-Actions</b>.</span></li>
-<li><span>Type the text to display in the <b>Action Name</b> field.
-This is a brief label for the action.</span></li>
-<li><span>Type a longer, more descriptive text for the action in the <b>Comment</b>
-field.</span></li>
-<li><span>Type the actual command string to run when
-a user selects this action. This command can use action substitution
-variables when your action is run. These variables are used when defining the
-command string to run for a particular action. Substitution variables keep you
-from having to explicitly code command parameter values. Click <b>Insert
-variable</b> to see and select valid variables.</span></li>
-</ol>
-<div class="p"><b>Additional parameters</b>
-<ul>
-<li>Select <b>Browse</b> to search for and select command
-files (for example, .exe, .bat or .cmd files). The file name you select
-is reflected in the Command field when you return. </li>
-<li>Select <b>Prompt</b> to prompt the command currently entered
-in the Command area.</li>
-<li>Select <b>Prompt first</b> to indicate that Remote System
-Explorer should prompt the command when it is run.</li>
-<li>Select <b>Refresh after</b> to have Remote System Explorer
-refresh the selected files after the action's command is run. This is
-useful if your command affects the information displayed in the file list
-window for the selected files, for example, if your command changes the type
-of a file.</li>
-<li>Select <b>Show action</b>.</li>
-<li>Select <b>Single selection only</b> if you want to show
-this action only when a single object is selected.</li>
-<li>Select <b>Invoke once </b> to collect the full names of
-all selected resources into the file name parameter and run the command
-only once for all resources that are selected..</li>
-<li>Select any currently defined named types from the <b>Defined
-Types</b> list
-and click <b>Add</b> to include them in the <b>Selected
-Types</b> list. The action will only appear if a file matching one
-of these types is selected.</li>
-</ul>
-<p>You can choose to view user actions by active profile for remote
-objects
-on the <b>User Actions</b> cascade menu. You can see both
-team-shared and private user actions. To enable this, select <b>Cascade
-user actions by profile</b> on the <b>Remote Systems Preferences</b>
-page.</p>
-</div>
-</div>
-<div>
-<p><b class="relconceptshd">Related concepts</b><br/>
-<a href="../concepts/cuseractions.html" title="">User actions (user options)</a><br/>
-</p>
-</div>
-</body>
-</html>
diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/twrkcmdshl.html b/rse/doc/org.eclipse.rse.doc.user/tasks/twrkcmdshl.html deleted file mode 100755 index 36a7efc44..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/twrkcmdshl.html +++ /dev/null @@ -1,57 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 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>Working with command shells</title>
-</head>
-
-<body id="twrkcmdshl"><a name="twrkcmdshl"></a>
-<h1 class="topictitle1">Working with command shells</h1>
-<div>
-<p>In the Remote Systems view, you can launch a shell to perform commands
-in a specific directory or folder of a remote file system.</p>
-<div class="p">
-To launch a new shell from the Remote Systems view:
-<ol>
-<li>Expand a connection.</li>
-<li>Right-click on a file subsystem that supports shells and select <b>Launch Shell</b>.</li>
-<li>Enter shell commands, such as "ls" or "pwd", in the <b>Command</b> field (just beneath the shell itself).</li>
-</ol>
-</div>
-<div class="p">
-You can also run commands from locations further down in the remote file system
-tree, so that you do not need to navigate there from your home directory each time.
-This option takes the default shell, sets the current directory to the folder that was selected,
-and invokes a command in that directory. If you check the <b>Run in
-new shell</b> check box you will get a new shell instead of running the
-command in the current shell:
-<ol>
-<li>Expand the file subsystem until you are at the directory where you want
-to run your commands.</li>
-<li>Right-click on that directory and select <b>Run Commands</b>.</li>
-<li>Enter the command you want to run in the <b>Command</b> field and click <b>OK</b>.</li>
-</ol>
-</div>
-<div class="note">
-<span class="notetitle">Note: </span>
-Each new shell shows up in a separate tab. If more than one
-shell is running on the same connection, each subsequent shell has a number
-appended to the connection name.
-</div>
-</div>
-<div>
-<p>
-<b class="relconceptshd">Related concepts</b><br/>
-<a href="../concepts/crunremcmds.html" title="">Shells and commands in the Remote Systems view</a><br/>
-</p>
-<p>
-<b class="reltaskshd">Related tasks</b><br/>
-<a href="truncmdsview.html" title="">Running and viewing commands and shells using the Remote Commands view</a><br/>
-</p>
-</div>
-</body>
-</html>
\ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/toc.xml b/rse/doc/org.eclipse.rse.doc.user/toc.xml deleted file mode 100755 index 6fe447d1b..000000000 --- a/rse/doc/org.eclipse.rse.doc.user/toc.xml +++ /dev/null @@ -1,61 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<toc label="RSE User Guide"> - <topic label="Getting Started" href="gettingstarted/g_start.html"> - <topic label="Installing the Remote System Explorer" href="gettingstarted/g1installing.html"/> - <topic label="First Steps with the Remote System Explorer" href="gettingstarted/g2firststeps.html"/> - <topic label="Setting up a dstore server" href="tasks/tbeginlinux.html"/> - <topic label="Using Remote Connections" href="gettingstarted/gusing.html"/> - <topic label="Extending Remote System Explorer" href="gettingstarted/gxtending.html"/> - </topic> - <topic label="Remote System Explorer Connections" href="concepts/cbegin.html"> - <topic label="Universal Systems" href="concepts/cuniversal.html"/> - <topic label="Connecting to a remote Linux or UNIX server" href="tasks/tbeginlinux.html"/> - <topic label="Connecting to a remote Windows server" href="tasks/tbeginwindows.html"/> - <topic label="Disconnecting from a remote server" href="tasks/tbegindiscon.html"/> - <topic label="Creating a second connection to a remote server" href="tasks/tbeginsecond.html"/> - <topic label="Deleting a connection" href="tasks/tbegindelete.html"/> - <topic label="Configuring environment variable support for connections" href="tasks/tbeginenv.html"/> - </topic> - <topic label="Remote System Explorer filters, filter pools, and filter pool references" href="concepts/cfilters.html"> - <topic label="Creating filters" href="tasks/tmanagemem.html"/> - <topic label="Changing filters" href="tasks/tmanageedit.html"/> - <topic label="Deleting filters" href="tasks/tmanagedel.html"/> - <topic label="Configuring filter pools" href="tasks/tmanagepools.html"/> - <topic label="Configuring filter pool references" href="tasks/tmanagepoolsref.html"/> - </topic> - <topic label="Remote System Explorer Profiles" href="concepts/cprofile.html"> - <topic label="Creating a second profile" href="tasks/tbeginsecprofile.html"/> - <topic label="Deleting a profile" href="tasks/tbegindeleteprofile.html"/> - </topic> - <topic label="Team support" href="concepts/cteam.html"> - <topic label="Using team support" href="tasks/tteamsup.html"/> - <topic label="Working with profiles and team support" href="tasks/tteamsup1.html"/> - </topic> - <topic label="Shells and commands in the Remote Systems view" href="concepts/crunremcmds.html"> - <topic label="Running and viewing commands and shells using the Remote Commands view" href="tasks/truncmdsview.html"/> - <topic label="Working with command shells" href="tasks/twrkcmdshl.html"/> - </topic> - <!-- TODODeferred after RSE 1.0 - <topic label="User actions" href="concepts/cuseractions.html"> - <topic label="Managing user actions" href="tasks/tworkuseract.html"/> - <topic label="Editing an existing type" href="tasks/tedittype.html"/> - <topic label="Removing an existing type" href="tasks/tremtype.html"/> - </topic> - --> - <topic label="Search for text and files on remote servers" href="tasks/tmanagesearch.html"> - <topic label="Using search parameters with special characters" href="ref/rsearch.html"/> - </topic> - <!-- TODODeferred after RSE 1.0 - <topic label="Compiling programs" href="concepts/cremcompile.html"/> - --> - <topic label="Managing archived files" href="tasks/tarchive.html"/> - <!-- TODODeferred after RSE 1.0 - <topic label="Importing resources from a remote file system" href="tasks/tremoimp.html" /> - <topic label="Exporting resources to a remote file system" href="tasks/tremoexp.html" /> - <topic label="Building programs on a remote system" href="tasks/tbuild.html" /> - --> - <topic label="Accessing Remote System Explorer preferences" href="ref/rrsepref.html"/> - <topic label="Saving User IDs and passwords" href="tasks/tbeginpass.html"/> -<topic label="Legal" href="notices.html"/> -</toc>
\ No newline at end of file diff --git a/rse/doc/readme.txt b/rse/doc/readme.txt deleted file mode 100644 index 4b45b5127..000000000 --- a/rse/doc/readme.txt +++ /dev/null @@ -1,2 +0,0 @@ -Use the "doc" folder for plugin projects containing documentation. -All projects should be named "org.eclipse.rse.doc.*".
\ No newline at end of file |
