From Darin McBride · 1996-04-06 15:57 · #73550 in EMULATE
In reply to New Asm,C++,C,68000,FORTRAN,HTML,... e by Paul Rider
PR> The menus are configured very simply to call your
PR> favorite compilers, assemblers, linkers, debuggers, and
PR> even to run your final version when it is done...
I wonder if we could make it smart enough to 'learn' what messages to send (using WinSendMessage) to force a compile from a GUI IDE.
Question: Is this PM-based? If so, it would be great - the only PM-based C/C++ editors I know of are Borland's IDE and EPM 6.xx (when you can figure out how to do it). What I would suggest (and, hell, yes, I would want to beta test it if you can make it available via internet rather than just F'REQ) is to allow macros similar to EPM's (type in 'if' and it fills in, for example, 'if () /* */
{
*
}
else
{
} /* end if */
'
and leaves the cursor at the '*'. BUT MAKE THIS CHANGEABLE because, for example, I prefer:
'if () { /* */
*
} else {
} /* end if */
'
Another feature that I'm now used to in FTE is auto-indent. Hit a key, and it indents the row properly. For example:
function_call( <--- hit enter here
*<--- cursor moves to here
or
for (...) <--- hit enter here
macro fills in, and ...
for (...) {
* <--- leaves cursor here
} <--- hit enter here
* <--- leaves cursor here
function_call_without_semicolon(...) <--hit enter here
* <--- leaves cursor here (good hint for lack of semicolon <G>
if (...) {
* <--- leaves cursor here. Hit '#' and it becomes:
if (...) {
#* <---- leaves cursor here.
If you want a copy of FTE (freeware, AFAIK), I will send it to you via email (uuencoded). Just leave an address...
It has many good features, but its main drawback: TEXT BASED.
Also, see if you can make your editor DLL-based for Watcom users. :-) If not, always make sure you can specify line-number and row-number on the command line. Further, an option, if it is not DLL based, to check for its own existance would be nice... for example, if I am editting FOO.C, and I 'run' your editor telling it to be on line 215, column 9 and to load FOO.C all from the commandline, it should look in the process list, find that it is already editting FOO.C and, if the user has turned on 'only load files once', it will send a message to the original edit window to go to 215,9 and then exit itself. Or, perhaps, you could have that as a tri-state question ... optionally asking the user at each occurance whether she wants to open a new edit window, or modify the original one. (If there already are two edit windows on the same file open, forget it... don't ask, open a third.) Oh, and make sure that I can edit FOO.C in C:\SRC as well as a FOO.C in C:\SRC\PROJECT ... and that it doesn't move the cursor in the wrong foo.c... :-)
Just a little wish list, Paul... but as you can see, I've been looking for this for a long time - but I've never sat down to make it myself. :-)
--- Maximus/2 3.01
* Origin: Tanktalus' Tower BBS (PVT) (1:342/708)