Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!bloom-beacon!dprg-330.GOVt.shearson.COM!fgreco
From: fgreco@dprg-330.GOVt.shearson.COM (Frank Greco)
Newsgroups: comp.windows.x
Subject: Re: A tirade about inefficient software & systems
Message-ID: <9011072333.AA17805@islanders.>
Date: 7 Nov 90 23:33:32 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 25

> >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.
> 

	What Paul is describing is also true for rendering 
	NeWS in an XView CANVAS under OpenWindows.

	And, no X extensions are involved; you're guaranteed to get PS
	rendering with OW.



	Frank G.

	X Extensions = Batteries not (always) included