Basic settings

Overview: global files

Some basic settings are valid for all emulated terminal types and cannot be modified by users. After installation, the corresponding JavaScript files can be found in the auto start directory config/_macro/auto:

• config/_macro/auto/_preferences.js: Settings for the initial start of the emulation window
• config/_macro/auto/_preferences.js: Settings that are restored each time you start the emulation window
• config/_macro/auto/_colors.js: Definition of system colors that users can select
• config/_macro/auto/_hardcopy.js: Settings for hardcopy print

If you want to make changes to a file, first copy the corresponding file from the system directory config/_macro/auto to your custom directory custom/_macro/auto and make your changes there. This enables you to easily apply your customizations when updating to subsequent versions.

Language-specific settings can be made accordingly:

• config/_lang/de/lwtext.js: German text
• config/_lang/en/lwtext.js: English text

Note: These changes are only applied after the cache is refreshed!

In addition to global settings, you can define many terminal-specific settings:

• Templates are used to define the settings of the menuline (menu bar), tool bar, keyboard settings, and mouse settings.
• Auto start macros enable you to change the behavior of the terminal as required.

Initial settings: lwh.pref.initial

The file config/_macro/auto/_preferences.js contains the associative array lwh.pref.initial, which defines the settings that are valid when the emulation window is started for the first time. These settings are also valid if no settings cookie is found when the emulation window is started or if the cookie does not contain the corresponding setting.

Example:

lwh.pref.initial = {
   ...
   "lwt.tips.active":         true,   // tip of the day: show on session start: true/false
   "lwh.pref.pSave":          true,   // auto-save current user preferences on exit: true/false
   "lwh.color.schema.value":  0,      // colors: scheme number, as defined in lwh.color.system
   ...

Note:

• When working, users can access the corresponding menu to change the settings that you made.
• You can avoid these changes by removing the menu items required for these changes.
• Upon exiting the program, the current settings of the user are automatically saved in a cookie on the user's local computer. The settings are re-evaluated when the program is started again.
• Most of the settings are non-critical and are only used to improve usability, such as "Hardcopy of current screen" or "Buffer Input (type ahead)"
  You usually do not change these settings.
• In an emergency, users can use "Delete cache" to restore your default settings.

Permanent settings: lwh.pref.defaults

The file config/_macro/auto/_preferences.js also contains the associative array lwh.pref.defaults, which determines the settings that are valid each time the emulation window is started. These settings are not saved in the cookie.

Example:

• If you delete the line

     ...
     "lwh.pref.pSave":	true,	// auto-save current user preferences on exit: true/false
     ...
  

  from lwh.pref.initial and use the value false for lwh.pref.defaults, settings are not automatically saved in a cookie.

  lwh.pref.defaults = {
     ...
     "lwh.pref.pSave":	false,	// auto-save current user preferences on exit: true/false
     ...
  

• If you also remove the menu item [Options]/[Save Current Settings], you prevent cookies from being written.

Note:

• When working, users can access the corresponding menu to change the settings that you made.
• You can prevent these changes by removing the corresponding menu items.
• The settings lwh.pref.defaults are not saved on the client as cookies when the program is terminated; when the program is restarted, your default settings are re-applied.
• The parameters in lwh.demon.delay should not be changed without careful consideration:
  You control the continuous connection monitoring and thereby enable the secure operation of the terminal emulation, even over connections that are susceptible to interference, such as GSM.

System colors: lwh.color.system

The file config/_macro/auto/_colors.js contains the array lwh.color.system and determines the system colors.
Each line contains the name of the color scheme and RGB values of the 16 available host colors (HTML notation: 2 hex numbers each for the colors red, green und blue).

Example:

lwh.color.system = [
   //    schema name     0=black   1=blue    2=red      3=pink    4=green   5=cyan   6=yellow  7=white   8=gray    9=darkBlu 10=orange 11=purple 12=ligree 13=lityan 14=browVT 15=lgrayVT
   [   "[default 1]",  ["#000000","#1E90FF","#FF0000","#FF00FF","#00FF00","#00FFFF","#FFFF00","#FFFFFF","#4D4D4D","#0000CD","#CD0000","#CD00CD","#00CD00","#008B8B","#FFA500","#e5e5e5"]	],
   [   "[9755 mono]",  ["#000000","#FFFFFF","#ff0000","#FF00FF","#FAF0E6","#FAF0E6","#FAF0E6","#FFFFFF","#4d4d4d","#000000","#cd0000","#cd00cd","#000000","#000000","#000000","#e5e5e5"]	],
   [   "[VT 1]",       ["#000000","#0000FF","#ff0000","#ff00ff","#00ff00","#00ffff","#ffff00","#ffffff","#4d4d4d","#0000cd","#cd0000","#cd00cd","#00cd00","#00cdcd","#cdcd00","#e5e5e5"]	],
   ...
   [   "[gray 1]",     ["#DDDDDD","#0000FF","#FF0000","#FF00FF","#228B22","#00CED1","#A0522D","#000000","#808080","#1E90FF","#FF8C00","#800080","#80ff80","#00FFFF","#FFFF00","#404040"]	]
];

Note:

• The parameter in lwh.color.schema.value (or in lwh.pref.defaults) defines the number of the default color scheme.
• The menu function [Color]/[Color Scheme] enables users to select a color scheme.
• If you do not remove the menu function [Colors]/[Edit Color Scheme], users can create additional color settings. These are saved in a cookie.
  Users cannot change or delete the system colors that you have set.

Language-specific settings: lwtext.js

The file config/_lang/XX/lwtext.js contains language-specific text that are displayed in the statusline (status bar) or in error messages.

If you replace the text in messages with empty strings, the corresponding messages are no longer displayed.

Example:

If you want to switch off the display "received BEL from host", simply replace this text with an empty line:

...
/** if set: message to user: "cannot insert data in filled field. 3270, 5250 only." @type {String} @since 2007-05-12 */
lwt.msgFieldFull     = "cannot insert data in filled field.";
/** if set: message to user: "VT received BEL control char" @type {String} @since 2007-05-10 */
lwt.msgHostBel       = "";   // "received BEL from host";
/** if set: message to user: "Host system is in locked state" @type {String} @since 2007-07-03 */
lwt.msgHostLocked    = "confirm locking of screen with <RESET>";
...

Hardcopy print: lwh.genHC.cb

The file config/_macro/auto/_hardcopy.js contains the function lwh.genHC.cb, which is called up each time the users create a hardcopy of the current screen.
This function enables you to determine the output format.

Example:

If you do not require an entry field at the top of your hardcopy page, you can comment out the corresponding data:

lwh.genHC.cb = function(ctrl) {
   ...lwh.genHC.cb = function(ctrl) {
   ...
   ctrl.screen =
      ...
      /////"<div>" +     // input textarea for user notes
      /////   "<textarea style='height:2em; width:100%'>" +
      /////   "</textarea>" +
      /////"</div>" +
      ...
   ...
};

Host print

You are usually not required to make any changes except to the settings in the file ajax.ini. However, you can extend the functionality of the printer component on the server side and change it according to your specific requirements. Additional information can be found under WebSpool.