OS/2 Shareware BBS: 8 Other/08-Other.zip/edis201d.zip/edis.inf

OS/2 Help File | 1996-10-02 | 33KB | 884 lines

ΓòÉΓòÉΓòÉ 1. About the EDis Project ΓòÉΓòÉΓòÉ

Welcome to...

EDis V 2.0 for OS/2 (PM and OpenDoc version)
-----------------------------------------------------
released: 16.09.1996 as FULL and DEMO version

This chapter gives you an overview of the EDis project and what is it useful
for.

For further informations about EDis V 2.0 take a look at the official EDis
homepage:

http://www.informatik.tu-muenchen.de/~schwarma/edis.html

There are two versions of the program, a demo version and a full version.

     The full version can be bought from me or from an online warehouse. Send
      me an email or go to the EDis homepage to get further informations, where
      to get the full version. Note This software has to be licensed for every
      workstation (host) it is used on.

     The demo version can be copied and shared freely without payment. It is
      fully functional except the fact that SAVING OF TEXT IS DISABLED.
      Academic staff and students may obtain a free registration number from me
      by sending me an email with name, address and academic grade or
      profession. By submitting the registration number inside the registry
      dialog, saving of text is enabled. Note Registering the software is only
      for academic useage due to the fact, that this program is also part of a
      academic project. All other people who want a full version of the program
      have to buy it.


ΓòÉΓòÉΓòÉ 1.1. What is the EDis Project ΓòÉΓòÉΓòÉ

The EDis project realizes a distributed multiuser editor allowing some users to
edit the same text at the same time synchonized, protecting all changes against
each other and transfering changes made by one user to every other user of the
text, cross a network and (planned) cross different platforms such as OS/2 and
Windows (95/NT).

The editor is divided into an editor client and an editor (text) server. The
editor server handles the text storing and managing and is implemented as a
collection of DSOM-classes executed by a DSOM-Server-Program. The editor client
handles the local version of the text and communicates all changes made with
the server. Till now, two clients exists, a PM client running on on OS/2 Warp
(3 and 4) and an OpenDoc client part running on OS/2 Warp 3 with Fixpack 17 and
OpenDoc from Devcon 10 or OS/2 Warp 4. This two clients share about 90% of the
code needed for local text managament, only about 10% implement the code for
the different environments. There will be a Windows 95/NT/OLE2 client and also
a Windows 95/NT server, betaing end of october.

This project serves both as a technologie demo demonstrating the power of
combining SOM, DSOM and OpenDoc into a software project and as a real world
application which lets you edit text (ASCII).

Please try version and send me your opinions, found errors and questions
appeared during the use of this application. It will be improves due to your
needs and requests, it is still an open project.

This project is part of a graduate paper about compound document frameworks,
comparing OLE and OpenDoc and the following todays frameworks:

 CDF             Compound Document Framework,  IBM,  OS/2  and Windows

 ODF             OpenDoc Development Framework, Apple, MacOS and Windows

 MFC             Microsoft Foundation Classes,  MS,   Windows

 This graduate paper is written at IBM Deutschland GmbH, Germany set by the
 'Institut fБr Informatik' at TU-MБnchen, professorship 'Softwaretechnik' of
 Prof. Dr. Albert Endres.

 This graduate paper was guided by Christoph Hofmann (TU-MБnchen) and Scott
 Davis (IBM Ehningen).

 If you show interest in this graduate paper, it shall be completed till
 15.11.1996. It will then be available as HTML and PS text via my homepage.
 (But sorry to say only in german language).


ΓòÉΓòÉΓòÉ 1.2. What is it used for ΓòÉΓòÉΓòÉ

