Sun WorkShop TeamWare: User's Guide: 6 - TeamWare Configuring User Interfaces

# TeamWare Configuring User Interfaces | # 6 |

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 manual pages. The remainder of this chapter is an introduction to the Configuring CLI and GUI.

This chapter is organized as follows:

TeamWare Configuring Command-Line Interface | page 52
TeamWare Configuring Graphical User Interface | page 53
Starting TeamWare Configuring | page 53

## TeamWare Configuring Command-Line Interface

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` enables you to list Configuring commands (Code Example 6-1). You can list Configuring commands with their use summaries by executing teamwarewithout specifying any arguments. You can achieve the same results by executing `codemgr` with the `help` subcommand.

Code Example 6-1 `codemgr` Umbrella Command
    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

> Note - You must use the individual command name when you access TeamWare manual 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 manual pages for details.

## TeamWare Configuring Graphical User Interface

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.

> Note - 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.

## Starting TeamWare Configuring

To start TeamWare Configuring, at a shell command prompt type `twconfig` followed by the ampersand symbol (`&`) as shown. After a moment, the Configuring window appears.

    demo% twconfig &
    demo%

### TeamWare Configuring Windows

Configuring consists of a base window and a number of pop-up windows. Within this base window is a menu bar from which you can choose commands, menu items, and window items to help you accomplish your tasks. The online Help contains a full explanation of TeamWare Configuring Windows.

You navigate the file system with point-and-click windows. Select files and directories by moving the mouse pointer over icons and clicking SELECT. You can make multiple selections using two different methods:

- Use the ADJUST mouse button to extend the selection to multiple files or directories.

- Press SELECT in an open area of the pane and drag a bounding box diagonally until the desired group of icons is enclosed, then release SELECT.

When you make your selection, select the button at the bottom of the chooser window to make your choice effective. You can also choose a file or directory by typing its name in the Name text field and selecting the Add Files to List button (or typing Return).

You can navigate down through the file system hierarchy by double-clicking SELECT on any directory icon. To move hierarchically upward, double-click SELECT on the directory icon. To move directly to a directory, enter its path name in the Name text field and select the Load Directory button.

> Note - Mouse button action is different in the Motif/CDE interfaces. To make a selection, click the left mouse button to select the first item, then extend the selection by clicking the left mouse button on another item while pressing the Shift key (this action is called Shift-SELECT). If you press Shift-SELECT on an item that is already selected, that item is deselected.

> Note - A check mark in a file icon indicates that the file is checked out from SCCS.

### Configuring Window

When you start the Configuring program, the base window appears. 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.

#### Workspace Graph Pane

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.

##### Loading Workspaces into the Workspace Graph Pane

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, use the Load Workspaces window from the File menu.

##### Layout

Workspace hierarchy graphs are automatically created in the Workspace Graph pane by the Configuring program as you load workspaces (using the Load menu). Hierarchies are displayed either vertically or horizontally starting from the upper-left corner and distributed to the right as space permits. You can choose the orientation using the Orientation item form the View menu. Vertical orientation is the default. Layout is done automatically--you are not able to change the layout by moving icons with the mouse.

##### Workspace Name Fields

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 using the Name item from the View menu.

You can change the path name of a workspace by editing the name text field.

##### Dragging and Dropping Workspace Icons

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, the Configuringprogram will initiate 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 "Copying Files between Workspaces" on page 83.

  #### Table 6-1 Workspace Drag and Drop Action

  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 select and 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" on page 66.

> Note - You are prompted to confirm the reparent operation.

##### Double-Click Action

When you double-click the SELECT mouse button when the pointer is over a workspace icon, the TeamWare utility Versioning is automatically started (with the selected workspace automatically loaded). See Versioning online Help and the section in this manual on Versioning for instructions on using Versioning.

If you double-click SELECT 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 Configuring pop-up window under the Properties button.

#### Configuring Window Control Area

See online Help for detailed descriptions of Configuring Windows.

### Customizing the Configuring Program Using Properties

Using the Tool Properties window, you can customize the behavior of:

- Configuring window functions
- Bringover/Putback transactions
- Resolve transaction

You activate the Tool Properties window by choosing the Configuring item from the Options menu. The Category menu on the Properties window enables you to switch between the Configuring, Bringover/Putback, and Resolve panes.

#### Configuring Defaults Files

When you change Configuring behavior using the Tool Properties window, you can use the Set Default button to preserve the changes in defaults files in your home directory. The defaults files are consulted by Configuring when it is started, your changes are used as the default values.

Changes made in the Resolve pane of the Tool Properties window are written to the file ~`/.codemgr_resrc`. This file is a standard SunOS runtime configuration file.

Changes made in the Configuring and Bringover/Putback panes of the Tool Properties window are written to the file ~/`.codemgrtoolrc`. This file is an OpenWindows XDefaults format file.

#### Configuring Pane

The Configuring pane of the Tool Properties window enables you to change the behavior of the Configuring base window. The specific properties are described in Table 6-2.

#### Table 6-2 Configuring Tool Properties

Property | Description
Default Directory | Directory to which Configuring actions are relative.
Double-click Action | Specify the commands you want launched when you double-click SELECT on: standard workspace icons, icons of workspaces that contain conflicts. Specify the path names required to execute the commands based on the current working directory and your search path. By default, the standard workspace command is Versioning (`vertool`); by default, the Resolve Transaction window (<resolve_pane>) is activated 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 | Choose the Horizontal setting if you want the workspace hierarchy displayed horizontally from left to right in the Workspace Graph pane. Choose 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 Orientation item on the View menu in the main Configuring window.
Workspace Names | Choose the Short setting if you want workspaces labelled with the shortest possible name in the Workspace Graph pane. Choose Full if you want workspaces labelled with absolute path names. By default the Full setting is in effect. This property corresponds to the Names item on the View menu in the main Configuring window.

#### Bringover/Putback Pane

The Bringover/Putback pane of the Tool Properties window 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.

#### Table 6-3 Bringover/Putback Tool Properties

Property | Description
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.
Auto Display | Automatically displays the Transaction Output window during transaction execution.
Auto Bringover Update | If a Putback transaction is blocked, automatically initiates a Bringover transaction to update the child workspace.

#### Resolve Pane

The Resolve pane of the Tool Properties window enables you to change the behavior of the Resolve pane of the Transaction window. The specific properties are described in Table 6-4.

#### Table 6-4 Resolve Tool Properties

Property | Description
Start Merging (auto load) | Causes Merging(FileMerge) 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 | 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.

### Accelerators

Table 6-5 summarizes the various accelerators available for Configuring functions.

#### Table 6-5 Summary of Configuring Accelerators

Accelerator | Action | Where to Find More Information
Drag and drop workspace icon | Activate Bringover/Putback transaction window | "Dragging and Dropping Workspace Icons"
SHIFT + drag and drop workspace icon | Reparent workspace | "Dragging and Dropping Workspace Icons"
Click SELECT on workspace icon name field | Rename workspace | "Workspace Name Fields"
Double-click SELECT on workspace icon | Launch a tool. User configurable, Versioning is the default | ""Double-Click Action"
Double-click SELECT on an icon of a workspace that contains conflicts | Launch a tool. User configurable, Resolve window is the default | "Double-Click Action"