This section describes how to configure character application objects. Terminal emulator mappings are also discussed.
This section includes the following topics:
You use a character application object if you want to give a VT420, Wyse 60, or SCO Console character application to users.
In the Administration Console, the configuration settings for character application objects are divided into the following tabs:
General tab – These settings control the name and the icon used when creating links for users
Launch tab – These settings control how the application is started and whether application sessions can be suspended and resumed
Presentation tab – These settings control how the application is displayed to users
Performance tab – These settings are used to optimize the performance of the application
Client Device tab – These settings control how the user’s client device interacts with the application
The following table lists the most commonly used settings for configuring character application objects and how to use them.
To use and display the euro character, the terminal session must be capable of displaying 8-bit characters. To ensure this, enter the command stty -istrip. Also, the client device must be capable of entering the euro character.
On the command line, you create a character application object with the tarantella object new_charapp command. You can also create multiple character application objects at the same time with the tarantella object script command. See Populating the SGD Organizational Hierarchy Using a Batch Script.
Character application objects can only be created in the o=applications organizational hierarchy.
The SGD terminal emulators associate keys on the user’s client keyboard with keys found on a real terminal. For each type of terminal emulator: SCO Console, Wyse 60, and VT420, there is a default keyboard mapping.
To change the default mappings or define additional mappings for a particular application, you can specify your own keyboard map file using an object’s Keyboard Map attribute.
The emulators have built-in keyboard maps, which are equivalent to the following sample keymap files in the /opt/tarantella/etc/data/keymaps directory:
ansikey.txt – For the SCO Console emulator
vt420key.txt – For the VT420 emulator
w60key.txt – For the Wyse 60 emulator
Note - Modifying these keyboard maps does not alter the default mappings used by SGD. The only way to do this is to specify a keyboard map in an application object’s Keyboard Map attribute.
To create your own keyboard map, make a copy of one of the sample keyboard map files, and modify it to suit your application. You can modify a keyboard map in any text editor.
The format of a mapping is:
Where ClientKeys is the key, or keys, that the user presses on the client device, and Translation is the keystroke, or keystrokes, sent to the application on the application server. For example:
With this mapping, when the user presses the Page Down key the emulator sends the keystroke Next to the application server.
If a particular key has a user-defined mapping, the default settings are overridden. If no user-defined mapping is present, the default mapping is sent to the application server.
You can send complete strings on a single key press, by surrounding the string in straight quotation marks. For example:
To enter non-printable characters when mapping strings, use the code shown in the table below:
To specify modifier keys, such as Shift, Control, and Alt, in a mapping, separate the keys with the plus sign, +. For example:
Shift+NUMLOCK=INSLINE Shift+F1="\0330a" Alt+Shift+Control+DELETE="\003[33~"
The following are lists of key names that are valid in SGD keyboard maps. The Client Device Keys list shows the key names that represent keys on the user’s client device. These are the keys that can be mapped to the emulator key names given in Application Server Keystrokes, which are the keystrokes ultimately sent to the application on the application server.
Note - The default mappings between these key names are as found in the keyboard maps supplied with SGD. If a key is not in a keyboard map, then it is not mapped.
SGD supports the following keys on the user’s client device:
F1 to F12
KP0 to KP9
The following application server keystrokes are supported for SCO Console applications:
F1 to F12
KP0 to KP9
The following application server keystrokes are supported for VT420 applications:
F1 to F20
KP0 to KP9
PF1 to PF4
The following application server keystrokes are supported for Wyse 60 applications:
F1 to F16
KP0 to KP9
Terminal emulator attribute maps enable you to change how character attributes such as bold or underline are displayed in the SGD terminal emulators. For example, you can specify that text that normally appears bold and underlined appears red in the SGD terminal emulators, but not red and bold and underlined.
SGD provides a default attribute map /opt/tarantella/etc/data/attrmap.txt. This maps character attributes to the logical color Color_15 (white). You can also create your own attribute map.
The SGD attribute maps enable you to map the following attributes:
To map combinations of attributes, separate the attributes with the plus sign +, for example, Bold+Underline.
To display colors in the terminal emulators, SGD maps logical colors to RGB values. For example, the logical color Color_9 maps to the RGB value 128 0 0 (red).
When mapping attributes to colors in your attribute map, specify the logical color name. For example:
To change bold underlined text to red text:
To change inverse blinking text to light red text:
For a complete list of logical color to RGB value mappings, refer to the comments in attrmap.txt.
You can change the default color mappings by editing the color map used by the terminal emulators. See Terminal Emulator Color Maps.
Note - Wyse 60 terminals display only black and white colors. However, you can use the SGD Wyse 60 terminal emulator to display colors in your Wyse 60 applications. You can do this by using the attribute map to map character attributes in the Wyse 60 application to colors.
SCO Console (ANSI) and VT420 terminals support 16 colors. The SGD terminal emulator uses a color map to determine how these colors are presented in an application session.
Note - Wyse 60 terminals are monochrome. You can only switch the background and foreground colors, black and white, using the color map. However, you can map character attributes such as bold or underline to any of the 16 logical colors supported by the terminal emulator. See Terminal Emulator Attribute Maps.
The color map maps the logical colors Color_0 through to Color_15, inclusive, to colors and the RGB values that SGD uses to represent those colors. The default mappings are as follows:
To alter the defaults for a particular application, create your own color map, and specify it in the application object’s Color Map attribute.
A default text-format color map /opt/tarantella/etc/data/colormap.txt is provided.
To make the color red brighter, change the RGB setting of Color_9 to 192 0 0.
To change items that appear in light green to appear yellow, change the RGB setting of Color_2 to 255 255 0, the RGB value of yellow.
One common color change is to switch the foreground and background colors between black and white. When you do this, you are not changing the foreground or background color as such, you are changing the way black (Color_0) and white (Color_15) are displayed. Therefore, if your application has a white background and you want to change it to a black background, change the value of Color_15 to 0 0 0, the RGB value of black.