home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
gbase321.zip
/
README.WIN
< prev
Wrap
Text File
|
1995-10-19
|
17KB
|
394 lines
____________________________________________________________________
********************************************************************
____________________________________________________________________
Technical README for Windows
Welcome to Guidelines version 3.2 technical notes.
Version Comment
────────────────────────────────────────────────────────────────────────
3.2 25/08/95 RAP Created
____________________________________________________________________
********************************************************************
____________________________________________________________________
─ CONTENTS ───────────────────────────────────────────────────────────────
────────
1.0 Using GUI files from previous Guidelines versions.
2.0 Third party tools and Guidelines.
3.0 Running applications generated by previous Guidelines releases.
4.0 Running generated Windows applications on OS/2 Warp.
5.0 Running generated Windows applications on DOS + Windows.
6.0 Development considerations for Windows applications.
7.0 Notes on Designer (for Windows compilers)
8.0 Extra information - SQL.
9.0 Extra information - Image.
10.0 Extra information - Notes.
____________________________________________________________________
********************************************************************
____________________________________________________________________
──────────────────────────────────────────────────────
─ 1.0 USING GUI FILES FROM PREVIOUS GUIDELINES VERSIONS ─────────────────
──────────────────────────────────────────────────────
Guidelines 3.2 is able to use GUI files saved by earlier versions of
Guidelines, and will automatically convert older GUI formats to the
current format. Unless you use new controls, functions, or features
introduced by Guidelines 3.2, you may also use GUI files saved by
Guidelines 3.2 with Guidelines releases 3.1GA and 3.1GA+PIP.
─────────────────────────────────────
─ 2.0 THIRD PARTY TOOLS AND GUIDELINES ──────────────────────────────────
─────────────────────────────────────
The Guidelines Designer is now fully compatible with the popular 4DOS
aftermarket replacement command interpreter from JP Software.
Guidelines will now properly handle the case where you have installed
4DOS as your default command interpreter for Virtual DOS Machines and
you use a DOS-based compiler such as Borland C++ 4.0 or 4.5.
Because the batch file generated by the Guidelines Designer to run your
DOS compiler still must function with COMMAND, it is inadvisable for
4DOS users to alias standard commands such as IF, SET, PATH, and GOTO as
this may interfere with operation.
──────────────────────────────────────────────────────────────────
─ 3.0 RUNNING APPLICATIONS GENERATED BY PREVIOUS GUIDELINES RELEASES ────
──────────────────────────────────────────────────────────────────
Existing applications will not be affected by fixes and updates to the
Guidelines Runtime libraries unless they were created to use the
dynamic versions of those libraries. Applications that were created to
use the static versions of the runtime libraries will need to be
regenerated with Guidelines 3.2 and relinked with the latest static
runtime libraries in order to receive any benefit from this release of
Guidelines.
Existing applications generated by Guidelines releases 2.1a(65), 3.1GA,
and 3.1GA+PIP that were created to use the dynamic versions of the
Guidelines Runtime libraries will run over the libraries provided in
Guidelines 3.2.
Please note that you will not be able to run applications generated by
Guidelines 3.2 on top of earlier Guidelines Runtime libraries.
───────────────────────────────────────────────────────
─ 4.0 RUNNING GENERATED WINDOWS APPLICATIONS ON OS/2 WARP ────────────────
───────────────────────────────────────────────────────
In order for Guidelines to run programs, generated with one of the
Windows compilers, from within the Designer on OS/2 Warp 3.00 (either
Warp FullPack or Warp for Windows, including the Connect versions), the
default Win-OS/2 settings must be changed.
Under Warp, if a Windows program is run from the Designer when the
Seamless Sessions setting is enabled (from the Output|Options menu of
the Designer) and the Win-OS/2 settings are configured to not use
fastload or are configured to start Win-OS/2 in Standard Mode instead of
Enhanced Compatibility Mode, the Windows application may not start and a
SYS3175 error may occur. To correct this, and allow Windows programs to
be run on the Warp desktop from the Designer, either
(i) turn off the Seamless Sessions setting in Guidelines, or
(ii) "pre-load" an Enhanced Mode common session by running a Windows
application from the Workplace Shell desktop that has been
configured to run seamlessly on the desktop in Enhanced
Compatibility Mode (i.e. `Win-OS/2 Window' is checked in its
settings notebook, `Separate Session' is not, and WIN_RUN_MODE
in the settings dialogue is set to "3.1 Enhanced
Compatibility"), or
(iii) ensure that an Enhanced Mode common session is fast-loaded by
opening the `Win-OS/2 Setup' notebook in your `System Setup'
folder (accessible from the Desktop popup menu), turning on
`Fastload' and `Win-OS/2 Window', and ensuring that WIN_RUN_MODE
in the settings dialogue is set to "3.1 Enhanced Compatibility".
Guidelines generated Windows applications will then run when you select
the Run option from within Guidelines.
───────────────────────────────────────────────────────────
─ 5.0 RUNNING GENERATED WINDOWS APPLICATIONS ON DOS + WINDOWS ────────────
───────────────────────────────────────────────────────────
Running a Guidelines generated application on a DOS + Windows machine
requires you to install some of the Guidelines runtime support files on
that machine. This can be done as follows:
EITHER:
Use the Installer to load the runtime objects only for the packs
used by the application. This is the easiest method, but there is
a tendency for too much detail to be loaded this way.
OR:
( These instructions assume that your development machine has Guidelines
installed in C:\GUIDE and that you wish to install the Guidelines
runtime support onto drive C: on the target machine. The asterisks
mark steps that apply specifically to installing Client-Server Support
on the target machine which may be omitted if CSS is not required by
your application. )
1. Create a new directory tree on the target machine to contain the
Guidelines runtime files :
MD C:\GUIDE
MD C:\GUIDE\BIN
MD C:\GUIDE\DLL
MD C:\GUIDE\DATA
MD C:\GUIDE\HELP
2. Copy the following dynamic link libraries from the C:\GUIDE\DLL
directory on your development machine to C:\GUIDE\DLL on the
target machine:
All *WB*.DLL, *WB2*.DLL, and *WB3*.DLL.
Also all FCL*.DLL and GCWB*.DLL for CUA controls in Windows.
This will load up more than is necessary, but some Guidelines
Utilities require Borland 4.5 objects even when running in a
Borland 4.0 environment. The complexity of the setup means that
fully laying it out in text format would be too complicated and
subject to error.
3. Copy the Borland C++ runtime library DLLs (BC40RTL.DLL and
BC450RTL.DLL) from your development machine to C:\WINDOWS on the
target machine.
*4. Copy the following CSS programs from C:\GUIDE\BIN on your
development machine to C:\GUIDE\BIN on your target machine :
JCFW0000.EXE JCHW0000.EXE JCBW0000.EXE JCUW0000.EXE
EDTGTAB.EXE
*5. Copy the following CSS data files from C:\GUIDE\DATA on your
development machine to C:\GUIDE\DATA on your target machine :
GETCHRID.CLP FILESYN.DAT HOSTAPPL.DAT CODEPAGE.DAT
HOSTLINK.DAT APPLICAT.INI LOCATION.DAT JBAGTAB.DAT
USERHOST.DAT
*6. Copy the following CSS help files from C:\GUIDE\HELP on your
development machine to C:\GUIDE\HELP on your target machine :
CSSERR.MSG EDTGTAB.MSG ASU01OID.MSG
7. Ensure that SHARE is loaded in DOS by adding the following line to
CONFIG.SYS if it is not already present (normally this will have
been done for you when you installed DOS).
INSTALL=C:\DOS\SHARE.EXE
*8. Set the following variables in CONFIG.SYS (if you are using Novell
DOS 4.0 or earlier or Microsoft DOS 5.0 or earlier you may use
AUTOEXEC.BAT instead) :
SET BINDPATH=C:\GUIDE\BIN
SET JBAFILES=C:\GUIDE\DATA
SET JBAPASSWRD=C:\GUIDE\DATA
SET CSSXLAT=C:\GUIDE\DATA\JBAGTAB.DAT
SET CSSSYN=C:\GUIDE\DATA\FILESYN.DAT
SET CSSLOC=C:\GUIDE\DATA\LOCATION.DAT
SET CSSUSER=xxxxxxxxxx
where xxxxxxxxxx is the user profile defined as being the local
logon userid within CSS configuration (see below).
9. Add the following to the PATH statement in CONFIG.SYS (or
AUTOEXEC.BAT) :
C:\GUIDE\DLL;C:\GUIDE\BIN;C:\GUIDE\HELP
10. Reboot the machine so that the changes in AUTOEXEC.BAT and
CONFIG.SYS take effect.
*11. For ease of use, create a new program group in Program Manager
entitled "CSS Utilities" and create icons in that group for each
of the CSS utility programs as follows :
C:\GUIDE\BIN\JCFW0000.EXE "CSS Configuration"
C:\GUIDE\BIN\JCHW0000.EXE "Maintain Host Applications"
C:\GUIDE\BIN\JCBW0000.EXE "CSS Backup/Restore"
C:\GUIDE\BIN\JCUW0000.EXE "Maintain CSS Users"
C:\GUIDE\BIN\RSQ90WBD.EXE "SQL Configuration"
C:\GUIDE\BIN\JMCW0000.EXE "Message Class Browser"
*12. Run the CSS Configuration program (either from File Manager or
from the icons that you have set up in Program Manager) and
maintain the local logon user ID (xxxxxxxxxx).
You may now install and run your application.
───────────────────────────────────────────────────────
─ 6.0 DEVELOPMENT CONSIDERATIONS FOR WINDOWS APPLICATIONS ────────────────
───────────────────────────────────────────────────────
The manual 'Guidelines Programming for Microsoft Windows' supplied with
the Windows Code Enabler pack describes the major differences between
programming for OS/2 WARP and Microsoft Windows.
Help text
─────────
Guidelines will generate a HPJ (Help Project File) and a RTF (the
equivalent of an .IPF file). The Help compiler uses both of these
files to create the .HLP file. Partial IPF tag interpretation is
performed. As the IPF tags are not fully parsed (they are merely scanned
for keywords) any errors in the IPF code will more than likely generate
invalid RTF code.
The following tags are supported when Help text is compiled for Windows:-
Paragraphs :p
Hilited Phrases :hpn
Hyper-links :link (supports reftype hd (header) and fn (footnote))
Multiple fonts :font
Multiple Colors :color
Margins :lm (left margin) and rm: (right margin)
Bitmaps :artwork (linkfile/fit is ignored, center is runin)
Other tags .br (break) :xmp (all other tags are ignored
─────────────────────────────────
─ 7.0 NOTES ON GUIDELINES DESIGNER ──────────────────────────────────
─────────────────────────────────
══ Changes to directory structure ═════════════════════════════════════════════
The directory structure of the Designer has changed with this release.
Users upgrading from previous versions of Guidelines should read the
installation instructions that accompany the product and also :
1. Open the environment details dialogues for all of the compilers that
they use and modify the include and library paths to point to
\GUIDE\INCLUDE and \GUIDE\LIB respectively, instead of to \GUIDE\SYS.
2. Modify their GUE variable in \CONFIG.SYS to include \GUIDE\GUE on its
path.
3. Add \GUIDE\HELP to their DPATH in \CONFIG.SYS.
4. Ensure that LIBPATH in \CONFIG.SYS includes \GUIDE\DLL and not
\GUIDE\SYS.
══ Changes to compiler support ════════════════════════════════════════════════
1. This release now supports Borland C++ 4.5 for DOS+Windows. Users
installing Borland C++ 4.0 will automatically load Borland 4.5 as it
is used by Guidelines itself. The environment paths for the two
compilers must be separated. Follow the procedure below to set
the environments correctly:
(1) Bring up the Output|Environment... dialog.
(2) Select the compiler to be used and select [Edit] then [OK].
(3) Click on [Default] to reset to the new compiler options.
(4) Click on [Paths] and edit the environment variables, so that they
resemble the details below.
(5) Click on [OK].
(6) Click on [OK].
Sample Environment settings:
Key Description Example
<d> Drive and path for Guidelines c:\guide
<f> Drive and path for temp directory c:\temp
<g> Drive and path for Borland 4.0 c:\bc4
<h> Drive and path for Borland 4.5 c:\bc45
Environment Details for Windows Borland C++ 4.0
PATH=.;<g>\bin
INCLUDE=.;<d>\include;<g>\include
LIB=.;<d>\lib;<g>\lib
Environment Details for Windows Borland C++ 4.5
PATH=.;c:<h>\bin
INCLUDE=.;<d>\include;<h>\include
LIB=.;<d>\lib;c:<h>\lib
Note, if extensions have been installed in a directory <i>
which is not <d> then add
;<i>\include
to the end of each INCLUDE environment variable and
;<i>\Lib
to the end of each LIB environment variable.
══ Changes to using Guidelines ════════════════════════════════════════════════
1. People generating Windows applications may find several places where
behaviour that has a visual impact on their applications has been
fixed by the new Runtime. In particular, they may find that the
Activate() and the Dismiss() methods to work in the correct manner,
that child windows can now be activated (this is a Guidelines-supplied
extension to the functionality of "raw" Windows, which does not allow
windows other than top-level windows to be activated), and that the
behaviours of non-modal and child dialogues have been corrected.
2. Active windows function differently between Windows and Presentation
Manager. Whereas in PM all Windows between the focused window and
the desktop are active and will receive activation events (allowing dialogs
to be created in child windows and still respond correctly), in Windows,
only top-level windows may be active and will be sent activate events.
Guidelines 3.2 now provides the superior functionality of Presentation
Manager for Guidelines applications running on Windows. This is a change
from the previous version, where the native behaviour of both platforms
was adhered to.
3. The Guidelines Runtime has been enhanced to use 3D input fields. This
feature will be used on new and existing 3.1A applications as the runtime
is backwardly compatible. This function may be switched off at design time
by specifying not to use borders.
────────────────────────────────
─ 8.0 EXTRA INSTRUCTIONS FOR - SQL ──────────────────────────────────
────────────────────────────────
To load SQL for runtime use, the CSS environment variables BINDPATH and
JBAFILES are required. See the section on CSS environment variables above.
───────────────────────────────────────────────
─ 9.0 EXTRA INSTRUCTIONS FOR - NEW IMAGE EXTENSION ─────────────────
───────────────────────────────────────────────
The following files are also required for runtime installation of the
Image control:
FOMonImg FOColImg (all .DLLs)
GGLUWB*D.DLL (prerequisite for Image)
KF-911 software engine provided with image should be installed.
───────────────────────────────────
─ 10.0 EXTRA INSTRUCTIONS FOR - NOTES ───────────────────────────────
───────────────────────────────────
Note that most of the Lotus Notes functions use handles to files
and databases. Any handles passed as parameters MUST be valid,
otherwise a PC lock may result. This is especially noticeable
with closing files and databases.