There are at least four possible usability situations for a distributed
multiuser editor:

     As a technology demo for the power of combining CORBA and OpenDoc and the
      use of software components.

     Due to the separation of text editing and text managing (storing) into
      two separated pocesses on two machines, the text is very safe. If a
      client breaks up, (could happen expecially in the current OpenDoc 1.0
      environment), the text server stays up and running, just start the client
      again and relog to the text server. All the changes made are still
      present and no work is lost.

     The simultanous processing of text is very useful in larger enterprises
      for communication and text editing. Some users can join together onto a
      project, everybody sees what is done and where changes appear. Even
      messages between users can be effectively transmitted.

     Within tutorial sessions while scholars work on their jobs (e.g. tests) a
      teacher is able to join in the test, follow the work of the scholars and
      give hints or corrections in place.


ΓòÉΓòÉΓòÉ 1.3. About this release ΓòÉΓòÉΓòÉ

This is the first commercial version of this program, so it has been tested
well and seems to be quite stable.

There are two versions of the program, a demo version and a full version.

     The full version can be bought from me or from an online warehouse. Send
      me an email or go to the EDis homepage to get further informations, where
      to get the full version. Note This software has to be licensed for every
      workstation (host) it is used on.

     The demo version can be copied and shared freely without payment. It is
      fully functional except the fact that SAVING OF TEXT IS DISABLED.
      Academic staff and students may obtain a free registration number from me
      by sending me an email with name, address and academic grade or
      profession. By submitting the registration number inside the registry
      dialog, saving of text is enabled. Note Registering the software is only
      for academic useage due to the fact, that this program is also part of a
      academic project. All other people who want a full version of the program
      have to buy it.


ΓòÉΓòÉΓòÉ 1.4. About the author ΓòÉΓòÉΓòÉ

This program has been written by Martin Schwarz for IBM Informationssysteme
GmbH and TU-MБnchen.

(c) 1996 by Computer-Software-Entwicklung
      Martin Schwarz
      Meisenweg 5
      84544 Aschau a. Inn
      Germany

      E-MAIL: [e-mail]
      WWW: http://www.informatik.tu-muenchen.de/~schwarma/


ΓòÉΓòÉΓòÉ 2. Installation ΓòÉΓòÉΓòÉ

Before installation you have to decide whether the editor should work on a
single worksstation or in a network and whether you want to use the PM-Client,
the OpenDoc-Client or both.

First take a look on the hardware and software requirements and decide which
options you take and then continue with the basic installation.


ΓòÉΓòÉΓòÉ 2.1. Hardware requirements ΓòÉΓòÉΓòÉ

     An OS/2 Warp powered 386 PC or higher with at least 8 MB RAM

     TCP/IP Network for Multiple Workstations


ΓòÉΓòÉΓòÉ 2.2. Software requirements ΓòÉΓòÉΓòÉ

     Single Workstation / PM-Client:

        -  OS/2 Warp 3 or 4

     Single Workstation / OpenDoc Client:

        -  OS/2 Warp 3 + Fixpack 17 + OpenDoc 1.0 from DevCon 10 or

        -  OS/2 Warp 4

     Multiple Workstations / Workgroup

        -  Single Workstation requirements

        -  TCP/IP Network (e.g. LAN Server + MPTN)

        -  DSOM Workgroup Enabler for OS/2 on every workstation


ΓòÉΓòÉΓòÉ 2.3. Basic installation ΓòÉΓòÉΓòÉ

Even if you use the editor on multiple workstation, it has to be installed on
your local harddrive. (At least the file EDis.IR has to be local to fulfill the
Interface Repository).

