This document describes the procedure for installing the DOME source code
library.

Note: The DOME Library requires the use of the Cincom's
VisualWorks Smalltalk 7.4.1 tool suite.  A free non-commercial version of
VisualWorks is available for Intel Windows, Power Mac, and Linux
Platforms.  Commercial versions of VisualWorks are available for Windows,
Power Mac, and most UNIX operating systems.  Cincom can be reached at:
http://www.cincomsmalltalk.com.


Introduction
------------

The DOME library is distributed as a collection of parcels which are easily
loaded via the parcel loading mechanism of VisualWorks.  All of the parcels
are located in the directory named "parcels".

Alternatively, DoME can be loaded as a bundle from the Cincom Public Repository
(http://www.cincomsmalltalk.com/CincomSmalltalkWiki/PostgreSQL+Access+Page).
The latest development version is DOME-53-RH-80.2.

Installation Steps
------------------

To load and use the DOME library:

 o It is recommended that the DOME library be loaded into a new image.

 o Move the directory called "tools" to the same directory from which
   VisualWorks is started from.  Many portions of the DOME library depend
   on finding files contained in the tools directory.  If DOME is unable to
   find the tools directory when it starts up then the DOME Launcher will
   display a message to that effect.

 o Add the DOME parcels directory to the VisualWorks' Parcel Path.  From
   the VisualWorks Launcher select the File->Settings menu entry.  Go to
   the Parcel Path tab in the Settings dialog and add the DOME library
   parcels directory to the list.

 o Load the DOME parcel by selecting the Tools->Load Parcel Named... menu
   entry from the VisualWorks Launcher.  Enter "DOME" into the dialog and
   press return.  This will load all of the required parcels.

 o The VisualWorks Launcher is extended with a Tools->DOME menu.  The
   "Launcher" sub-menu entry opens a DOME Launcher window.

 o The VisualWorks UIPainter parcel should be loaded so new cursors and
   icons may be created within the DOME Tool Specification tool.  It is
   fine to have the ClassNameChooser and ClassReporter classes be loaded at
   a later time if so prompted.

Parcel List
-----------

An index of all packages including their version and change history can be
found in parcels/index.html.

Base System

 o emapps - Envy support.

 o T-gen - T-gen parser/scanner generator.  Refer to the parcel's comment
   and notice for details about its authorship and availability.

 o DoMESystem - The DOME library.  The DoMESystem parcel can be loaded
   instead of the DOME parcel to get only the core DOME library
   functionality.

Additional Notations

 o ColbertSystem
 o DFDSystem
 o IDEF0System
 o MultiPageSystem
 o PaperOutlineSystem
 o PetriNetSystem   
 o STDSystem

Additional Windows Capabilities

 o WindowsExtensions - This parcel contains interfaces for using the File
   Dialog Box available under Windows.  Refer to the parcel's comment for
   details about its authorship and availability.

Full System  

 o DOME - This is an empty parcel that has its prerequisites set to all of
   the previously mentioned parcels.

Additional Capability

 o MultiLayerTabControl - This parcel replaces the usages of the
   VisualWorks Notebook widget with the much more user friendly ICC
   TabControl widget.  This parcel is dependent upon the ICC TabControl and
   TabControlDemo parcels.  DOME uses a notebook widget in the preferences
   dialog as well as in the property editor.


For Additional Assistance
-------------------------

For additional assistance, see the DOME web pages at

www.htc.honeywell.com/dome

or the DoME port development website

www.mrgg.at/wiki/dome/.


Acknowledgements
----------------

In addition to the freely available t-gen (T-gen parcel) and file dialog
box (WindowsExtensions) libraries, the DOME library makes use of the
HyperText capabilities of Smallwalker.  Due to slight modification of the
SmallWalker HyperText capabilities the SmallWalker classes included in the
DOME library have been renamed to have a SW prefix so that Smallwalker can
still be loaded without conflict.  Refer to the class comment of any of
these SW prefixed classes for details about its authorship and
availability.