2.15. Installation and Operating Environment Interface

Cover in as OS-independent way as possible how to install the system, and how it's invoked from the OS.

2.15.1. Regular User Installation

Want to keep prompts to a minimum. I think these are they, er, this is it:

"Enter the name of the directory where the Calendar Tool will store its standard files. _______________"

Instead of a prompt, conclude the installation with a tip of one of the following forms, as appropriate:

You are a confirmed registered user on the Calendar Tool central host computer host name.

You can use the `Admin->Central Host' command to change your central host or disconnect from the host to run in stand-alone mode.

-- or --

This installation of the Calendar Tool is configured to run as a stand-alone program that is not initially connected to a Calendar Tool central host computer. If you are a registered user on a Calendar Tool central host, you can use the `Admin->Central Host' command to connect to the host. If you are not a registered and want to become one, please contact your local Calendar Tool administrator.

The first form of tip happens by virtue of a cal tool admin having built a custom config with the default name of a central host set to a host on which the user running the install is registered. The second form happens otherwise.

2.15.2. Implementor or Adminstrator Configuration of the Calendar Tool

When the app is built by the implementors or configured by an adminstrator, it contains the following hard-wird information:

a set of default option values

2.15.3. Installation of the Calendar Tool on a Regular User's Local Computer

When installed, the app is additionally configured with the following info:

the user's calendar tool directory

2.15.4. Installation of the Calendar Tool Administration Program on a Central Host

2.15.5. Location of Calendar Tool Files

Some directory needs to be designated as a user's caltool directory, and this directory must be that specified in a register's user's central host user database record. The default name for this directory in the standard Calendar Tool distribution is .CalendarTool. System installers and adminstrators must take care that the following conditions do not cause confusion or problems for users:

the installation script, by some funky OS convention, puts the user's cal tool dir is some place like c:336e user's cal tool database record says the user's cal tool dir is someplace else
a user is registered on more than one calendar tool central host, with different cal tool directories, or other different user-record information on thoses hosts

As necessary, expand and elaborate upon these conditions, including explanation of exactly where they're problems or can lead to problems.

2.15.6. Invoking the Calendar Once Installed

Points to include:

Init file only invoked one time at start-up, not at each file open
Prev rule means no init file happens when other user's calendars are open.
Allow (?provide?) both command line and GUI invocation; with command line, args specify files and options. With GUI invocation, calendar files are the one or more selected for invocation. In either case, all open files are opened by the tool.
The initial default calendar is an empty calendar named "unnamed"; this is overridded by a command-line arg or icon-based file invocation.

Prev: multi-user-envir | Next: future-enhancements | Up: functional | Top: index