During installation you can choose between installing

     Server and PM-Client or

     Server, PM-Client and OpenDoc-Client.

 For the basic installation process start the IBM Software Installer
 install.exe. It will

     Copy and decompress the following files in one directory on your lacal
      disk

        -  Server and PM-Client related files:

           EDISSRV.DLL    editor server library

           EDIOCL1.DLL    IBM Visual Age Compiler Library (cppom30)

           EDIOCL2.DLL    IBM Open Class Library (cppoob3)

           EDIOCL3.DLL    IBM Open Class Library (cppoou3)

           EDISRES.DLL    editor client resources

           EDISCLI.DLL    editor client common text management library

           EDISPM.EXE     editor PM-Client frontend

           EDIS.HLP       edior client online help file

           EDIS.INF       this Users'Guide

           EDIS.IR        Interface Repository used by EDis V2.0

        -  OpenDoc-Client related files:

           EDISPART.DLL    editor client OpenDoc part handler library

           EDISUPRT.DLL    user display OpenDoc part handler library

           EDISREG.EXE    program for creating OpenDoc part templates

           EDBASE.DLL     parent class used by the OpenDoc parts

     Add the following statements to your CONFIG.SYS

      LIBPATH              the installation directory will be added

      SET PATH             the installation directory will be added

      SET HELP             the installation directory will be added

      SET SOMIR            the entry %installation directory%\EDIS.IR will be
                           added

     A desktop folder named EDis V 2.0 will be created with the following
      files

      PM-Client:           Program Reference to the file EDISPM.EXE

      EDIS.INF             Shadow Object of the file EDIS.INF

      Register OpenDoc-Client   Program Reference to the file EDISREG.EXE

 If you want to install from disks, copy the files on two disks and change disk
 and press retry everytime an error message apears. (The above file sort order
 will help you).


ΓòÉΓòÉΓòÉ 2.4. DSOM installation ΓòÉΓòÉΓòÉ

The installation and configuration of the DSOM environment can be very tricky.
In the following I gave you a few hints for the correct installation.


ΓòÉΓòÉΓòÉ 2.4.1. Workplace DSOM ΓòÉΓòÉΓòÉ

The normal DSOM environment included in OS/2 Warp 3 or 4 will be all you need.

If not already done, add statments for hostname and username to the CONFIG.SYS
(e.g. SET HOSTNAME=GigaPower  SET USER=Martin).


ΓòÉΓòÉΓòÉ 2.4.2. Workgroup DSOM ΓòÉΓòÉΓòÉ

This program has been tested on an OS/2 Lan Server 4.0 driven network.

The following informations will help you in your installation process.

     The network must be TCP/IP enabled, hostnames and TCP/IP addresses must
      be set for every host.

     Hostname and username has to be set in the CONFIG.SYS of every host.

     The IBM DSOM Workgroup Enabler must be installed on every host, you can
      get it from http://www.software.ibm.com/objects/somobjects.

     The file EDISSRV.DLL contains the DSOM classes

        -  EDSService,

        -  EDSText,

        -  EDSLine,

        -  EDDAServer,

        -  EDSAServer

     The information required for the Interface Repository is contained in the
      file EDIS.IR which is set in the SOMIR path during installation.

     The Implementation Repository must be located in a shared directory! The
      entrys for the text servers are dynamically created and deleted and must
      be available for every client from every host. Set the statement SET
      SOMDDIR in the CONFIG.SYS to a shared directory on your network.


ΓòÉΓòÉΓòÉ 2.5. OpenDoc installation ΓòÉΓòÉΓòÉ

To run the OpenDoc-Client, the class EDisPart included in the file EDISPART.DLL
and the class EDisUserPart included in the file EDISUPRT.DLL has to be
registered to OpenDoc to create templates.

To accomplish that let run the included program EDISREG.EXE which will do just
that.

You can also use the commands:

     ODINST -cEDisPart -dedispart

     ODINST -cEDisUserPart -dedisuprt


ΓòÉΓòÉΓòÉ 2.6. If installation fails ΓòÉΓòÉΓòÉ

Send me an email or contact me via my address. I will then try to fix your
problem and eventually update the product.


ΓòÉΓòÉΓòÉ 3. Using EDis ΓòÉΓòÉΓòÉ

Both editor clients (PM and OpenDoc) are completely online help enabled. Press
F1 to get context information or choose an menu help entry.

