Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!sunybcs!ugpete From: ugpete@sunybcs.uucp (Peter Theobald) Newsgroups: comp.sys.amiga Subject: Re: Ban the Cloud! (plus sugg. for Workbench) Message-ID: <9247@sunybcs.UUCP> Date: 12 Mar 88 19:40:50 GMT References: <318@jc3b21.UUCP> <3624@bloom-beacon.MIT.EDU> <761@sandino.quintus.UUCP> Sender: nobody@sunybcs.UUCP Reply-To: ugpete@sunybcs.UUCP (Peter Theobald) Organization: SUNY/Buffalo Computer Science Lines: 27 Keywords: Workbench >> >(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. >How about this: >Output redirection: When a WB-started task produces output (to >stdout), a "magic window" is created. This window displays a scrolling >view of the output of the task. >Input redirection: The files you select (while holding the shift key) >before firing the WB tool are implicitly cat'd and sent to stdin of the >task. No problem. Also, you should be able to select a "magic window" >for input to a tool in the same way. How about new Workbench menu choices: 'redirect' and 'new file.' When you select 'redirect', you then point the mouse at the input file 'click', then draw an arrow towards the application, 'click'. Voila! An arrow represents the input redirection. Or you point at the application, 'click' and drag an arrow to a file, 'click'. You have just redirected output. Or put an arrow from an application to another application. This pipes the output of one to the input of the other. You could have a chain of arrows piping output through an arbitrary number of files and applications. To redirect output to a new as-of-yet-uncreated file, the 'new file' menu choice would simply create a blank file with an icon. Peter Theobald SUNY/Buffalo Computer Science internet: ugpete@cs.buffalo.edu bitnet: ugpete@sunybcs.BITNET uucp: ..!{ames,boulder,decvax,rutgers}!sunybcs!ugpete csnet: ugpete@buffalo.CSNET