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

[191588] simplified the team support discussion, removing most of it.

Browse source
This commit is contained in:
David Dykstal 2007-06-20 03:29:10 +00:00
parent 7113be1267
commit 2c6a9629c6
5 changed files with 109 additions and 81 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

41
rse/doc/org.eclipse.rse.doc.isv/guide/Artifacts.html
View file

@ -4,7 +4,7 @@
<head> <head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css"> <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." > <meta name="copyright" content="Copyright (c) IBM Corporation and others 2002, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" HREF="../book.css"> <link rel="stylesheet" type="text/css" HREF="../book.css">
<title>RSE Artifacts</title> <title>RSE Artifacts</title>
</head> </head>
@ -30,18 +30,24 @@ The RSE's <A href="view_RS.gif">Remote Systems view</A> shows all existing <b>Ho
Hosts are objects that are persisted, containing the information needed to access a particular remote host. 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. The view contains a prompt to create new Hosts, and pop-up menu actions to rename, copy, delete, and reorder existing Hosts.
</p> </p>
<p>Hosts contain attributes, or data, that is saved between sessions of the workbench. These attributes are <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 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. 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 Underneath, all Hosts are stored in profiles by an registered persistence provider.
the user can enable for team support, allowing Hosts to be shared by a team.
</p> </p>
<h2><A name="profiles">Profiles</A></h2> <h2><A name="profiles">Profiles</A></h2>
<p> <p>
To facilitate team-shared and user-unique Hosts, To facilitate sharing Hosts are owned by <b>Profiles</b>.
Hosts are owned by <b>profiles</b>. These are simply <A href="file_profiles.gif">folders in the RemoteSystemsConnections In 1.0 these were simply folders in the RemoteSystemsConnections
project</A>, as it turns out, within which all other data including Hosts are scoped. Internally profiles are realized as project. With the introduction of persistence providers in 2.0, profiles
can now be persisted in multiple forms - including the 1.0 scheme.
It is our intention to have RSE allow for the sharing of profiles by exporting to and importing from
the file system or from projects in a future release.
</p>
<p>
Internally profiles are realized as
SystemProfile objects, managed by the SystemProfileManager. SystemProfile objects, managed by the SystemProfileManager.
For each profile there is also a SystemHostPool object For each profile there is also a SystemHostPool object
created to manage the Hosts within that profile. There are menu actions for the created to manage the Hosts within that profile. There are menu actions for the
@ -53,7 +59,11 @@ By default, there exists a profile named <code>Team</code>, and a profile with a
host is created the user is asked to supply this unique name, which defaults to the hostname of their 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 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 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 setting to show the host names qualified by their profile name.
</p>
<!-- TODO
<p>
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 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 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 all the Hosts created by all the team members. However, only the two default profiles are active, so the Hosts
@ -66,13 +76,11 @@ for:
<li>User-roaming, whereby a user uses a different workstation than usual, <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. and then synchronizes with the team repository and sets their profile to be active.
</ol> </ol>
<p> -->
<!-- TODO rework
As an aside, user IDs and passwords are not shared with the team repository, but rather stored only locally per As an aside, user IDs and passwords are not shared with the team repository, but rather stored only locally per
workstation. 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> <h2><A name="subsystems">Subsystems and subsystem configurations</A></h2>
<p> <p>
@ -98,7 +106,12 @@ remote commands. There is also a Remote Shell view supplied that logs all comman
enter a command to be run remotely. The commands all execute within the same shell, and users 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. can launch additional shells for the same host.
</ol> </ol>
<h2><A name="systems">Systems and System Managers</A></h2> <p>
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="systems">Connector services and their managers</A></h2>
<p>While not seen by the user, subsystem objects are required to return a <b>connectorservice</b> object via the <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 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 is an object implementing the <A href="../reference/api/org/eclipse/rse/core/subsystems/IConnectorService.html">IConnectorService</A> interface.

20
rse/doc/org.eclipse.rse.doc.isv/guide/plugin/subsystem.html
View file