The EDis editor consists of two separate executed parts communicating with each
other:

     Editor (text) server: Manages an ASCII textfile synchonizing the requests
      of a number of editor clients.

     Editor client: Edits a lokal version of the text and communicates the
      changes made line by line with the editor server. The local version of
      the text is updated regularly with the central version hold by the editor
      server.

 A editor client can read single lines from the server and lock them for
 exclusive usage so that no other client is able to lock or write this line,
 reading is allowed. Further more every line has a version number which is
 counting up during every update. If the version number of a line before
 writing or locking is higher than the current local line version number, lock
 or write is not allowed.

 Made changed are saved in a eventlist. The clients fetch this eventlist
 regularly and apply these events to the local version of the text (Update).
 The update frequence can be set in the setting dialog from 1 to 1000 seconds.
 Clients must register itself to the server by a unique username during
 server-logon. This username is used to mark lines as locked. All currently
 registered usernamed can be viewed inside the user window of the editor.


ΓòÉΓòÉΓòÉ 3.1. Start of the program ΓòÉΓòÉΓòÉ

The DSOM Environment has to be available and ready. The DSOM-Demon SOMDD.EXE
will be started automatically by the Editor client during startup as a process
of the Workplace Shell if not already running.

Start either the PM-Client or the OpenDoc-Client.

     In order to run the PM-Client start the program "PM-Client" in the "EDis
      V 2.0" folder or type EDisPM inside a command window. You can submit up
      to two parameters:

        -  Username: Set your logon username during startup.

        -  Textalias: Immediately logon to the given text server during
           startup.

      If there is an existing profile called (EDISPM.INI) in your working
      directory, settings, username and textalias will be loaded from it. You
      can override the this by submitting the parameters username and "NO" for
      the textalias.

     To start the OpenDoc-Client drag the "Distributed Editor Part" template
      to either the desktop for creating a root part or a container part for
      creating an embedded part or start a previous created OpenDoc document
      including the OpenDoc-Client. If this Client was closed while logged on
      to a text, the text will immeadiatly be loaded during startup.

 During the start of any EDis client the DSOM environment is tested and
 started. If any errors occure then first check the DSOM environment, e.g. if
 the DSOM-Daemon somdd.exe is started. IF the client hangs during startup, try
 to set the statement SET SOMDTIMEOUT= to a value of 15 seconds. If a timeout
 occures, a message box will display with a SOM/DSOM-error code.

 NoteDuring initialisation, the message "initializing, please wait..." is
 displayed inside the program window until the it it completed and the message
 "ready to logon..." appears. While initialisation is in progress, the Logon
 menu entry is disabled. But most other functions are available because the
 initialisation is separated into a own thread.


ΓòÉΓòÉΓòÉ 3.2. Text management ΓòÉΓòÉΓòÉ

There are two basic servers managing and administrating different text:

     A text administration server managing text server information where on
      which host the text server is started and from which text file it should
      load. The information is stored in the profile (EDIS.INI). This profile
      is placed in the directory where the SOMDDIR environment variable is
      pointed to. (Look for the SET SOMDDIR= statment in your CONFIG.SYS).

     A text server manages the text. It is started with the first client
      logging on to a unique text alias for which currently no text server
      exists. During startup the text is loaded from a given file (if the file
      does not exist, a new one is created). After startup, the text server is
      ready for clients to log on that text. With the last client logging off
      from the text server, the text server is terminated after the text has
      been saved to given filepath.

 Clients can

     Logon to a text server by selecting the logon entry from one of the menus
      or by specification of a second parameter during client startup.
      Remember: Text are referenced by a unique text alias. With the text
      alias, clients are able to request the hostname and the filepath for that
      alias. Inside the logon dialog, all currently registered text are
      displayed with the text alias, hostname, filepath and the status
      displaying "active" when a text server is running for the alias and
      "------" when not. You can add, delete or change the entrys from within
      that dialog. By choosing an entry, logging on to that text proceeds.

      Note If the program is in demo mode (no valid registration number has
      been submitted in the registry dialog) during logon an informational
      message will appear and the text server either switched to demo mode,
      that means saving of text is not allowed, or the editor client allowes
      only viewing of the text.

     Logoff from a text server by selecting the logoff entry from one of the
      menus. Logoff also takes place when a client is closed.

     Save text to the currently defined filepath.

     Change the currently defined filepath and save the text to the new
      filepath. Remember that the filepath roots on the host the text server is
      running (determined by hostname), not always on your local host. You can
      change the hostname the text server should be executed within the logon
      dialog, but only if the text server is currently not active.

     Import text from file. You can choose a local text within a file dialog,
      read that text and transfer it to the text server.

     Export the local text to a file. Choose a filename to store within the
      save as dialog and proceed.

 Servers are DSOM objects which are executed by the standard DSOM server
 program somdsvr.exe. These servers are automatically started by the client if
 the somdd.exe is running. Every single text refered by a unique text alias is
 managed by one text server.


