Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!apple!vsi1!frame!glc
From: glc@frame.UUCP (Greg Cockroft)
Newsgroups: comp.sys.next
Subject: Re: Where's the Bits
Message-ID: <3565@frame.UUCP>
Date: 28 Jul 89 10:06:56 GMT
Reply-To: glc@frame.com (Greg Cockroft)
Distribution: usa
Organization: Frame Technology Corp. San Jose, Calif.
Lines: 29
Disclaimer: Author Is Responsibility For Contents


>I know what's going on.  With all due respect, you are barking up
>the wrong tree.  To paraphrase James Gosling, "Pixels are bad for
>you."

Yes, but even NeWS ended up with the setrasteropcode operator, because the
ideal is not always practical.

>Just out of curiosity, what is the fancy effect you are trying to
>achieve that neither Display PostScript nor compositing can do for
>you?

I want to have multiple greyscale images flipping simultaneously on the 
screen in realtime. The only way to do this in NeXTSTep is to create all
the images ahead of time and composite them onto the screen.

Here is another example where anti-pixel paranoia is harmful.

With the removal of initwindowalpha in 0.9, there is no way to invert a
rectangle quickly in NeXTStep. 

FrameMaker inverts rectangles around objects for object manipulation, because
it is non-destructive to possible objects drawn underneath.

The alternate way to do objects handles is to damage the area underneath.
This works fine if nothing complex is damaged, but in alot of cases this is
very slow.

	-greg.