This document describes jinit.tcl version 4.1/4.2.
* It sets the Tk colormodel to colour if possible (even on displays with only a few colours). The Tk default is to use monochrome if the display supports sixteen colours or fewer, but many displays with as few as four colours have no trouble displaying Tk's 3D effects, so the jstools applications use colour if possible.
* It sets NAME and HOME global variables with the values of the corresponding environment variables.
* It sets the application's `client' and `command' properties for the use of X session managers.
* It reads in the user's global preferences. This is important, as many of the jstools libraries depend on the existence of variables created during this process.
* It tries to load the user's preferred language database for presentation of strings by library routines.
* If app was specified, it also tries to load an applicationspecific language database for presentation of strings used by the application.
* It sets up Text and Entry bindings to use the user's preferred editor emulation, and reads the user's ~/.tk/textbindings.tcl and ~/.tk/entrybindings.tcl, if any.
If you don't want to use j:jstools_init because there's something it does that you don't like, you should refer to the procedure itself to see what you need to do to initialise your application.
* While colour works well for displays with small numbers of shades of grey, it may not work well for all displays with small numbers of actual distinct hues. Ideally, whether to use colour or monochrome would be decided based on the kind of display (e.g. StaticGray vs. DirectColor) as well as on the number of colours, or perhaps it would be a user preference.
* It would be nice if j:jstools_init could handle setting up the
auto_path variable to find the libraries. Since it is itself called
using the autoloading mechanism, of course, it can't.