ooRexx (Open Object Rexx) Files

                      Release Notes ooDialog 4.1.0
                      ============================

ooDialog 4.1.0 is the version of ooDialog first distributed with ooRexx
4.0.0, plus all bug fixes and enhancements made to ooDialog up through
ooRexx 4.1.2.

ooDialog 4.1.0 can be installed to any ooRexx installation, 4.0.0 or
later.

Beginning with the release of ooDialog 4.2.0, the installation of
ooDialog has been decoupled from the interpreter.  ooDialog 4.1.0
installs over the top of any ooRexx installation.  It replaces the
version of ooDialog in the ooRexx installation with ooDialog 4.1.0.

This type of ooDialog installation is called an "independent" ooDialog
installation to indicate the ooDialog installation is independent of an
ooRexx installation and, to a degree, the version of ooRexx installed.

At the time of this release, 3 versions of ooDialog are being made
available as independent installations.  These are ooDialog 4.0.0,
4.1.0, and 4.2.0.  Going forward, ooDialog users will be able to install
any version of ooDialog they want to their ooRexx installation.
Provided of course that the ooRexx version meets the minimum required
version for the ooDialog version.

ooDialog 4.1.0 requires a minimum ooRexx version of 4.0.0.


Installation
============

Installation is simple, done through a typical Windows installer.  Pick
the installation package that matches the bitness of the ooRexx
installation.  I.e., a 32-bit package for a 32-bit ooRexx and a 64-bit
package for a 64-bit ooRexx.

The installer will detect the installed ooRexx, location and version.
If the ooRexx version is less than 4.0.0, or if there is no installed
ooRexx, the installer will abort with a message explaining the problem.
Otherwise the installer will replace the current ooDialog with ooDialog
4.1.0.

Note that the actions of the installer are dependent on the version
of ooRexx, not the version of the installed ooDialog.  For instance, if
the installed ooDialog is version 4.3.0, but for some reason the user is
not happy with that version, running the ooDialog 4.1.0 installer will
replace the 4.3.0 version with the 4.1.0 version.

At the time of the installation, *all* ooDialog programs must be halted
and the ooDialog PDFs must be closed if they happen to be opened.

An alternative way to install ooDialog 4.1.0 is to install
switchOODialog, however switchOODialog requires that the ooRexx version
be ooRexx 4.1.0 or later.  The ooDialog 4.1.0 installer only requires
that the ooRexx version be 4.0.0.


switchOODialog
==============

Switch ooDialog provided a way for users of ooDialog to begin testing
and experimenting with the new features in 4.2.0.  Switch ooDialog is
available for the ooDialog 4.2.0 so that users can upgrade their version
of ooDialog without worrying about the consequences.  If there is some
problem and they are not happy with ooDialog 4.2.0, they can easily
switch back to ooDialog 4.1.0

Switch ooDialog makes it possible for users to easily and transparently
switch back and forth between ooDialog 4.2.0 and the release version of
ooDialog packaged with ooRexx 4.1.0.  Switch ooDialog is downloadable
from SourceForge, in the ooDialog 4.2.0 area, making an upgrade to
ooDialog 4.2.0 worry free.

To install ooDialog 4.2.0, pick the switchOODialog package that matches
the bitness of the installed ooRexx.

When switchOODialog is initially installed, the active version of
ooDialog will be ooDialog 4.2.0.  switchOODialog.exe acts like a toggle.
Each time it is executed it switches the active version of ooDialog
between 4.1.0 and 4.2.0.

switchOODialog can be executed from the command line, or through menu
items in the ooRexx section of the Start menu.

switchOODialog has the same requirements as does a regular installation
of ooDialog 4.2.0.  There must be an installed version of ooRexx that is
at least version 4.1.0.  At the time of the installation, *all* ooDialog
programs must be halted and the ooDialog PDFs must be closed if they
happen to be opened.


Known Problems, "Gotchas," and Solutions with Independent Installations
=======================================================================

* Problem:

  The ooRexx installer creates a log of the files it installs.  When the
  uninstaller runs, the user can select to only uninstall files logged
  during installation.  An independent ooDialog installation may install
  some example programs, documentation files, and shortcuts not recorded
  in the log file.  If at that point, ooRexx is uninstalled, these files
  and shortcuts may not be deleted.

  Solution 1:

  Before uninstalling ooRexx, install the independent ooDialog that
  matches the ooRexx installation.  I.e., if the ooRexx installation is
  any 4.0.x, or 4.1.x ooRexx version, install the ooDialog 4.1.0
  independent installation. Then when ooRexx is uninstalled, all ooDialog
  files and shortcuts will be removed because the files and shortcuts
  exactly match what was installed during the ooRexx installation.

  Solution 2:

  After uninstalling ooRexx, manually delete any files in the old ooRexx
  installation directory.

* Gotcha:

  The independent ooDialog installation deletes the entire ooDialog
  samples subdirectory tree.  This will delete any personal files
  that may have been put there after ooRexx was installed.

  Solution 1:

  Do not put personal files in the %REXX_HOME%\samples\ooDialog
  subdirectory tree.

  Solution 2:

  Before executing the independent ooDialog installer, move or back up
  any personal files that may be in %REXX_HOME%\samples\ooDialog
  subdirectory tree.