schemes
X Window System resources for VersionVault Graphical User Interfaces (GUIs)
Applicability
Product |
Command type |
---|---|
VersionVault |
data structure |
Platform |
---|
UNIX® |
Linux® |
Synopsis
VersionVault GUIs use Common Desktop Environment (CDE) settings or can read scheme files.
Description
Scheme files are collections of X Window System resource settings that control the geometry, colors, and fonts used by application GUIs. By default, VersionVault does not enable schemes. Instead, the GUIs use the settings that your Common Desktop Environment (CDE) specifies. However, you can enable schemes and use the VersionVault schemes mechanism by adding the following resource to your .Xdefaults file:
*useSchemes: all
All VersionVault GUIs except the following support the schemes mechanism:
- cleardescribe
- clearhistory
Each scheme is implemented as a separate directory. For example, the scheme Turner consists of four files:
Turner/palette |
Defines mnemonic names for colors and fonts, using a subset of standard cpp(1) syntax: #ifndef GAMMA_1_0 #define TextForeground #fffff #define BasicBackground #002e5c #define ScrolledListBackground #623463 . . . |
Turner/Turner |
Specifies resources for use by the X Toolkit widgets that make up the GUI panels. These resources can be specified absolutely, or in terms of the mnemonic names defined in the palette file: *XmText*marginHeight: 4 . . . *foreground: TextForeground *background: BasicBackground |
Turner/VersionVaultpalette |
Extends or overrides the standard palette definitions |
Turner/VersionVault |
Extends and/or overrides the standard Turner file definitions |
The two mnemonic map declaration files are combined, as are the two resource definition files. If the same resource is specified in the standard file and the VersionVault file, the specification in the VersionVault file is used. To add your own definitions or to replace existing ones, either edit one or both of the files specific to VersionVault or create your own scheme files and specify a scheme file search path, as described in the section Search path for schemes.
Note that the palette and VersionVaultPalette files are not actually processed by cpp; they are processed by the VersionVault GUI itself. The resources (Turner and VersionVault) apply only to the program that reads them. They are not added to the RESOURCE_MANAGER property of the root window and, therefore, do not affect other X applications.
Schemes are configured at two levels:
- Your display's X resources enable scheme use and specify the name of a particular scheme.
- A search path capability supports maintenance of systemwide and personal schemes.
Resources for schemes
The scheme resource specifies a scheme to be used by the VersionVault GUI. For example:
*scheme: Turner |
Specifies scheme for all GUI utilities |
|
Specifies scheme for |
If you enable scheme use but do not specify a particular scheme, the color scheme Lascaux or the black-and-white scheme Willis is used. If you do not explicitly enable schemes, the CDE resource settings are used.
Monochrome and grayscale schemes
By default, users working on a monochrome monitor get the Willis scheme, and users working on a grayscale monitor gets the Print scheme. You can override these assignments with the resources *monoScheme and *grayScheme, respectively. If you specify an alternative scheme, it must be located in the scheme search path, which is described in the following section.
Search path for schemes
The GUIs use a search path to find scheme directories. The default
search path is /usr/lib/X11/Schemes:/opt/hcl/ccm/versionvault/config/ui/Schemes
.
You can use the environment variable SCHEMESEARCHPATH to specify a colon-separated list of directories to be searched instead. Each entry on this list must be in the following standard X Toolkit form:
- pathname/%T/%N%S
The GUIs always make these substitutions:
- %T: Schemes
- %N:scheme-name
- %S: (null)
For example, if your SCHEMESEARCHPATH value is
/netwide/config/ui/%T/%N%S:/home/gomez/%T/%N%S
and your .Xdefaults file includes the line
*scheme: Rembrandt
then the GUI reads resource schemes from these two directories:
/netwide/config/ui/Schemes/Rembrandt /home/gomez/Schemes/Rembrandt
The GUI searches for the first instance of each scheme file (the standard map declaration file, the standard resource definition file, and the versions of the standard files), and then concatenates the files.
International language support
If your site uses the language resource *xnlLanguage to implement pathname substitutions based on national language and/or codeset, you may want to expand customized SCHEMESEARCHPATH entries to use one or more of these optional substitution parameters:
- %L: Value of *xnlLanguage (language[_territory][.codeset])
- %l: language
- %t: territory (if any)
- %c: codeset (if any)
For more information about constructing directory trees to store language-dependent application text files, see X Windows® System Toolkit documentation.
Platform-specific support
On some platforms, there are specific requirements for the location of the Schemes directory. For information about platform-specific requirements, see the Release Notes.
Files
- versionvault-home-dir/config/ui/Schemes/Gainsborough/*
- versionvault-home-dir/config/ui/Schemes/Lascaux/*
- versionvault-home-dir/config/ui/Schemes/Leonardo/*
- versionvault-home-dir/config/ui/Schemes/Monet/*
- versionvault-home-dir/config/ui/Schemes/Print/*
- versionvault-home-dir/config/ui/Schemes/Rembrandt/*
- versionvault-home-dir/config/ui/Schemes/Sargent/*
- versionvault-home-dir/config/ui/Schemes/Titian/*
- versionvault-home-dir/config/ui/Schemes/Turner/*
- versionvault-home-dir/config/ui/Schemes/VanGogh/*
- versionvault-home-dir/config/ui/Schemes/Whistler/*
- versionvault-home-dir/config/ui/Schemes/Willis/*
See also
cleardescribe, clearhistory, cpp(1), X Toolkit documentation, Common Desktop Environment documentation