Xref: utzoo comp.sys.next:19334 comp.graphics:18715
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!rosie!aozer
From: aozer@next.com (Ali Ozer)
Newsgroups: comp.sys.next,comp.graphics
Subject: Re: Lines in Postscript on the NeXT
Keywords: Lines,antialiasing,Postscript
Message-ID: <1004@rosie.NeXT.COM>
Date: 20 Jun 91 06:31:26 GMT
References: <1991Jun17.054324.11804@slate.mines.colorado.edu>
Sender: news@NeXT.COM
Followup-To: comp.sys.next
Organization: Next Computer, Inc.
Lines: 19
Nntp-Posting-Host: twinpeaks.next.com

In article <1991Jun17.054324.11804@slate.mines.colorado.edu> Friedel Michael writes:
>... write bitmap graphics straight to a buffer and flush the buffer to the 
>screen. Does anyone know an efficient way of doing this in Postscript ...

Pretty much the only way to get bitmap graphics to PostScript is the
image operator, or better yet, its AppKit counterparts: The
NXImageBitmap() function and the NXBitmapImageRep class.  You can
pretty much create a buffer of any depth (grayscale, RGB, or CMYK, 1,
2, 4, or 8 bits per component) and do your own drawing, and then image
it down to PostScript.

Under NeXTstep 2.x it turns out that imaging can be real efficient if
the depth & configuration of the bitmap matches that of the window
you're imaging into.  Thus it might be a good idea to ask for the 
characteristics of the window you're going to draw the bitmap in and
create a buffer of the same depth...

Ali, Ali_Ozer@NeXT.com