streeter@ingr.UUCP (08/08/86)
[the line-eater is a myth. It does not e
My friends and I are trying to write our own CLI. This is not
really a problem, since most of what is necessary is fairly
straight-forward. However, it is our desire to run the CLI in an
80-column window, and this is where our problems lie. We can let
our CLI create itself a window, accept input from it and send output
to it with no problem. The problem is passing information about the
window to other programs run from the CLI. We have to pass them a
File Handle for their input and output.
In order to create an 80-column window one must use OpenWindow,
rather than fopen("CON:etc"). There is no (apparent) way to
associate this new window with a File Handle. We are not
Developers, so we have access only to published public
documentation. What we understand from our study is that AmigaDOS
talks to Handler Processes to do its I/O (the process ID of the
Handler Process is in the File Handle). It is apparent that a
Console Handler exists for this purpose, although it must be an
integral part of the system (i.e., there is not a file by that name
in the proper directory).
What I need to know is whether (and how) I can convince that Handler to
handle a window of my creation (not likely), or if I must (and if I
can) create my own window handler and link it into the system
tables, then ask AmigaDOS to open the window for me. Any help from
more knowledgeable individuals is requested/appreciated. Even the
"You're going about it all wrong!" variety is fine.
One more question while I'm asking; How does a CLI detach itself
from the process which created it? I suspect it invovles an
intermediate process which LoadSegs and CreateProcs the CLI, then
exits. Is this correct?
Guy Streeter
akgua!ingr!streeter