Xref: utzoo comp.sys.next:938 comp.windows.news:1022
Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!amdcad!sun!pitstop!sundc!seismo!uunet!mcvax!unido!ecrcvax!andy
From: andy@ecrcvax.UUCP (Andrew Dwelly)
Newsgroups: comp.sys.next,comp.windows.news
Subject: Re: Re : Display PS vs NeWS
Keywords: NeWS is a superset of POSTSCRIPT!
Message-ID: <663@ecrcvax.UUCP>
Date: 19 Dec 88 09:40:32 GMT
References: <941@riddle.UUCP> <2391@ssc-vax.UUCP> <109@adobe.COM>
Reply-To: andy@ecrcvax.UUCP (Andrew Dwelly)
Organization: ECRC, Munich 81, West Germany
Lines: 30

In article <109@adobe.COM> greid@adobe.COM (Glenn Reid) writes:
 
>And also, Display PostScript has nothing to do with X windows, other
>than the ability to ge integrated into it.  The NeXT machine does not
>run X windows; it draws its windows with Display PostScript.

Ahh, this is interesting.

I just received the "Display Postscript preliminary documentation" (thanks
Glenn), which I have so far only had a chance to glance at. What I did notice,
however, is that input does not seem to be well supported. I understand, from
following various comments in this forum that the reason is that DPS is really
only meant for output, and supposed to run -with- a windowing system.

So now I'm confused. Users of NeXT and Glenn, would you say DPS is a suitable
basis for creating window systems with the associated paraphernalia ? would you
claim that it is one component from several, making up a WISIWYG sort of
interface? More pointedly, how does DPS support interaction between the cursor
and "interface objects" ?

Andy

Andrew Dwelly                 
E.C.R.C.                                       UUCP: mcvax!unido!ecrcvax!andy
ArabellaStrasse 17 			       or    pyramid!ecrcvax!andy
D-8000 Muenchen 81, West Germany 	       UUCP Domain:  andy@ecrcvax.UUCP

[Bump, Crash ......
 Listen; who swears ?
 Christopher Robin has fallen down stairs.]