|
|
|
|
$RAZOR_HOME/examples/Xdefaults.sample
... may be copied and referenced as necessary to form your own set of Xdefaults.
The tables below detail a subset of the many options discussed in the sample file. They represent some of the more useful resources, and are grouped to highlight various themes. For a full and accurate description, we encourage you to refer to the file itself.
In the tables, the left column is the resource specification, the center column shows the default resource value, and the right column indicates whether or not the resource is honored by the PC clients. Those resources honored by the PC clients will be marked with a `w' and are contained in the file Wdefaults located in the $RAZOR_UNIVERSE_DIR directory.
The following sets the foreground and background for the issues, versions and threads interfaces.
A table exists which lists all sorts of colors by name, and relates them to the various intensity levels.
On Sun's running OpenWindows, consult the file $OPENWINHOME/lib/rgb.txtand on other UNIX systems, consult the file /usr/lib/X11/rgb.txt.
Issues*fontList Versions*fontList Threads*fontList | -*-helvetica-bold-r- normal--12-* | |
Issues*FilterForm*fontList Versions*FilterForm*fontList Threads*FilterForm*fontList | -*-helvetica-bold-r- normal-*-12-* | |
Issues*XmList.fontList Versions*XmList.fontList Threads*XmList.fontList | -*-courier-bold-r-normal-- 12-* | |
Versions*Diff*Text.fontList Threads*DiffText.fontList | -*-courier-medium-r- normal--10-* | |
Issues*ReportText*fontList | -*-courier-bold-r-normal- *-12-* | |
Versions*Browse*Text.fontList Versions*FileInfo*Text.fontList Versions*PromoteForm*fontList Versions*State*Text.fontList Versions*Errors*Text.fontList Issues*Errors*Text.fontList Threads*Errors*Text.fontList | -*-courier-bold-r-normal-- 12-* | |
Issues*FormWorkArea*fontList Threads*CreateForm*fontList | -*-helvetica-bold-r- normal-*-12-* | |
Issues*IssueForm*XmText.fontList1 | -*-courier-medium-r- normal--12-* | |
Issues*ListFont Version*ListFont Threads*ListFont | -*-courier-bold-r-normal-- 12-* | |
Issues.IssueForm*Text1.fontList Issues.IssueForm*Text2.fontList | -*-courier-bold-r-normal-- 12-* -*-courier-bold-r-normal-- 12-* |
| 1
The font used by the two text widgets at the bottom of the issue form are fixed width. Take note that the size (width) of this font controls the overall width of an issue form.
|
It's possible to set the initial value for various display and filter toggles. The values shown in the following table are the programmatic defaults, where a value of `0' means off, and `1' means on. (You can also use the strings `True' and `False,' if you prefer.).
Many users prefer that text (and text field) widgets behave in a manner other than the default provided by Motif. What follows is a set of examples of some things that can be set and how this would be done. The action functions shown are pretty much self-explanatory. Try them out and pick the ones you like. The examples are shown for the issues program, but can be applied to versions, threads or any other interface. Removing the leading `Issues' from the translation definition will cause the definitions to take effect for all text widgets, not just those used by Razor.
It can prove extremely useful to be able to take the output of a command and insert it into a text or text field widget. If text is selected, the text will be replaced by the output of the command. Razor provides this capability through the razor-cmd() action.
What follows are several convenient settings for the Text widget along with an example of how to define the F2 key to place the current date into the widget. Also shown is an example of how to define the F3 key to execute `fmt' on the selected text.
Issues*XmText.translations:#override\n\
Ctrl<Key>u: delete-to-start-of-line()\n\
Ctrl<Key>e: end-of-line()\n\
Ctrl<Key>a: beginning-of-line()\n\
Ctrl<Key>w: forward-word()\n\
<Key>L6: copy-clipboard()\n\
<Key>L8: paste-clipboard()\n\
<Key>L10: cut-clipboard()\n\
Ctrl<Key>w: delete-word()\n\
Shift Ctrl<Key>e: end-of-line()\n\
Shift<Key>Delete: delete-next-character()\n\
<Key>osfDelete: delete-previous-character()\n\
<Key>F2: razor-cmd("echo -n `date +%y/%m/%d`")\n\
<Key>F3: razor-cmd("fmt")\n
The Xdefaults.sample file included with the Razor release also documents a fairly complete collection of bindings which allow text widgets to closely emulate the behavior of Emacs. Please refer directly to the above file if this interests you.
It's occasionally handy to set these to something a bit more descriptive, especially when you may have multiple databases running at your site.
Issues*title Issues*iconName | Issues Issues | w |
Versions*title Versions*iconName | Versions Versions | w |
Threads*title Threads*iconName | Threads Threads | w |
If control over the number of rows/columns the diff utility is required, use the following resources.
Versions.Diff*DiffText.columns Versions.Diff*DiffText.rows | 180 40 | |
Threads*DiffText.columns Threads*DiffText.rows | 100 15 |
The work area on the issue form which contains the configurable attributes is defined as FormWorkArea. Its height is set and may be changed to meet user preference. The number of rows used by the two text panes at the bottom of the issue form may also be defined.To configure the issue form for an issues group other than the default issues group, append the issue group name to `IssueForm' in the resource specification. For example, setting issue form height for issue group `dev' could be done with resource setting `Issues*IssueFormdev*TextForm1.height:400'.
Issues.IssueForm*TextForm1.height Issues.IssueForm*TextForm2.height | 100 100 |
Note that the overall initial width of the issue form is controlled by the amount of space required to display 80 characters in the two text widgets. To increase or decrease the initial width, you need to specify a different font for that area.
The text panes on the issues text will automatically scroll to the bottom when a form is displayed. This behavior can be overridden.
Issues.problemToBottom Issues.solutionToBottom | False True | w w |
Scrolling and word-wrapping can also be controlled in the two text areas.
Issues*Text1.wordWrap Issues*Text1.scrollHorizontal Issues*Text2.wordWrap Issues*Text2.scrollHorizontal | True False True False |
The ability to relate issues to file operations can be disabled by not having any file groups or via an X resource setting.
Issues.enableDnd Issues.enableCopy | True True |
When populating an issue form with widgets, the issues program will start 10 pixels from the top of the form, with a gap of 10 pixels between the widgets. The default behavior is to have all labels be fixed width based on the longest label. Some users may prefer to modify these values to provide a tighter or looser appearance.
Issues.IssueForm*Workform.populateOffset Issues.IssueForm*Workform.initialOffset | 10 10 | w w |
Left to its own, the issues program will strive to keep an accurate list of issues on the display. Each time the database server receives a change, it notifies all of the other running issues programs, and each in turn will update its display. It is possible to prevent this from happening while you are actively editing an issue.
Issues.updateDuringModify | True | w |
Users who wish to change the length of the STATE name string to accommodate long (or short) STATE names when they are displayed on the issue form, can do so through the setting of an X resource.
Issues.stateNameLen | 15 |
If using multiple issues groups, the default issues group shown in the Group pulldown is shown as -Issues-. Some users may prefer to modify this value to provide a different appearance.1
Issues.defaultGroupString | -Issues- | w |
Users of the text editor vi are accustomed to hitting the <ESC> key while entering text. Unfortunately, the default action of that key in Razor programs is to dismiss the window. Its possible to override that behavior in the issues program by setting the following resource...
Issues.ignoreEscape | True |
The number of columns used to display groups in the issues groups pulldown is defined as follows: a value of 0 means the program will compute the number of columns automatically, while a non-zero value will be honored as defined.
Issues.groupColumns | 0 | w |
You may control the double-click interval time for the issues main list. The interval is in milliseconds.
Issues.listDoubleClickTime | 500 |
The legal values are: NO_LINE, SINGLE_LINE, DOUBLE_LINE, SINGLE_DASHED_LINE, SHADOW_ETCHED_IN, SHADOW_ETCHED_OUT
Issues*ReportSep.separatorType | SHADOW_ETCHED_IN |
A visual separator may be added in the pull-down lists for Commands and Reports using the following resource.
The legal values are: NO_LINE, SINGLE_LINE, DOUBLE_LINE, SINGLE_DASHED_LINE, SHADOW_ETCHED_IN, SHADOW_ETCHED_OUT
Issues*ReportSep.separatorType | SHADOW_ETCHED_IN |
The number of characters to use when displaying file names in versions can be controlled by...
Versions.filenameLength | 32 | w |
Binary introductions can be controlled with...
Versions*Introduce*BinaryRC.Binary.set Versions*Introduce*BinaryRC.Auto-detect.set | False False1 | w w |
| 1
Razor's PC Client will only allow Binary or Auto-detect to be selected, you must have one selected - unlike the UNIX client. By default Auto-detect is set to true in the Wdefaults file.
|
The check-in dialog allows users to specify the action to take on files which are being checked in. The choices are "Take the files", "Leave a read-only copy", and "Check files back out for edit". The default selection can be controlled through one of the following X resources. Remember that only one of them can be set to True.
Versions*FileControl.TakeFiles*set Versions*FileControl.LeaveReadonly*set Versions*FileControl.CheckOut*set | False True False | w w w |
You can control the output path for versions as being absolute or relative.
Versions*AbsolutePath.set | False | w |
There's even an X resource which forces the immediate deletion of the backup files (...filename) which are created during the check-in and introduction operations. This option does not effect command line check-ins or introductions - they always make a backup.
Versions.makeBackup | True | w |
You can control whether the check-in title information will be the same for all files or what was originally entered for each file at check-out...
Versions*OrigInfo.set | 0 | w |
The number of columns used to display groups in the Versions groups pulldown is defined as the following, (a value of 0 indicates program computed, non-zero will be honored as defined).
Versions.groupColumns | 0 | w |
You may control the double-click interval time for the versions main list. The interval is in milliseconds.
Versions.listDoubleClickTime | 500 |
You may control the behavior of the Versions diff output with the following three resources. You should set only one of these values to True.
Versions*ShowAll.set Versions*NoIdenticalLines.set Versions*OnlyLeftSide.set | True False False |
If control over the number of rows/columns the diff utility is required, use the following resources.
Versions.Diff*DiffText.columns Versions.Diff*DiffText.rows | 180 40 |
Versions merge colors can be controlled with the following resources.
The Commands text pane scrolling and word-wrap attributes can be controlled as follows.
Versions*Commands*XmText.wordWrap Versions*Commands*XmText.scrollHorizontal | True False |
The number of characters to use when displaying file names in threads can be controlled by...
Threads.filenameLength Threads.threadnameLength | 32 32 |
The following controls the minimum/starting height of the center area of the paned window:
Threads*IssueListPane.IssueFileActions.paneMinimum | 100 |
The following controls whether the inclusion of files may be based only on issue relationships:
Threads*onlyFromIssues | 0 | w |
The following controls whether changes can be made after file inclusion has been changed via the issue selection dialog:
Threads*allowChangesAfterIssueInclusion | 0 | w |
The number of columns used to display groups in the threads groups pulldown is defined as follows: a value of 0 means the program will compute it automatically, while a non-zero value will be honored as defined.
Threads.groupColumns | 0 | w |
You may control the double-click interval time for the threads main list. The interval is in milliseconds.
Threads.listDoubleClickTime | 500 |
If control over the number of rows/columns the diff utility is required, use the following resources.
Threads*DiffText.columns Threads*DiffText.rows | 100 15 |
The following controls the initial setting for thread file selection criteria for branched files, as set in the Edit Threads Selections pulldown.
Threads*SelectionsPulldown.SelectOne.set Threads*SelectionsPulldown.SelectAny.set | 1 0 | w w |
The following controls the sensitivity setting (whether or not the option can be selected) for thread file selection of branched files. Changing the value to 0 makes the option not selectable.
Threads*SelectionsPulldown.SelectOne.sensitive Threads*SelectionsPulldown.SelectAny.sensitive | 1 1 | w w |
The Commands text pane scrolling and word-wrap attributes can be controlled as follows.
Threads*Commands*XmText. wordWrap Threads*Commands*XmText.scrollHorizontal | True False |
When composing email to be sent to Tower Concepts, the default text which appears in the To: Cc: and Subject: fields can be set to something other than the defaults.
*ComposeTo.value *ComposeCc.value *ComposeCommentSubject.value *ComposeLogSubject.value | support@tower.com <empty> Razor Comments Razor Log Output | w w w w |
As strange as it may seem, some users have asked how to hide our friend (and mascot) Occam from the various dialogs which employ his likeness. If set to false, the Tower Concepts logo will appear in his place.
Versions.Status.showOccam: Versions.ErrorLog.showOccam: | True True | w |
|
|
|
|
|
(Part 3 of 3 for this section) (Generated 09/13/99 at 18:19:17) |
|||
|
Copyright Tower Concepts http://www.tower.com Voice: 315-363-8000 Fax: 315-363-7488 support@tower.com sales@tower.com |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
