
   File:  README for the LSX Toolkit, Release 1.1 (October 4, 1996)

   Copyright (c) 1996 Lotus Development Corporation
_______________________________________________________________________
_______________________________________________________________________

INSTALLATION AND USAGE AGREEMENT

Installation and use of the LSX Toolkit is governed by the agreement
consisting of the text of the file LSX\LSXLICNS.TXT.
The agreement is titled "Software Development Kit Agreement."
Read the agreement before installing or using the LSX Toolkit.

_______________________________________________________________________

MEDIA

This release of the LSX Toolkit software is made available on
the World Wide Web and on the Lotus Toolkit Collection CD.


INSTALLING THE TOOLKIT

Install the Toolkit software to a hard drive on your machine.

To install from the Web, follow the installation instructions on the Web page.

To install from the Lotus Toolkit Collection, follow these instructions:

(on Intel platforms): XCOPY the LSX directory to the root
of the local hard drive where you wish to run the Toolkit.

(on the Macintosh PowerPC platform): copy the LSX folder to the local hard
drive where you wish to run the Toolkit.

(on UNIX platforms): Copy the file lsx_tk.tar to the root of your
home directory. Then type:
	tar fv lsxtk.tar

On any platform, the Toolkit documentation file LSXDOC.NSF will be installed
in LSX\LSXDOC. LSXDOC.NSF is a Notes Release 4 database. After you have
copied this file to your local Notes data directory, e.g. C:\NOTES\DATA,
add the database icon to your Notes workspace. In LSXDOC.NSF, refer to
the first section, "Platform-Specific Reference", for further instructions
on configuring your installed Toolkit.
_______________________________________________________________________

WHAT'S NEW IN RELEASE 1.1

The LSX Toolkit Release 1.1 is an upgrade of LSX Toolkit 1.0.

Additional platforms supported: LSX is now supported on AIX under Notes
Version 4.11 or later, and the Macintosh PowerPC Notes Version 4.1 or later.
Be sure that you have the appropriate Notes version on the server, the client,
or both, depending on which is accessing the LSX.

Additional uses of the LSX API: The Template sample now implements
user-defined constant and procedure registration. The sample also shows how
to use an expanded class, with run-time binding of class properties.

Redesigned LSXLODL: The LSXLODL code generator has been redesigned to reduce
your work in producing the class-registration tables required to build an LSX.
When you lay out your desired LSX classes in LotusScript-like language,
LSXLODL will generate all the necessary registration tables, GUID tables, and
class, property, method, and event ids for the LSX. For details, see the
section "LSXLODL: Compiling Class-Registration Tables" in the Toolkit
documentation.
_____________________________________________________________________


Release Note: Toolkit Release 1.1 Platforms

This release of the Toolkit consists of software and documentation for
16-bit and 32-bit Windows platforms, OS/2 Warp, DEC Alpha NT, Macintosh
PowerPC, and the UNIX platforms Sun SPARC Solaris, Solaris X86, and AIX.

LSXs will not run with Notes Release 4.x on the HP-UX platform.
_______________________________________________________________________


Release Note: Maximum length of filename in USELSX statement

The LotusScript USELSX statement may designate an LSX by a pathname.
This pathname must be no more than 40 characters in length.
_______________________________________________________________________


Release Note: Unloading a loaded LSX

Once an LSX has been loaded, there is no facility for unloading it
from the Lotus product that hosts the LotusScript instance. Also, it is
not a LotusScript error to try to load an LSX, with a USELSX statement,
when that LSX is already loaded. Taken together, these two facts mean that
you need to be careful, when debugging, to ensure that the latest compiled
version of your LSX will be loaded when you run a script containing the
USELSX statement.

To achieve that, you may need to terminate the LotusScript instance and
reload LotusScript. On some platforms, the only way to do that is to
terminate the Lotus product hosting the LotusScript instance. In particular,
if the LSX changes, especially in any way that affects the registration
information, then you must update the Version field in the ClassDesc argument
to the ClassRegister method call that registers each class in the LSX.
Alternatively, tell the users of the LSX to recompile the script that loads
the LSX. Unless the Version flag is changed or the script is recompiled,
the script will interact with the LSX in an unpredictable way.
_______________________________________________________________________


Release Note: Debugging LSXs on the AIX platform

The LSX test tool LSXRUN is not supported on AIX. When you need to test
your LSX on AIX, use the LotusScript IDE in Notes as your script testing
environment, and the Notes executable for source-level debugging. Follow
these steps:

1.  Start Notes
2.  Find the process ID for the Notes session
3.  Start your debugger with the Notes process ID as the executable
4.  Launch the script that would call your LSX
_______________________________________________________________________


Release Note: LSXTEST

The test tool LSXTEST includes a Help menu. The menu commands are not
enabled. The LSXTEST Help file is not included in this release. Full
documentation of LSXTEST is in the Toolkit documentation file LSXDOC.NSF.

_______________________________________________________________________
_______________________________________________________________________

