Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utcs!oscvax!rico
From: rico@oscvax.UUCP
Newsgroups: net.micro.amiga
Subject: Re: Some wishes
Message-ID: <423@oscvax.UUCP>
Date: Mon, 23-Jun-86 09:59:47 EDT
Article-I.D.: oscvax.423
Posted: Mon Jun 23 09:59:47 1986
Date-Received: Mon, 23-Jun-86 17:11:44 EDT
References: <1868@gitpyr.UUCP> <398@cbmvax.cbmvax.cbm.UUCP> <420@oscvax.UUCP> <548@3comvax.UUCP>
Reply-To: rico@oscvax.UUCP (Rico Mariani)
Organization: Ontario Science Centre, Toronto
Lines: 58
Summary: make a more general con: device

In article <548@3comvax.UUCP> mykes@3comvax.UUCP (Mike Schwartz) writes:
>I hope that there is still a chance to get this question answered:  how
>can you get a CLI to work in the window of your choice?  I swear I've read
>every page of the AmigaDos manuals, and searched through header files and
>everything. 
>
>I would like to finish MyCLI the way a CLI should be for the Amiga
>(sorry but it is not Unix style - which may be a good idea:) with pulldown
>menus for simple commands, a close gadget to use instead of EndCLI,
>full-time directories on screen (tag & delete a bunch at a time), etc.
>
>
>OK, so here is how far I have gotten:
>	1. open custom screen
>	2. open custom window with desired gadgets & menus
>	3. open a console.device to work with window
>
>At this point, I give up.  I want to use Execute() to run a program, but
>I want to REDIRECT it's input and output to MY WINDOW.  Is there a sanctioned
>way of doing this?  I have seen several people make similar requests, 
>especially those who have worked on CLI replacements (Matt Dillon, for one).
>CLI may have been an afterthought, but it is clearly getting the most
>programs written for it (sad but true), and being able to get Intuition and
>CLI to work together makes a lot of sense.

I've been thinking that I want to do something very similar to what you're
talking about.  I was planning on using an icon based system though... kind
of like a programmers workbench that shows *everything*, not just files
with associated .info files.  

Now, about attaching a CLI to a custom screen/window... well I don't think
it can be done with the existing device drivers.  As I see it, the problem
is that the CLI wants to be attached to something in the AmigaDOS filing
system (it really likes con: windows).  Since con: windows are not general
enough (are they??) to attach to custom screens (ie. they must live in
the workbench and use the system font and... and... and...) you are kind
of stuck.  My solution?  Well since I just (this weekend) figured out
how to tell AmigaDOS how to find my very own device handler, I can
now go about writing a more general console-ish thing.  One that would
allow you to attach to *any* window in *any* screen and use your very
own favourite font and other IntuiThings.  Sorry I can't promise a
delivery date on this thing, it could be yet another project that Rico
starts but never finishes.  Feel free to steal the idea (if you feel
guilty about doing this, also feel free to name your firstborn son
after me :-) ).

Has anyone heard anything about the pipe: handler that was promised
way back when and a long time ago (are you listening John Toebes??).
Does anyone know anything about the Pipe-Handler file that is mentioned
in the 1.2 Beta2 file listings?  It says that it's supposed to be in
the l: (I think) directory of the Workbench disk, but it's nowhere
to be seen.  What gives?

	-Rico

	...{ihnp4|allegra|decvax|watmath|linus}!utzoo!oscvax!rico

DISCLAIMER:  This article is not the Science Centre's fault... leave them alone.