Sun WorkShop TeamWare User's Guide HomeContentsPreviousNextIndex


Chapter 11

Sun WorkShop TeamWare Shortcuts

Sun WorkShop TeamWare provides several shortcuts to make it easier to use. This chapter discusses the following topics:

Accessing TeamWare From the Command Line

In addition to working with Sun WorkShop TeamWare tools through the graphical user interface (GUI), you can also type TeamWare commands at any system prompt. You can access Sun WorkShop TeamWare commands through the GUI and at the command line, and both can be used interchangeably. You can simultaneously use the GUI for some functions and work at the command line for others. You can include these commands in scripts or programs to further automate your file management.

Configuring Commands

To see a list of Configuring commands, type codemgr.

example% codemgr
	 	 	 bringover ...
	 	 	 codemgrtool
	 	 	 help	 
	 	 	 putback ...
	 	 	 resolve ...
	 	 	 workspace ....
	 	 	 ws_undo  ....

This list includes the syntax of each command with command options enclosed in square brackets. For example, here is the syntax of the bringover command:

bringover [-w child_ws] [-p parent_ws] [-c comment] 
[-m comment_file] [[-f flp]...] [-n] [-g] [-q] [-v] [-B] [-C] 
[files and dirs]

Here's how you could issue a bringover command at the command line:

% bringover -w my_child -p their_parent /usr/ws/project 

Sun WorkShop TeamWare tools provide several ways to reduce typing long command lines, including environment variables and argument files that store previously specified arguments. To get a detailed listing of the command and the options you can use with the command, type man <commandname>, for example:

% man bringover


Note – Because Sun WorkShop product man pages do not install into the standard
/usr/share/man directories, you must change your MANPATH environment variable to enable access to Sun WorkShop TeamWare man pages. See Access to Sun WorkShop Development Tools.

TABLE 11-1 lists often-used Configuring menu items and their corresponding commands.

TABLE 11-1   Configuring Menu Items and Corresponding Commands
GUI Menu Item Corresponding Command
Create Workspace workspace create
Rename workspace move
Parent workspace parent
Bringover Create bringover
Bringover Update bringover
Putback putback
Undo ws_undo
Resolve resolve


To make a workspace the default for command line commands, set the CODEMGR_WS environment variable. See Configuring Environment Variables.

Versioning Commands

To start Versioning from the command line, type twversion followed by the ampersand (&):

demo% twversion &

Merging Commands

To start Merging from the command line without loading any input files (assuming that the Merging executable is in your search path), at a shell command prompt, type twmerge followed by the ampersand (&):

demo% twmerge &

The twmerge command starts Merging (in the background) without loading any files. To start Merging with files loaded in each window, see Loading Two Files at Startup.

The complete twmerge command is summarized below, with command options enclosed in square brackets.

twmerge [-b] [-r] [-tabsize number] [-diffopt [bwi]] 
[-a  ancestor] [-f1  name1] [-f2  name2] 
[-l listfile] [  leftfile rightfile [outfile]  ] [-V]

Loading Two Files at Startup

To load two files at the time you start Merging from the command line, change to the directory in which the files are stored and specify the file names on the command line. To merge two files named file_1 and file_2, use the following command:

demo% twmerge file_1 file_2 &

The first file listed appears in the left text pane; the second file appears in the right pane.

Loading Three Files at Startup

To merge the same two files and at the same time compare them to a common ancestor named ancestor_file, change to the directory in which the files are stored and use the following command:

demo% twmerge -a ancestor_file file_1 file_2 &

The ancestor file is not displayed, but differences between the ancestor file and the two descendants are marked, and the merged output file is based on the ancestor file.

Freezepoint Commands

You can create, update, and extract freezepoints at the command line. To see a list of Freezepoint commands, type freezept

example% freezept
	 	 	 compare ...
	 	 	 create ...
	 	 	 diff ...
	 	 	 extract ...
	 	 	 help	 
	 	 	 sid ...
	 	 	 smid ...
	 	 	 update  ....

.

For information about using Freezepoint from the command line, see the freezept man page

% man freezept

. Type:

GUI Shortcuts

There are several shortcuts built into the Sun WorkShop TeamWare interface. This is true for selecting workspaces, directories and files:

TABLE 11-2 lists other Sun WorkShop TeamWare mouse and keyboard shortcuts.

TABLE 11-2   Mouse and Keyboard Shortcuts 
Action Result For More Information
Drag and drop workspace icon on an open area. Displays Bringover Create Transaction dialog box.
Drag and drop parent workspace icon on a child workspace icon. Displays Bringover Update tab in the transaction dialog box.
Drag and drop child workspace icon on a parent workspace icon. Displays Putback tab in the Transaction dialog box.
Drag and drop workspace icon on an unrelated workspace icon. Displays a pop-up dialog box asking if you want to perform a bringover or a putback.
Control+drag and drop workspace icon on another workspace. Reparents workspace. Reparenting a Workspace.
Control+drag and drop workspace icon on an open area. Orphans workspace. Reparenting a Workspace.
Click workspace icon name field. Renames workspace.
Click right mouse button in Configuring. Displays a combination menu of File, Workspace and Transaction menus.
Press Props key in Configuring on empty area. Displays CodeManager tab of Tool Properties dialog box. Customizing Configuring Using Tool Properties.
Press Props key in Configuring with a workspace selected. Displays Workspace Properties dialog box. Customizing Configuring Using Tool Properties.
Double-click workspace icon in Configuring. Launches a tool. User configurable, Versioning is the default. Double-Click Actions in Configuring.
Double-click icon of a workspace that contains conflicts. Launches a tool. User configurable, Resolve window is the default. Double-Click Actions in Configuring.
Double-click on file icon in Versioning. Checks out the file or displays file history; user configurable. Double-Click Actions in Configuring.
Double-click on delta in Versioning File History. Displays the delta in your default editor. Double-Click Actions in Configuring.
Click right mouse button in Versioning. Displays a combination menu of Select Files and commands menu.
Click right mouse button in Versioning File History. Displays a combination menu of the Version menu and Merge Branches. Viewing File History.
Click right mouse button in Merging. Displays the Navigate menu. Resolving Differences.


Double-Click Actions in Configuring

When you double-click with the pointer over a workspace icon, the TeamWare Versioning is automatically started (with the selected workspace automatically loaded). If you double-click when the pointer is over the icon of a workspace that contains unresolved conflicts, Configuring automatically activates the Resolve tab. 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 FIGURE 3-7).

Double-Click Actions in Versioning

By default, double-clicking on a file in the Versioning window "toggles" the state of the file, that is, it will check out the file, or if the file is already checked out, it will check in the file. You can change the double-click action to display the file history instead in Versioning Options (View Options, General Tab). See Changing Versioning Properties.

Double-Click Action File History

Double-clicking on a delta in the Versioning File History window displays the delta in your default editor.


Sun Microsystems, Inc.
Copyright information. All rights reserved.
Feedback
Library   |   Contents   |   Previous   |   Next   |   Index