ΓòÉΓòÉΓòÉ 3.3. Text editing ΓòÉΓòÉΓòÉ

Changes are only valid onto locked lines.

Lockes are requested before an edit action goes actually to the edit window. If
a line could not be locked, edit actions for that line are surpressed.

In the status line, the locked status is displayed.

 Key             Function

 Cursor          Move the text cursor. If the cursor leaves a locked line, this
                 line is released and written to the editor server. The new
                 line information with the actual cursor position is shown in
                 the status line.

 Pos 1           Set the text cursor to the first position in the current line.
                 The new line information with the actual cursor position is
                 shown in the status line.

 Ende            Set the text cursor to the last position in the current line.
                 The new line information with the actual cursor position is
                 shown in the status line.

 Ctrl+Pos 1      Set the text cursor to the first line of the text. If the
                 cursor leaves a locked line, this line is released and written
                 to the editor server. The new line information with the actual
                 cursor position is shown in the status line.

 Strg+Ende       Set the text cursor to the first line of the text. If the
                 cursor leaves a locked line, this line is released and written
                 to the editor server. The new line information with the actual
                 cursor position is shown in the status line.

 Insert          Toggles the insert mode between insert/overwrite.

 Delete          If the current cursor line is not already locked, a lock will
                 be questioned to the server. If the lock is valid, the
                 character in behind the text cursor is deleted. If the text
                 cursor is at the end of the line, the next line will be locked
                 and appended onto the current line.

 Enter           If the current cursor line is not already locked, a lock will
                 be questioned to the server. If the lock is valid, a new line
                 will be inserted after the current line and the text after the
                 text cursor is clipped to the new inserted line. After the
                 operation, the text cursor is placed in the new inserted line
                 which is locked for you.

 Backspace       If the current cursor line is not already locked, a lock will
                 be questioned to the server. If the lock is valid, the
                 character in front of the text cursor is deleted. If the text
                 cursor is in the first position of the line, the line will be
                 deleted and appended onto the line before as long as the
                 locking of the line before is valid.

 Ctrl+Backspace  If the current cursor line is not already locked, a lock will
                 be questioned to the server. If the lock is valid, the line is
                 deleted.

 Character       If the current cursor line is not already locked, a lock will
                 be questioned to the server. If the lock is valid, the
                 character is inserted at the cursor position.

 Mouse operations:

 Click the mouse inside the edit window to set the cursor position. You can
 mark a block of text with the mouse. If you click a mouse button while a block
 is marked, the block is demarked.

 Block operations:

 Cut, Copy and Paste are supported for single lines and blocks. Before deleting
 or inserting a block, the action is certainly validated with the text server
 if this action is currently possible.


ΓòÉΓòÉΓòÉ 3.4. Configuring the program ΓòÉΓòÉΓòÉ

There are three basic options dialogs:

     Username: Change the username used to register yourself to a text server.
      The default is "anonymous".

     Fonts: Change the font used in text and user window.

     Settings: Change colors, update frequency, border size, tab size and
      toggle horizontal and vertcal splitting of edit and user windows.

     Userlist: Toggle the user window on and off.

     Scrollbars: Toggle the scrollbars of the edit window on and off.


ΓòÉΓòÉΓòÉ 3.5. Exiting the program ΓòÉΓòÉΓòÉ

Close the program. Settings are saved to a profile (EDIS.INI) in your working
directory (that is not always the program directory).