@ -23,14 +23,20 @@ each created by a subsystem configuration registered with this extension point.
as it has only one element, <b><samp>&lt;configuration&gt;</samp></b>, with only a few simple attributes to supply: as it has only one element, <b><samp>&lt;configuration&gt;</samp></b>, with only a few simple attributes to supply:
</p> </p>
<ul> <ul>
<li><b>id</b>. Unique id for the extension, as required for all extensions. However, in this case it is used to create <li><b>id</b>.
folders within the <samp>RemoteSystemsConnections</samp> project, where all Remote System Explorer data is stored. Unique id for the extension, as required for all extensions.
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 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. object via its ID.
<li><b>icon</b>. The icon displayed in the Remote Systems view for each subsystem created by this subsystem configuration. <li><b>vendor</b>.
<li><b>iconlive</b>. The icon used when the subsystem is physically connected to its remote system. Your company name, shown in properties dialog for subsystems created by this subsystem configuration.
<li><b>name</b>. The name displayed in the Remote Systems view for each subsystem created by this subsystem configuration. <li><b>icon</b>.
<li><b>systemTypeIds</b>. A semi-colon separated list of system type IDs which this subsystem configuration supports. When a user creates a 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>systemTypeIds</b>.
A semi-colon separated list of system type IDs 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. Wildcards are connection, this configuration will only be asked to create a subsystem for connections to systems of these types. Wildcards are
supported; in order to register against all system types, specify a single "*". supported; in order to register against all system types, specify a single "*".
<li><b>serviceType</b>. An optional semi-colon separated list of names and transports that can be used to match this service with remotelly advertised services through DNS-SD or any other supported service discovery protocol. <li><b>serviceType</b>. An optional semi-colon separated list of names and transports that can be used to match this service with remotelly advertised services through DNS-SD or any other supported service discovery protocol.

123
rse/doc/org.eclipse.rse.doc.user/concepts/cprofile.html
View file

@ -2,60 +2,52 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html> <html>
<head> <head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page."/> <meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2007. 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"/> <link rel="stylesheet" type="text/css" href="../book.css" />
<title>Remote System Explorer Profiles</title> <title> Remote System Explorer Profiles </title>
</head> </head>
<body id="cprofile-body"> <body id="cprofile-body">
<a name="cprofile"><!-- --></a> <a name="cprofile">
<h1 class="topictitle1">Remote System Explorer Profiles</h1> <!-- -->
</a> <h1 class="topictitle1"> Remote System Explorer Profiles </h1>
<div> <div>
<p>When you define your first connection to your remote server, you <p>
will also define 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 <em>private profile</em>), plus a common profile called <i> Team</i>. The intent is to be able to share the Team profile in the future with other members of your team. You can also create your own profiles.
your first profile. All Remote System Explorer resources such as </p>
connections, <div class="p">
filters, and filter pools are owned by a profile. Profiles help you Profiles contain:
manage these resources when you have a lot of connections. The Remote <ul>
System Explorer creates <li>
a unique profile per team member (that person's <span Connections -- including subsystem properties. User IDs and passwords are not shared.
style="font-style: italic;">private profile</span>), plus a common </li>
profile called <i>Team</i>. <li>
You can also create your own profiles. </p> Filters, filter pools, and filters pool references
<div class="p">Profiles contain: </li>
<ul> <li>
<li>Connections -- including subsystem properties. User IDs and User-defined actions
passwords are not shared.</li> </li>
<li>Filters, filter pools, and filters pool references</li> <li>
<li>User-defined actions</li> Compile commands
<li>Compile commands</li> </li>
</ul> </ul>
</div> </div>
<p>Profiles can be active, or inactive. By default, only your private <p>
profile 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.
and the Team profile are active. The Remote System Explorer displays </p>
all connections <p>
from all active profiles and, within a connection, allows filter pools 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 in the future you can share resources and information with other people.
to </p>
be referenced from any active profile. Further, the user actions and <div class="p">
compile <!-- TODO rework
commands shown in the right-click menu for a remote resource are from Placing all connection and filter data in a profile
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 shared by the team
assists in team support, since all connections, filter pools, and team assists in team support, since all connections, filter pools, and team
profiles profiles
can be shared among team members. You can use the Team view to control can be shared among team members.
which -->
profiles display in your workspace by making the profiles active. You can use the Team view to control which profiles display in your workspace by making the profiles active.
<!-- TODO rework
<div class="note"><span class="notetitle">Note: </span>Making <div class="note"><span class="notetitle">Note: </span>Making
a profile active or inactive does not affect your teammates. For a profile active or inactive does not affect your teammates. For
example, example,
@ -69,7 +61,9 @@ the profiles are stored. See topics in the help contents and
links links
below about team support for more information on profiles and shared below about team support for more information on profiles and shared
data.</div> data.</div>
</div> -->
</div>
<!-- TODO rework
<p>To reduce collisions when you synchronize the user IDs and the <p>To reduce collisions when you synchronize the user IDs and the
ordering of ordering of
resources in a profile are stored locally on your workstation. To resources in a profile are stored locally on your workstation. To
@ -84,21 +78,30 @@ will
then be stored on the server, and any developer can obtain profile then be stored on the server, and any developer can obtain profile
resources resources
from the central server. </p> from the central server. </p>
-->
</div> </div>
<div> <div>
<p><b class="relconceptshd">Related concepts</b><br/> <p>
<a href="cfilters.html" title="">Remote System Explorer filters, filter <b class="relconceptshd"> Related concepts</b>
pools, and filter pool references</a><br/> <br />
<a href="cbegin.html" title="">Remote System Explorer Connections</a><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 />
<!-- TODO rework
<a href="cteam.html" title="">Team support</a><br/> <a href="cteam.html" title="">Team support</a><br/>
</p> -->
<p><b class="reltaskshd">Related tasks</b><br/> </p>
<p>
<b class="reltaskshd"> Related tasks</b>
<br />
<!-- TODO rework
<a href="../tasks/tteamsup.html" title="">Using team support</a><br/> <a href="../tasks/tteamsup.html" title="">Using team support</a><br/>
<a href="../tasks/tteamsup1.html" title="">Working with profiles and <a href="../tasks/tteamsup1.html" title="">Working with profiles and team support</a><br/>
team support</a><br/> -->
<a href="../tasks/tbeginsecprofile.html" title="">Creating a second <a href="../tasks/tbeginsecprofile.html" title=""> Creating a second profile</a>
profile</a><br/> <br />
</p> </p>
</div> </div>
</body> </body>
</html> </html>

