Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!mailrus!tut.cis.ohio-state.edu!rutgers!mtune!mtunx!whuts!homxb!hropus!ki4pv!codas!usfvax2!jc3b21!fgd3 From: fgd3@jc3b21.UUCP (Fabbian G. Dufoe) Newsgroups: comp.sys.amiga Subject: Re: Ban the Cloud! (plus sugg. for Workbench) Message-ID: <348@jc3b21.UUCP> Date: 24 Mar 88 04:34:46 GMT References: <318@jc3b21.UUCP> <761@sandino.quintus.UUCP> Organization: St. Petersburg Jr. College, FL Lines: 28 Keywords: Workbench Summary: Let me clarify how the redirection icons would work. In article <761@sandino.quintus.UUCP>, pds@quintus.UUCP (Peter Schachte) writes: > In article <3624@bloom-beacon.MIT.EDU>, cthulhu@athena.mit.edu (Jim Reich) writes: > > In article <329@jc3b21.UUCP> fgd3@jc3b21.UUCP (Fabbian G. Dufoe) writes: > > >(4) Workbench doesn't have the CLI's provisions for I/O redirection. > > >How about two special icons on the Workbench screen: "<" and ">". > > >... Drop a file on one and I/O is redirected to or from that file. > > Bad bad bad. Each program should be allowed to have its own > > output or input redirected from/to different sources. Perhaps I didn't make myself clear. The special icons "<" and ">" would simply pass the redirection instructions along when the program was started. Once one program was started you could use the icons again to start another program without interfering with the redirection that was already set up in the first case. In fact, the concept is the same as with the CLI. Under the CLI you use the redirection symbols "<" and ">" whenever you want them on a command line. You don't have to wait until that program is finished before you can use them on another command line (assuming you know how to use "NewCLI" or "Run". I agree that each program should be allowed to have its own output or input redirected from different sources. I believe my suggestion would provide for that. --Fabbian Dufoe 350 Ling-A-Mor Terrace South St. Petersburg, Florida 33705 813-823-2350 UUCP: ...gatech!codas!usfvax2!jc3b21!fgd3