This gives you the opportunity to have several different customized versions
with different settings, username and textalias by starting the program from
different directories.


ΓòÉΓòÉΓòÉ 3.6. Special OpenDoc features ΓòÉΓòÉΓòÉ

The EDis OpenDoc-Client consists of a part handler based on the
jmBaseNonContainerPart class inheriting its functionality.

Inside the frame border, some OpenClassLibrary Window classes managing the
display of the editor.

There are popup and pulldown menues available if the editor part is selected.


ΓòÉΓòÉΓòÉ 3.6.1. Storage information ΓòÉΓòÉΓòÉ

By closing the EDis OpenDoc-Client (part), the current username, the text name
(if already logged on to a text) and the layout informations are saved and
restoring during the next opening of the part.


ΓòÉΓòÉΓòÉ 3.6.2. Clipboard usage ΓòÉΓòÉΓòÉ

The EDis OpenDoc-Client is clipboard enabled, so you can cut, copy and paste
text in and out of the editor window.


ΓòÉΓòÉΓòÉ 3.6.3. Drag and Drop ΓòÉΓòÉΓòÉ

The EDis OpenDoc-Client is Drag and Drop enabled, you can mark a text, press
the right mousebutton over it and drag the maked ASCII text information to
either inside the editor part or outside to a text part.

If you holf the CONTROL key during dragging, the text is copied else the text
is deleted from the old position.


ΓòÉΓòÉΓòÉ 3.6.4. Draft versioning control ΓòÉΓòÉΓòÉ

Draft versioning simply do not work in the current version of OpenDoc (1.0 GA)
but should do with OS/2 Warp 4.


ΓòÉΓòÉΓòÉ 3.6.5. User Display Part ΓòÉΓòÉΓòÉ

The Distributed User Part serves as a OpenDoc part handler for displaying the
users currently logged on to a text (server).

The part is not directly connected to the text server, it gets the user
informations from the Distributed Editor Part via a link.

After creation and opening of this part, its empty until you specify a link
between one (or more) Distributed Editor Part(s) and this part.

There are two ways to create a link:

     Select Copy from the Distributed Editor Part's menu to copy the linkage
      information to the clipboard and then select Paste as link from this part
      to actually create the link.

     Drag and Drop Press the right mouse button somewhere over the Distributed
      Editor Part and drag the document image into this part's window. This way
      the linkage information will pass to this part and the link will be
      actually created.

 The link is saved while closing the document and will be restored the next
 time you open the document.

 As an update of the userlist of the Distributed Editor Part occures, the data
 will be send via the link to this part and be displayed.

 Note The OpenDoc linkgage mechanism requires the avsshell.exe to be up and
 running (it will be started by the parts). This programm is based on the DSOM
 environment. If the linking goes wrong, check the DSOM environment and delete
 the file avlsrvr.bto and the avlsrvr.bak from the /os2 folder. Then start
 somdd.exe (if not alread running) and the avsshell.exe. If both are running,
 the linking shall be no problem.


ΓòÉΓòÉΓòÉ 4. Copyright and additional informations ΓòÉΓòÉΓòÉ

The copyright and additional informations about the EDis project.

There is a homepage about the EDis project available:

http://www.informatik.tu-muenchen.de/~schwarma/edis.html


ΓòÉΓòÉΓòÉ 4.1. Copyright ΓòÉΓòÉΓòÉ

(c) 1996 by Computer-Software-Entwicklung
      Martin Schwarz
      Meisenweg 5
      84544 Aschau a. Inn
      Germany

      E-MAIL: [e-mail]
      WWW: http://www.informatik.tu-muenchen.de/~schwarma/

I am a student of computer science with theoretical medicine as my minor
subject. My main interests are in operating systems and databases.

My most fovorite computer operating system is OS/2 Warp, sometimes I also have
to put up with systems like WINDOWS (3.1/95/NT) or even more terrible DOS
(aaarrrggghhh).