4
rse/doc/org.eclipse.rse.doc.user/gettingstarted/gxtending.html
View file

@ -25,7 +25,9 @@ reference</a>.</p>
User actions, Compile Commands and User actions, Compile Commands and
--> -->
<a href="../ref/rrsepref.html">Preferences</a> and connection setup <a href="../ref/rrsepref.html">Preferences</a> and connection setup
<!-- TODO rework
<a href="../concepts/cteam.html">shared in a team</a>. <a href="../concepts/cteam.html">shared in a team</a>.
-->
</p> </p>
</div> </div>
@ -33,7 +35,9 @@ User actions, Compile Commands and
<p><b class="relconceptshd">Related concepts</b><br/> <p><b class="relconceptshd">Related concepts</b><br/>
<a href="../concepts/cfilters.html" title="">Remote System Explorer filters, filter <a href="../concepts/cfilters.html" title="">Remote System Explorer filters, filter
pools, and filter pool references</a><br/> pools, and filter pool references</a><br/>
<!-- TODO rework
<a href="../concepts/cteam.html" title="">Team support</a><br/> <a href="../concepts/cteam.html" title="">Team support</a><br/>
-->
</p> </p>
<!-- <!--
<p><b class="reltaskshd">Related tasks</b><br/> <p><b class="reltaskshd">Related tasks</b><br/>

2
rse/doc/org.eclipse.rse.doc.user/toc.xml
View file

@ -28,10 +28,12 @@
<topic label="Creating a second profile" href="tasks/tbeginsecprofile.html"/> <topic label="Creating a second profile" href="tasks/tbeginsecprofile.html"/>
<topic label="Deleting a profile" href="tasks/tbegindeleteprofile.html"/> <topic label="Deleting a profile" href="tasks/tbegindeleteprofile.html"/>
</topic> </topic>
<!-- TODO rework needed
<topic label="Team support" href="concepts/cteam.html"> <topic label="Team support" href="concepts/cteam.html">
<topic label="Using team support" href="tasks/tteamsup.html"/> <topic label="Using team support" href="tasks/tteamsup.html"/>
<topic label="Working with profiles and team support" href="tasks/tteamsup1.html"/> <topic label="Working with profiles and team support" href="tasks/tteamsup1.html"/>
</topic> </topic>
-->
<topic label="Shells and commands in the Remote Systems view" href="concepts/crunremcmds.html"> <topic label="Shells and commands in the Remote Systems view" href="concepts/crunremcmds.html">
<topic label="Running and viewing commands using the Remote Shell view" href="tasks/truncmdsview.html"/> <topic label="Running and viewing commands using the Remote Shell view" href="tasks/truncmdsview.html"/>
<topic label="Working with command shells" href="tasks/twrkcmdshl.html"/> <topic label="Working with command shells" href="tasks/twrkcmdshl.html"/>