Copyright 1996, Hyperion Softword

                    *************************************
                    *  Orpheus 2, beta release 2.00.30  *
                    *************************************

                Comments and queries to:  Hyperion Softword,
                535 Duvernay, Sherbrooke, QC J1L 1Y8, Canada
                    tel/fax - 819-566-6296 (Rod Willmot)
                       email - willmot@interlinx.qc.ca


Contents of this file:  Purpose
                        Usage
                        Supported Features
                        Missing Features
                        About CMP Files
                        Making Hotspots



PURPOSE:
========

    This program, the Simulator, is for use with hypertext projects that
    are still under development in OH.EXE.  Normally it is called by
    OH.EXE itself when you give the "Simulate Reader" command on the
    Project Menu.  However, it can also be run as a standalone program.

    The Simulator enables authors to view a work in progress exactly as
    it will be seen in the Reader when finished.  The Simulator obeys
    all project-specific settings made in the Project Options dialog,
    and responds to command buttons set up through the Screen Layout
    dialog.  In order for the Simulator to have something to work with,
    you must at some point give a Compile command, either from the Build
    Dialog (on the Project Menu), or with a convenient command that is also
    on the Project Menu, "Compile, Simulate".  See "About CMP Files" below.

    A special function of the Simulator is to enable authors working with
    graphics to create hotspots.  See "Making Hotspots" below.


USAGE:
======

    To run the Simulator as a standalone program:

        OHSIM [filename]

    where [filename] is the name of the project, with no extension.  The
    project must contain at least one CMP file in its storage directories,
    which in turn must include a compiled version of the project's Homecard.


SUPPORTED FEATURES:
===================

    The Simulator should support all features documented in online Help,
    with the exception of certain elements of the Reader that would be
    pointless to include.  In other words, if you are using a feature
    that will run in the Reader, you should be able to test it in the
    Simulator.  Missing features noted below will be added in coming
    releases.


MISSING FEATURES:
=================

    The Simulator does not yet replicate the Reader's built-in menus (which
    aren't there yet anyway), nor does it provide access to Reader Help
    (which hasn't been written yet).  Support for certain script commands
    will be added in parallel to both the Reader and the Simulator, in
    forthcoming releases.


ABOUT CMP FILES:
================

    Unlike the Orpheus Reader, which uses HTX files, and Orpheus Help,
    which uses HLP files, the Simulator uses the CMP files stored with
    your project's uncompiled cards.  CMP files are created when you
    give a Compile command through the Build Dialog; they contain all
    of the compiled cards for one storage directory.

    CMP files represent an intermediate stage between uncompiled cards and a
    finished, distributable HTX document.  They are the hypertext equivalent
    of the .OBJ files so dear to programmers.  Throughout the development
    period of a project, you should periodically open the Build Dialog
    (on the Project Menu) and, with Selection set to "Compile if new or
    changed", give a "Compile only" command.  All new or updated cards will
    be compiled, with the compiled version stored away automatically in the
    appropriate CMP file.  (NOTE: this does not in any way change the
    original - text file - copies of your uncompiled cards.)  You can then
    use the Simulator to examine and experience your work as if you were
    your intended reader, without having to product a finished HTX and fire
    up OHREAD.EXE.  Of course, when you do give the command to assemble a
    finished product, if most of the work is already present in CMP form
    the assembly will be extremely fast.  Since the compiler will also alert
    you to any problem areas in your project, it's a good idea to do an
    incremental compile at the end of every development day.

    For more about CMP and other files used by Orpheus, see Help on
    Files and Directories.


MAKING HOTSPOTS:
================

    The Simulator is your tool for making hotspots in Orpheus 2.  Any Graphic 
    card can have hotspots applied to a graphic (PCX, GIF, or other supported 
    format) or to an ansi screen.  Each hotspot can then be linked either to 
    another card (Text or Graphic) OR to one or more commands immediately 
    following the hotspot command.  For a complete discussion please see
    online Help.