home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
gbasedoc.zip
/
README.OS2
< prev
next >
Wrap
Text File
|
1995-10-19
|
19KB
|
443 lines
____________________________________________________________________
********************************************************************
____________________________________________________________________
Technical README - OS/2
Welcome to Guidelines version 3.2 technical notes.
Version Comment
────────────────────────────────────────────────────────────────────────
3.2 16/10/95 RAP Creation
____________________________________________________________________
********************************************************************
____________________________________________________________________
─ 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 OS/2 applications on OS/2 Warp.
5.0 Notes on OS2 Designer
6.0 Extra instructions for - SQL.
7.0 Extra instructions for - Image.
____________________________________________________________________
********************************************************************
____________________________________________________________________
──────────────────────────────────────────────────────
─ 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.
Please Note: Some Product Improvements may not be available without
regeneration and recompilation of application code.
─────────────────────────────────────
─ 2.0 THIRD PARTY TOOLS AND GUIDELINES ──────────────────────────────────
─────────────────────────────────────
The Guidelines Designer is now fully compatible with the popular 4OS2
aftermarket replacement command interpreter from JP Software.
Object Desktop, the Workplace Shell enhancement product from StarDock
systems, has been tested by StarDock and is fully compatible with the
Guidelines Designer and generated OS/2 applications. The NPS Workplace
Shell enhancer is also compatible with the Guidelines Designer and
generated OS/2 applications.
──────────────────────────────────────────────────────────────────
─ 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.
If you intend to run OS/2 applications created by previous releases of
Guidelines over the Guidelines 3.2 Runtime libraries, you *must*
ensure that you replace the GUICRT.DLL provided by the earlier release
by the GUICRT.DLL provided with Guidelines 3.2. Using an older
version of GUICRT.DLL with the Guidelines 3.2 Runtime may cause
program errors. The current GUICRT.DLL is now a forwarder DLL, provided
for backwards compatibility only, which forwards to GCRTOI2D.DLL.
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 OS/2 APPLICATIONS ON OS/2 WARP ──────────────────
─────────────────────────────────────────────────────
Running a Guidelines generated application on an OS/2 machine that does
not have Guidelines installed 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 Guidelines dynamic link libraries from the
C:\GUIDE\DLL directory on your development machine to C:\GUIDE\DLL
on the target machine:
All *OI*.DLL, *OI1*.DLL, and *OI2*.DLL
This will load up more than is necessary, but some IBM VisualAge
objects (*OI2*) are forwarder objects for IBM Cset 2.01. 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 following CSS programs from C:\GUIDE\BIN on your
development machine to C:\GUIDE\BIN on your target machine :
JCFO0000.EXE JCHO0000.EXE JCBO0000.EXE JCUO0000.EXE
*4. 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 MSG*.IDX MSG*.DAT RSQ*.ICO
JCFO0000.ICO JCHO0000.ICO JCBO0000.ICO JCUO0000.ICO
JOT3.ICO
*5. Copy the following CSS help files from C:\GUIDE\HELP on your
development machine to C:\GUIDE\HELP on your target machine :
JCFO0000.HLP JCHO0000.HLP JCBO0000.HLP JCUO0000.HLP
6. Refer to the extra sections if SQL or Image extensions are required.
7. Add the following to the LIBPATH statement in CONFIG.SYS :
C:\GUIDE\DLL
8. Add the following to the SET PATH statement in CONFIG.SYS :
C:\GUIDE\BIN
9. Add the following to the SET DPATH statement in CONFIG.SYS :
C:\GUIDE\HELP
10. Add the following to the SET HELP statement in CONFIG.SYS :
C:\GUIDE\HELP
*11. Set the following variables in CONFIG.SYS :
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).
12. Shut down and restart the machine so that changes in CONFIG.SYS
take effect.
*13. For ease of use, create new program objects in Workplace Shell
for the CSS utility programs that you copied earlier :
C:\GUIDE\BIN\JCFO0000.EXE "CSS Configuration"
C:\GUIDE\BIN\JCHO0000.EXE "Maintain Host Applications"
C:\GUIDE\BIN\JCBO0000.EXE "CSS Backup/Restore"
C:\GUIDE\BIN\JCUO0000.EXE "Maintain CSS Users"
C:\GUIDE\BIN\RSQ90OXX.EXE "SQL Configuration"
C:\GUIDE\BIN\JMCO0000.EXE "Message Class Browser"
You can create the new program objects by dragging and dropping a
Program template from your Templates folder, or by running the
following REXX script (copy and paste from this document and save
as a CMD file) from the command line:
/*Script start*/
/* Script to create CSS utility program objects on the Workplace */
/* Shell desktop on a target machine without Guidelines installed. */
/* (c) Copyright 1995 JBA Software Products. All rights reserved. */
call RxFuncAdd 'SysCreateObject', 'RexxUtil', 'SysCreateObject'
if \ SysCreateObject("WPProgram","CSS Configuration","<WP_DESKTOP>",
,"OBJECTID=<GUIDELINES_CSS_CONFIG>;",
||"EXENAME=JCFO0000.EXE;",
||"ICONFILE=C:\GUIDE\DATA\JCFO0000.ICO",
,"Update")
say "CSS Configuration program object creation failed!"
if \ SysCreateObject("WPProgram","Maintain Host Applications",
,"<WP_DESKTOP>",
,"OBJECTID=<GUIDELINES_HOST_MAINT>;",
||"EXENAME=JCHO0000.EXE;",
||"ICONFILE=C:\GUIDE\DATA\JCHO0000.ICO",
,"Update")
say "Host Apps program object creation failed!"
if \ SysCreateObject("WPProgram","CSS Backup/Restore","<WP_DESKTOP>",
,"OBJECTID=<GUIDELINES_CSS_BACKUP>;",
||"EXENAME=JCBO0000.EXE;",
||"ICONFILE=C:\GUIDE\DATA\JCBO0000.ICO",
,"Update")
say "CSS Backup/Restore program object creation failed!"
if \ SysCreateObject("WPProgram","Maintain CSS Users","<WP_DESKTOP>",
,"OBJECTID=<GUIDELINES_CSS_USERS>;",
||"EXENAME=JCUO0000.EXE;",
||"ICONFILE=C:\GUIDE\DATA\JCUO0000.ICO",
,"Update")
say "CSS Users program object creation failed!"
if \ SysCreateObject("WPProgram","CSS Configuration","<WP_DESKTOP>",
,"OBJECTID=<GUIDELINES_CSS_CONFIG>;",
||"EXENAME=JCFO0000.EXE;",
||"ICONFILE=C:\GUIDE\DATA\JCFO0000.ICO",
,"Update")
say "CSS Configuration program object creation failed!"
if \ SysCreateObject("WPProgram","SQL Configuration","<WP_DESKTOP>",
,"OBJECTID=<GUIDELINES_SQL_CONFIG>;",
||"EXENAME=RSQ90OXX.EXE;",
||"ICONFILE=C:\GUIDE\DATA\RSQ90OXX.ICO",
,"Update")
say "SQL Configuration program object creation failed!"
if \ SysCreateObject("WPProgram","Message Class Browser",
,"<WP_DESKTOP>",
,"OBJECTID=<GUIDELINES_MSG_BROWSER>;",
||"EXENAME=JMCO0000.EXE;",
||"ICONFILE=C:\GUIDE\DATA\JMCO0000.ICO",
,"Update")
say "Message Browser program object creation failed!"
/*Script end*/
*14. 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.
─────────────────────────────────
─ 5.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 IBM VisualAge C++ 3.00. Users installing
IBM CSet++ 2.01 will automatically load VisualAge 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
<a> Drive and path for OS2 c:\os2
<b> Drive and path for OS2 Toolkit c:\toolkt21
<c> Drive and path for CSet 2.01 c:\ibmcpp
<d> Drive and path for Guidelines c:\guide
<e> Drive and path for Visual Age 3.00 c:\ibmcpp30
<f> Drive and path for temp directory c:\temp
Environment Details for OS/2 IBM CSet++ 2.01
COMSPEC=<a>\cmd.exe
PATH=.;<b>\os2bin;<c>\bin
DPATH=.;<b>\ipfc;<c>\locale;<c>\help;<c>\sys
INCLUDE=.;<d>\include;<b>\cplus\os2h;<c>\include;<c>\ibmclass
LIB=.;<d>\lib;<b>\os2lib;<c>\lib
IPFC=<b>\ipfc
TMP=<f>
Environment Details for OS/2 IBM VisualAge C++ 3.00
COMSPEC=<a>\cmd.exe
PATH=.;<e>\bin
DPATH=.;<e>\locale;<e>\help;<e>\sys
INCLUDE=.;<d>\include;<e>\include;<e>\include\os2
LIB=.;<d>\lib;<e>\lib
IPFC=<e>\ipfc
TMP=<f>
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.
2. Guidelines now attempts to link using the compiler driver wherever
practical rather than calling the linker directly. This means that
some of the compiler command lines have changed. This means that
makefiles for IBM CSet++ 2.01 and IBM VisualAge C++ 3.00 will
now work the same way. Users of IBM CSet++ 2.01 that have upgraded
from a previous version of Guidelines should open the Environment
Details dialog for that compiler and click on the [Default] button to
reconfigure the command lines.
══ Changes to using Guidelines ════════════════════════════════════════════════
1. Multiline JOT comments are now available. The `{*' pair will begin a
multiline comment, and the '*}' pair must occur somewhere later in the
same action module to terminate it. The `C:' prefix for embedded C++
and the ';' single-line comment character will not be treated
specially within a multiline JOT comment.
A second comment style, the `{**}' pairs were chosen over the C++
`/**/' or Modula `(**)' comment delimiters because those latter may
occur as part of legal JOT code.
2. Warning Error in RC Compile due to FID_CLIENT
The header where FID_CLIENT is defined is part of the OS/2
Developers' Toolkit. It appears that although the resource
compiler is using the new C++ rules for manifest constants,
the OS/2 headers have not been updated to reflect this. To
be raised with IBM.
3. Variable 'y1' no longer allowed after recompile on 3.2
Certain functions now include the math.h file during compilation.
'y1' is a standard global variable of this file. Standard C library
functions such as these (and many more like 'abort', 'exit',
'rand', 'free' etc) must be avoided by developers. The full
list of these can be found in the compiler manuals.
4. I cannot link my IBM CSet++ 2.01 applications any more ! I get strange
errors about files called "-Feblah.exe".
This is because linking with the IBM C++ compilers is no longer
performed by calling the linker directly. In the environment details
dialog for IBM CSet++ 2.01 (under Output|Environment...) click on
the [Default] button, which will correct the linker command line.
5. On OS/2 2.1x the control co-ordinates on the Designer window are not
updated dynamically as I drag and drop controls about !
This is due to the internal changes in Presentation Manager between
OS/2 2.x and OS/2 3.x. For the technically minded, the reason is that
during a WinTrackRect call OS/2 2.x updates the 16-bit version of the
tracking structure, whereas OS/2 3.x updates the 32-bit version of the
tracking structure. Guidelines 2.10a(65) was the last release to
support the 16-bit PM structures. The solution is to upgrade to OS/2
3.x.
6. Guidelines is no longer generating my LNK files !
Only DOS compilers have a 127 character command line length limit.
Guidelines now places all files and options on the command line when
linking using an OS/2 compiler, instead of generating response files.
7. My application keeps reporting "Window not loaded" errors !
A common applications programming error is to use a property of a
window before it has been loaded (either via .Invoke() or .Load()).
The most common instance of this mistake is to set the .Parent
property of a window and then to .Load it (set the .Parent property
after loading, instead).
Whereas previous versions of the Guidelines Runtime would only note
some accesses to properties of unloaded windows, this version will
note *all* such accesses. So errors that went unreported before will
now be reported to you.
─────────────────────────────────
─ 6.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.
───────────────────────────────────────────────
─ 7.0 EXTRA INSTRUCTIONS FOR - NEW IMAGE EXTENSION ─────────────────
───────────────────────────────────────────────
The following files are also required for runtime installation of the Image
control:
FOMonOS2 FOColOS2 KIPPO* KSEO (all .DLLs)
____________________________________________________________________
********************************************************************
____________________________________________________________________