home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 5 Edit
/
05-Edit.zip
/
idedll.zip
/
README.TXT
< prev
next >
Wrap
Text File
|
1995-11-23
|
4KB
|
88 lines
Files in this ZIP file:
CPELINK.C - Source code for the DLL
CPELINK.H
CPELINK.TGT - Watcom Target file for the CPELINK.DLL
CPELINK.WPJ - Watcom Project file for the CPELINK.DLL
README.TXT - This file
WATCOM.PEL - PEL file with support routines for the PREDITOR/2 package
This DLL will link the Watcom IDE to CompuWare's PREDITOR/2 editor. This is a
first pass at the DLL, and there are a few things that I know could be improved
with the interface, but it seems to provide the basic interface.
Please read the comments at the begining of the CPELINK.C file for information
on redistributing this software and other such issues.
I will happily attempt to answer any questions one might have about this DLL,
but I cannot make any promises about how long it will take, or the accuracy of
my answers. If you do make improvements to the code, I would certainly be
intersted in seeing them. You can email me at 76512,3213@compuserve.com.
To use this DLL, do the following:
1) Copy the CPELINK.DLL into some directory that is part of the LIBPATH
defined in your CONFIG.SYS. The \WATCOM\BINP\DLL directory is a good
choice.
2) Copy the WATCOM.PEL file to the PREDITOR/2 directory used to hold the PEL
files for the editor. The default directory is \CPE\PEL.
3) Add a line to the WPEL.RSP file (which should reside in the same directory
as the PEL files). The line should read:
WATCOM.PEL
This tells the PREDITOR/2 PEL Compiler that the WATCOM.PEL file should be
included as part of the next compilation of the eidtor's PEL files.
4) Run the MAKE_AE.CMD command file (which should also be in the same directory
as the PEL files). This will recompile the CPE.AE file that the editor
uses during its operations.
5) You should then shutdown any copies of the PREDITOR/2 editor that you are
running. The changes made to the CPE.AE file will only be active in copies
of the editor started *after* the new CPE.AE file was created.
6) Go into the Watcom IDE and click on the 'File' menu item in the menu bar. In
the pop-up menu that appears, there is an item label 'Set Text Editor'. Click
on that item. You should now have a dialog window that is asking you to supply
the name of the DLL or executable to use within the IDE to access the editor.
7) In the box labeled 'Enter Editor File Name:' type in 'CPELINK' (do *not* include
the quotes, only the seven-letter name). In the box labeled 'Editor Type', click
on the radio button labeled 'DLL'.
8) Click on the 'OK' button and you're ready to go.
Known Problems:
The PREDITOR/2, version 2.1, does not send WM_DDE_TERMINATE messages to clients
when it terminates. Therefore, you should avoid terminating the editor before
terminating the IDE. Starting up the editor from within the IDE and then
terminating the editor can result in the IDE telling you that it cannot access
the editor. The error will not go away until you shut down the IDE and then
restart it.
The EDITSaveFiles function doesn't do anything at the moment. Therefore, if you
have modified files in the editor, you must remember to save them before instructing
the IDE to compile.
It is possible that once this DLL is loaded into memory, it will *never* be removed
until the machine is rebooted (I haven't had a chance to check this yet). This shouldn't
actually cause a problem other than the memory it occupies (which shouldn't be that much,
really).
On slower machines, the editor might not have enough time to load and initialize
before the IDE will give up on trying to contact it. This problem can be
solved by editing the CPELINK.C file and changing WAITTIME constant to a larger
value (WAITTIME is the number of seconds to wait for the PREDITOR/2 editor to
load and initialize). You will then need to recompile the DLL and copy the new
DLL over the old DLL (which you will not be able to do while the IDE is running).
Everything within this DLL is based upon one sample DLL that was written for the
Windoze environment and my own experimentation. Therefore, who knows if this DLL
will work in all situtations. I think it will, but since Watcom couldn't be bothered
to respond to any of my inquiries about how the editor DLL is used from the IDE, I
just don't know for sure.