Among some other stuff I sign responsible for the wellknown OS/2 software
PMxEyes. Besides I have already released an OpenDoc version of the PMxEyes to
get used to OpenDoc (ODxEyes), which I regard as a good technologie to stand
the OLE2 hype.

As a project for my studies, I implemented a distributed editor with the
SOM/DSOM technologie. Documentation, sources and the program are available via
my homepage as a HTML-text but only in german language.


ΓòÉΓòÉΓòÉ 4.2. Technical information ΓòÉΓòÉΓòÉ

Informations about the two technical bases EDis sets on:

     SOM/DSOM

     OpenDoc


ΓòÉΓòÉΓòÉ 4.2.1. SOM/DSOM ΓòÉΓòÉΓòÉ

SOM/DSOM implements a CORBA compliant object request broker which allows
applications to create, delete and access objects through a network as if they
where in th local processroom of the computer.


ΓòÉΓòÉΓòÉ 4.2.2. OpenDoc ΓòÉΓòÉΓòÉ

OpenDoc serves as a compound document architecture which is develloped by IBM
and Apple for the platforms MacOS, Windows, OS/2, AIX and more to come. The key
feature of the compound document architectures is the idea to build an
application lego-wise out of more parts from different vendors which plug
together to a well fit application suite.


ΓòÉΓòÉΓòÉ 4.3. Changes since EDisPM V1.0 ΓòÉΓòÉΓòÉ

EDisPM V1.0 was released on 30.09.1995 as part of a studies paper giving
overwiev and insides about CORBA, SOM and DSOM and demostrating its power with
this application.

EDisPM V1.1 was released on 25.06.1996 as part of a SOM/DSOM programming
tutorial called SOMObjects-Programming puplished in the german magazin OS/2
Inside volume 6/96 to 8/96.

EDis V2.0 was released on 16.09.1996 as part of a graduate paper about compound
document frameworks, demostrating the integration of a software product into
the OpenDoc environment and the power of combinating OpenDoc with SOM and DSOM.

Changes

     now for OpenDoc 1.0 GA,
     improvements in OpenDoc functionality,
     complete redesigned.


ΓòÉΓòÉΓòÉ 4.4. License Agreement ΓòÉΓòÉΓòÉ

SOFTWARE LICENSE AGREEMENT

          Computer-Software-Entwicklung
             Martin Schwarz
              Meisenweg 5
             84544 Aschau
               Germany
       email: [e-mail]
      http://www.informatik.tu-muenchen.de/~schwarma/

Read carefully the following terms and conditions.  Use of this product
constitutes your acceptance of these terms and conditions and your agreement to
abide by them.

This is a legal agreement between you, the end user, and Computer-
Software-Entwicklung Martin Schwarz ("MS-CSE").  By using this package, you are
agreeing to be bound by the terms of this agreement.  If you do not agree to
the terms of this agreement and you purchased this package directly from
MS-CSE, promptly return the disk package and the accompanying items (including
written materials and binders or other containers) within thirty (30) days to
MS-CSE for a refund, less the shipping and handling charges.  Returns are
subject to a 20% restocking fee.  If you obtained the software through a
reseller, dealer or distributor, consult them for their return policy.

This software comes in two versions, a freeware demo version and a commercial
full version. If you do not exactly know, which version you have got, start the
any client (e.g. EDISPM.EXE) and go to the "Product Information" dialog. If the
application title say "EDis 'version' (demo)" you have a demo version and are
bound to the demo version license agreement, if the application title say "EDis
'version'", you are bound to the full version license agreement. If the title
say "EDis 'version' (reg.)", you have got a registered demo license and are
bound to the registered demo license agreement.

