You can work with TeamWare Configuring in two ways:
Use the command-line interface (CLI).
Use the Configuring graphical user interface (GUI).
Both interfaces are included with TeamWare to accommodate different computing styles. Complete TeamWare Configuring functionality is implemented in both interfaces. The interfaces can be used interchangeably. You can simultaneously use the GUI for some functions and the CLI for others. Both interfaces employ the same underlying Configuring functionality and command structure; the difference is an easy-to-use, graphical, interface for the GUI.
The concepts in this chapter generally apply to both the GUI and the CLI. Except in cases where there are special considerations regarding the CLI, descriptions and examples are included for the GUI only--information specific to the CLI can be obtained online through the man pages. The remainder of this chapter is an introduction to the Configuring CLI and GUI.
This chapter is organized as follows:
The TeamWare Configuring CLI is accessible from any Solaris shell. The CLI is useful when you are not working on a window-based system.
Like SCCS commands, all CLI commands may be executed through a central "umbrella" command. The individual commands may also be executed directly by specifying the individual command name.
The umbrella command codemgr lets you list Configuring commands. You can list Configuring commands with their use summaries by typing codemgr without specifying any arguments. You can achieve the same results by typing codemgr with the help subcommand.
example% codemgr bringover ... codemgrtool help putback ... resolve ... ws_undo .... workspace ....
To use the umbrella command to execute commands, type codemgr followed by the name of the subcommand you wish to execute. For example:
% codemgr bringover -w my_child -p their_parent /usr/ws/project |
You can also execute the commands directly (without typing codemgr). For example:
% bringover -w my_child -p their_parent /usr/ws/project |
You must use the individual command name when you access TeamWare man pages.
TeamWare provides several ways to reduce typing long command-lines, including environment variables and argument files that store previously specified arguments. See the respective man pages for details.
The TeamWare GUI (Configuring) is a tool that enables you to view workspace hierarchies and to execute menu-based commands on workspaces and their contents. Key features include the following:
Graphical display of workspaces in a Workspace Graph pane. This feature enables users to:
Conveniently view workspace hierarchies
Use the mouse to select workspace icons
Execute menu-based commands on selected workspaces and their contents
Menu lists that reduce the need for you to remember and type command names, options, and arguments
Facilities to customize the GUI to meet your individual style and needs
Online help to assist you at all levels, including explanation of error messages
TeamWare windows, menus, and buttons are documented online using the Help feature. With Help, you can obtain information regarding any object on the screen. Therefore, this section does not discuss these objects in detail; rather, it serves as a guide to other aspects of Configuring. Throughout the rest of this chapter, Configuring tasks such as Bringover and Putback transactions and conflict resolution are discussed in detail.
To start TeamWare Configuring, at a shell command prompt type twconfig followed by the ampersand symbol (&).
demo% twconfig& |
After a moment, the Configuring window appears.
Configuring consists of a main window (see Figure 6-1) and a number of dialog boxes. Within the main window is a menu bar from which you can choose items to help you accomplish your tasks. The online help contains a full explanation of TeamWare Configuring windows.
When you start Configuring, the main window opens (see Figure 6-1). In working with Configuring, you select workspace icons in the Workspace Graph pane and then choose commands that act upon the selected workspaces and the files they contain.
File menu |
Provides commands to load, unload, and create workspaces |
Edit menu |
Provides commands to delete, rename, reparent, and update workspaces |
View menu |
Provides commands to set view options in the Workspace Graph pane |
Transactions menu |
Provides commands for synchronizing files with Bringover, Putback and Resolve transactions |
Options menu |
Provides commands for setting Workspace and Configuring options |
TeamWare menu |
Provides command for starting other TeamWare tools |
Workspace Graph pane |
Displays a visual graph of the workspaces you have loaded |
In the Workspace Graph pane each workspace is represented by a workspace icon. Parent and child relationships are depicted by lines connecting workspaces. The path name of the workspace top-level (root) directory is displayed beneath the icon.
When Configuring is started, it checks the directory (or directories) specified by the environment variable CODEMGR_WSPATH to determine if it contains any workspaces. If workspaces are found, they are loaded into the Workspace Graph pane. If CODEMGR_WSPATH is not set, Configuring attempts to load workspaces from the directory in which it was started. To load additional workspaces, choose File > Load Workspaces.
Workspace hierarchy graphs are automatically created in the Workspace Graph pane by the Configuring program as you load workspaces (using the Load menu and the Load Workspaces dialog box (see "Customizing Configuring Using Tool Properties"). Hierarchies are displayed either vertically or horizontally starting from the upper-left corner and distributed to the right as space permits. You can select the orientation by choosing View > Orientation. Vertical orientation is the default. Layout is done automatically--you cannot change the layout by moving icons with the mouse.
Beneath the workspace icon is a text field that contains the name of the workspace root directory. You can choose to have workspace names displayed one of two ways:
Using the absolute (full) path name of the root directory
Using the truncated (short) name of root directory
Choose the display style you prefer by choosing Name >View.
You can change the path name of a workspace by editing the name text box.
You can accomplish two types of operations by directly manipulating icons on the Workspace Graph pane. You can drag and drop workspace icons to initiate both Bringover and Putback transactions and to reparent workspaces.
Interworkspace transactions--If you select and drag a workspace and drop it on top of another icon, Configuring initiates one of the following transactions: Bringover Create, Bringover Update, Putback. You determine which transaction is initiated by which icon you drag, and where you drag it; Table 6-1 summarizes these actions. For more information about interworkspace transactions, see Chapter 8, Copying Files between Workspaces."
Drag: |
To: |
Action |
---|---|---|
Any workspace icon |
Open area |
Activate Bringover Create transaction window |
Parent workspace icon |
Child workspace icon |
Activate Bringover Update transaction window |
Child workspace icon |
Parent workspace icon |
Activate Putback transaction window |
Any workspace icon |
A nonrelated (not a parent or child) workspace icon |
Activate pop-up notice to determine actions |
Reparenting--To use the drag and drop facility to change a workspace's parent, press and hold the SHIFT key while you drag the workspace icon on top of its new parent's icon. If you drag the icon to an open area of the Workspace Graph pane, the workspace will be orphaned (have no parent). The display is automatically adjusted to reflect the new relationship. For more information about reparenting workspaces, see "Reparenting a Workspace".
You are prompted to confirm the reparent operation.
When you double-click when the pointer is over a workspace icon, the TeamWare Versioning is automatically started (with the selected workspace automatically loaded). See Versioning online help and Chapter 12, Performing Basic SCCS Functions with Versioning" for instructions on using Versioning.
If you double-click when the pointer is over the icon of a workspace that contains unresolved conflicts, Configuring automatically activates the Resolve transaction window. Conflicted files from the selected workspace are automatically loaded and ready for processing.
You can customize Configuring double-click behavior using the Tool Properties dialog box (see Table 6-2).
Using the Tool Properties dialog box (see Table 6-2), you can customize the behavior of:
Configuring window functions
Bringover/Putback transactions
Resolve transaction
To open the Tool Properties dialog box, choose Options > Configuring. The Category list box in the dialog box lets you to switch between the Configuring, Bringover/Putback, and Resolve panes.
When you change Configuring behavior using the Tool Properties window, you can use the Apply button to preserve the changes in runtime configuration files in your home directory. The runtime configuration files are consulted by Configuring when it starts; your changes are used as the default values.
Changes made in the Configuring and Bringover/Putback panes of the Tool Properties window are written to the file ~/.codemgrtoolrc. This file is an XWindows resource file.
Changes made in the Resolve pane of the Tool Properties window are written to the runtime configuration file ~/.codemgr_resrc.
The Configuring pane of the Tool Properties dialog box (see Table 6-2) enables you to change the behavior of the Configuring main window. The specific properties are described in Table 6-2.
Property |
Description |
---|---|
Current Working Directory |
Lets you specify the directory to which Configuring actions are relative. |
Workspace Double Click Action |
Lets you specify the commands you want launched when you double-click on a standard workspace icon. Type the path name required to execute the commands based on the current working directory and your search path. By default, the standard workspace command is Versioning (twversion). |
Conflict Workspace Double Click Action |
Lets you specify the commands you want launched when you double-click icons of workspaces that contain conflicts. Type the path name required to execute the commands based on the current working directory and your search path. By default, the Resolve Transaction window (<resolve_pane>) is opened for conflicted workspaces. |
Load Workspaces |
Select this check box if you want the parent and children of workspaces you load in the Workspace Graph pane automatically loaded with them. By default this box is not checked. |
Orientation |
Select the Horizontal setting if you want the workspace hierarchy displayed horizontally from left to right in the Workspace Graph pane. Select the Vertical setting if you want workspace hierarchy displayed vertically from top to bottom. By default the Vertical setting is in effect. This property corresponds to the choosing View Orientation the Configuring main window. |
Workspace Names |
Select the Short setting if you want workspaces labelled with the shortest possible name in the Workspace Graph pane. Select Full if you want workspaces labelled with absolute path names. By default the Full setting is in effect. This property corresponds to choosing View Names in the Configuring main window. |
The Bringover/Putback pane of the Tool Properties dialog box (see Figure 6-3) enables you to change the behavior of the Bringover and Putback panes of the Transactions window. The specific properties are described in Table 6-3.
Property |
Description |
---|---|
Transaction File List |
Selecting Auto Load causes Configuring to reread the Codemgr_wsdata/args file and load it into the File List pane whenever a new workspace is selected. You might choose to deselect this property when you want to use the same file list for a number of transactions involving different workspaces. |
Transaction Output |
If you select Auto Display, Configuring automatically displays the Transaction Output window during transaction execution. |
Putback |
If you select Auto Bringover Update, and a Putback transaction is blocked, Configuring automatically initiates a Bringover transaction to update the child workspace. |
The Resolve pane of the Tool Properties window enables you to change the behavior of the Resolve pane of the Transactions window. The specific properties are described in Table 6-4.
Property |
Description |
---|---|
Auto Start Merging Window |
Causes Merging to start automatically when the Resolve transaction pane is chosen. |
Auto Advance |
Causes the next file in the list to be automatically loaded into Merging after the current file is resolved. |
Prompt for Checkin Comments |
A default comment is automatically supplied during checkin after you resolve a file. This property causes you to be prompted for an additional comment that is appended to the standard comment. |
Use Existing Merging Window |
If this property is set, an already running Merging process is reused during subsequent resolve operations. |
Auto Save (when no unresolved diffs) |
If this property is set, and all the changes in the file can be "automerged," the files will also be saved and checked in; you need not select the Merging Save button. |
Table 6-5 summarizes the keyboard shortcuts available for Configuring functions.
Table 6-5 Configuring Keyboard Shortcuts
Accelerator |
Action |
Where to Find More Information |
---|---|---|
Drag and drop workspace icon |
Activate Bringover/Putback transaction window | |
SHIFT+drag and drop workspace icon |
Reparent workspace | |
Click workspace icon name field |
Rename workspace | |
Double-click workspace icon |
Launch a tool. User configurable, Versioning is the default | |
Double-click icon of a workspace that contains conflicts |
Launch a tool. User configurable, Resolve window is the default |