Path: utzoo!attcan!uunet!pmafire!uudell!milano.sw.mcc.com!cs.utexas.edu!helios!tamuts!n138ct
From: n138ct@tamuts.tamu.edu (Brent Burton)
Newsgroups: comp.sys.mac.misc
Subject: Re: System 7.0 vs. NeXT Step
Summary: my pipe idea is different
Keywords: pipes
Message-ID: <11518@helios.TAMU.EDU>
Date: 25 Jan 91 22:49:34 GMT
References: <5646@idunno.Princeton.EDU> <11492@helios.TAMU.EDU> <1991Jan24.205341.5563@zaphod.mps.ohio-state.edu>
Sender: usenet@helios.TAMU.EDU
Followup-To: comp.sys.mac.misc
Distribution: comp
Organization: Texas A&M University
Lines: 26

In article <1991Jan24.205341.5563@zaphod.mps.ohio-state.edu> edgar@shape.mps.ohio-state.edu (Gerald Edgar) writes:
>s.TAMU.EDU>

> [my idea of piping info (graphics or text - just tagged info) between
>  macprograms]
>
>And while you are at it, why not call it "Clipboard"?
>
>Sometimes I use MacroMaker to automatically Cut or Paste for me.

The clipboard is not the same.  The clipboard allows you (the user) to
place information between programs.  This is not piping; it's like
saving a text file in Word and opening it in Works.

Piping is the transfer of information between two programs while they
are running and is not typically controlled by the user, unlike
copying and pasting.  The user doesn't need to know what is happening,
except that the information is appearing 'over here' now.

I don't really know any more details about how this would truly work
because this is just a simple idea I dreamed up while rambling.

             +----------------------+------------------------+
             | Brent Burton         | n138ct@tamuts.tamu.edu |
             | Computer Sci/Physics +------------------------+
             | Texas A&M University | brentb@nuchat.UUCP     |