Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!decwrl!adobe!asente
From: asente@adobe.com (Paul Asente)
Newsgroups: comp.windows.x
Subject: Re: A tirade about inefficient software & systems
Message-ID: <7883@adobe.UUCP>
Date: 1 Nov 90 19:06:14 GMT
References: <9011010052.AA05115@zia.aoc.nrao.edu>
Sender: news@adobe.COM
Organization: Adobe Systems Inc.
Lines: 16

In article <9011010052.AA05115@zia.aoc.nrao.edu> cflatter@ZIA.AOC.NRAO.EDU (Chris Flatters) writes:
>Working against NeWS (and presumably Display PostScript) is the fact that
>they impose the PostScript imaging model on their clients, which may not
>be appropriate for some applications.

Not true for Display PostScript, at least as it exists on DEC and IBM boxes
(i.e. as an X extension, as opposed to NeXT, where it's the whole window
system).  You can freely intermingle PostScript and X calls to achieve the
results you want.  For example, a useful programming technique is to use
PostScript to image into a pixmap and use XCopyArea to blit portions or all
of the pixmap into an X window -- this gives you smooth animation since it
works as double buffering.  Especially useful for dragging outlines of
complicated shapes around.

	-paul asente
		asente@adobe.com	...decwrl!adobe!asente