home *** CD-ROM | disk | FTP | other *** search
- INTRODUCTION
-
- This system demonstrates the use of OS/2 Dialog Manager. DM is a
- powerful alternative to writing native PM code to support CUA (GUI)
- applications of simple to moderate complexity. There are some
- significant limitations which make DM inappropriate for very complex
- panels or systems. However, for a great deal of the quickie type
- systems it is uniquely suited. Further, as this dialog demonstrates,
- it has the ability to put a CUA panel in front of a REXX exec. This
- gives you a very attractive and powerful application with little more
- effort than producing a DOS BATCH file.
-
- The DTL Markup is included. It should be easy to expand upon if
- you have the toolkit DTL compiler.
-
- This exec is intended primarily to be run from STARTUP.CMD. It
- display a DM panel. This panel provides choices of the OS/2
- EE Managers, which one might wish to be started at IPL time.
-
- If a feature will be needed EVERY time it would be better to add it
- to a menu and have PM kick it off during initialization. The
- purpose here is to allow for things that you need often but not
- always.
-
-
- REQUIRED FILES & DISK SPACE
-
- Oddly enough the DM runtime DLL's etc. are not under a separate license.
- However, IBM has not included them with the base OS/2 operating system.
- Rather, these files are shipped with the OS/2 Programmer's Toolkit.
- The file INIT_APP.ZIP contains all the executables and source for this
- application. If you have the toolkit or if you have already installed
- a DM application, this is all you will need. Otherwise, you must also
- download INIT_DSK.ZIP. This file should be UNZIPPED to a blank floppy.
- It will install ALL files and directories so DM can be installed with
- this application. Dialog Manager will require approx. 3MB of disk to
- install.
-
-
- POTENTIALLY NECESSARY MODIFICATIONS TO .CMD FILE
-
- LINES 42 - 47 MAY NEED TO BE MODIFIED TO REFLECT THE INSTALLATION
- PATHS FOR YOUR OS/2 SYSTEM. THE CURRENT SETTINGS ASSUME THE BASE
- OP SYS IS ON DRIVE C: WITH THE EE MANAGERS ON DRIVE E:. ALL
- DIRECTORY NAMES ARE ASSUMED TO BE THE OS/2 INSTALLATION DEFAULTS.
-
- IF YOU USE THE SUPPLIED INSTALL PROGRAM, OR MANUALLY COPY
- THE FILES INTO THE 'C:\DMAPP' DIRECTORY, YOU SHOULD ENSURE THAT
- 'C:\DMAPP' IS IN YOUR PATH. ALTERNATELY YOU MAY MOVE 'BEGIN.CMD'
- TO A DIRECTORY ON YOUR PATH. THIS IS THE ONLY FILE WHICH MUST
- RESIDE IN A PATH DIRECTORY.
-
-
- CHOOSING YOUR EDITOR
-
- Since everyone has his favorite editor, A command line argument
- may be supplied to cause the dialog to invoke whichever one is
- desired. If one is not supplied it will default to the system
- editor.
-
- Syntax: PMREXX INIT <editor name>
- NOTE: full editor path must be specified if
- the editor is not in PATH env variable
-
-
- COMMENTS
-
- If you find this program useful or have suggestions for its
- improvement I would appreciate hearing from you. I can be
- reached on Compuserve ID 70534,377.
-
-
- WARRANTY
-
- This is user supported code. ALL source code for the system is
- included. Hopefully, the use will find this instructive in the
- use of Dialog Manager; which I believe to be one of the best parts
- of OS/2. Ideally, it will also provide a useful function. However,
- no warranties are implied herein. Stated another way:
-
- BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
- WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
- LAW. THIS PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY
- KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED
- TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
- A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
- PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
- PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
- REPAIR OR CORRECTION.
-