Path: utzoo!utgpu!attcan!uunet!husc6!cmcl2!rutgers!bellcore!tness7!tness1!sugar!ficc!peter
From: peter@ficc.UUCP (Peter da Silva)
Newsgroups: comp.unix.wizards
Subject: Re: where to do line editing?
Message-ID: <1220@ficc.UUCP>
Date: 5 Aug 88 13:42:47 GMT
References: <678@gtx.com> <593@blblbl.UUCP> <8263@brl-smoke.ARPA> <611@tub.UUCP> <1495@mcgp1.UUCP>
Organization: SCADA
Lines: 34

In article <1495@mcgp1.UUCP>, fst@mcgp1.UUCP (Skip Tavakkolian) writes:
> He asked what would pipes be (take the place of pipes) in the context
> of icons.

Pipes should work just fine with icons. Better, even. You should just be able
to grab your file, awk, grep, hook them together with rubber band lines,
and hit "go". I'm amazed that nobody has implemented this yet.

> C++.  I also believe it would require another data
> abstraction, perhaps as widely accepted as the 8-bit-byte, that would have
> the ability to carry more information about a phenomenon or an entity.

Why? What are your reasons for deciding pipes are insufficient. What
facility is missing with pipes? Am I missing something major here?

I don't want to know about sockets and streams. I'm already aware of them.
I just don't see why the byte-stream model is suddenly obsolete just because
of a graphic user interface. Especially since nobody seems to have even
tried to implement graphic pipes.

It's not like nobody has thought of them. I brought the subject up about
4 or 5 years ago. Since then I've occasionally seen someone on comp.windows
or comp.graphics bring it up...

> Maybe it is time to start thinking about what kind of standard that could
> be.

Places to look: Macintosh clipboards. Amiga IFF files. The IPC discussion
on comp.sys.amiga.tech. Smalltalk objects. Macintosh resource files.
-- 
Peter da Silva, Ferranti International Controls Corporation, sugar!ficc!peter.
"You made a TIME MACHINE out of a VOLKSWAGEN BEETLE?"
"Well, I couldn't afford another deLorean."
"But how do you ever get it up to 88 miles per hour????"