(License)

     Demo version license: The demo version is a full functional version
      except that SAVING OF TEXT IS DISBALED. You may use this demo version for
      an unlimited evaluation period; make as many copies of this demo version
      software and documentation as you wish; give exact copies of the original
      including this license.txt to anyone; and distribute this demo version
      software and documentation in its unmodified form including this
      license.txt via electronic means. There is no charge for any of the
      above.

     Registered demo version license: By receiving and submitting a
      registration number, the demo version is altered into an registered demo
      version with the complete functionality of the full version. You may not
      use a registration number on more than one computer (i.e.  a single CPU)
      at the same time.  You may not sell or rent or lease or transfer the
      registration number. The software itself applies still to the demo
      version license.

     Full version license: You, the original purchaser, are granted a
      nonexclusive license to use the Software under the terms stated in this
      Agreement.  You may not use the Software on more than one computer (i.e.
      a single CPU) at the same time.  You may copy the software for backup.
      You may not rent or lease the Software, but you may transfer it on a
      permanent basis if the person receiving it agrees to the terms of the
      Agreement.  If the Software is an update, any transfer must include the
      update and all prior versions.

     Common license: You may not: use, copy, modify, merge, or transfer copies
      of the program except as provided in this license; alter, reverse
      assemble or reverse compile the program; or sublicense, rent, lease, or
      assign the program.

      Title to the Software is not transferred to User.  Ownership of the
      Software is vested in MS-CSE subject to the rights granted in this
      Agreement.

 (Limited Warranty)

 THE SOFTWARE AND ACCOMPANYING DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT
 WARRANTY OF ANY KIND. THE ENTIRE RISK AS TO RESULTS AND PERFORMANCE OF THE
 SOFTWARE IS ASSUMED BY YOU.

 MS-CSE will not be liable for any special, incidental, consequential, indirect
 or similar damages due to the loss of data, loss of business profits, business
 interruption or any other reason, even if MS-CSE or an agent of MS-CSE has
 been advised of the possibility of such damages.  In no event shall MS-CSE's
 liability for any damages ever exceed the price paid for the license to use
 the software, regardless of the form of the claim.

 MS-CSE warrants that the medium upon which the Software is provided by MS-CSE
 to User shall be free from defects in materials and workmanship under normal
 use for a period of sixty (60) days from the date of receipt.

 MS-CSE's entire liability and your exclusive remedy shall be at MS-CSE's
 option, either to:  a.) replace of any defective medium upon its return to
 MS-CSE within the warranty period; or b.) refund of the license fee paid by
 User.

 Because laws may vary between jurisdictions, you may have different or other
 legal rights regarding this matter. If any provision of this Agreement is
 found void, invalid or unenforceable, it will not affect the validity of the
 balance of this Agreement, which shall remain valid and enforceable according
 to its terms.

 (Support)

 On-line support for registered users is available via Internet (email). These
 will be answered on a "best effort" basis.

 (General)

 You may terminate your license at any time, MS-CSE may terminate your license
 if you fail to comply with the terms and conditions of this license.  In
 either event, you must destroy all your copies of the Program.

 You are responsible for payment of any taxes, including personal taxes,
 resulting from this license.

 Neither party may bring an action, regardless of form, more than two years
 after the cause of action arose.

 If you acquired the Program in the United States, this license is governed by
 the laws of the State of New York.  If you acquired the Program in Canada,
 this license is governed by the laws of the Province of Ontario.  Otherwise,
 this license is governed by the law of the country in which you acquired the
 Program.


ΓòÉΓòÉΓòÉ 5. Where can I get more informations ΓòÉΓòÉΓòÉ

Here are some WWW-Links to informational pages of different subjects.

The official EDis homepage:

     http://www.informatik.tu-muenchen.de/~schwarma/edis.html

 You can reach Martin Schwarz via WWW:

     http://www.informatik.tu-muenchen.de/~schwarma/

 You can reach the TU-MБnchen (Technical University, Munich, Germany) via WWW:

     http://www.leo.org

     http://www.informatik.tu-muenchen.de

 You can reach IBM via WWW:

     http://www.ibm.com

     http://www.ibm.de

 You can get information about SOM/DSOM via WWW:

     http://www.software.ibm.com/objects/somobjects/

     http://www.informatik.tu-muenchen.de/~schwarma/corba.html

 You can get information about OpenDoc via WWW:

     http://www.cilabs.org

     http://www.software.ibm.com/clubopendoc/