Path: utzoo!attcan!uunet!husc6!rutgers!iuvax!mailrus!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.windows.x
Subject: Re: XPutPixel
Message-ID: <1088@cps3xx.UUCP>
Date: 15 Nov 88 18:00:53 GMT
References: <8811151509.AA07399@godot.radonc.unc.edu> <8811151539.AA02975@EXPO.LCS.MIT.EDU>
Reply-To: flynn@pixel.cps.msu.edu (Patrick J. Flynn)
Organization: Computer Science, Mich. State University
Lines: 22

In article <8811151539.AA02975@EXPO.LCS.MIT.EDU> rws@EXPO.LCS.MIT.EDU (Bob Scheifler) writes:
>
>   Yes, I know they're important, but then so are 12-bit CT images.
>
>Sure.  It's also good to keep in mind that XImages were not designed
>to handle real image processing needs (which is not to say that it
>shouldn't do what it does a whole lot faster).

OK, I'll bite. Is there any work going on that addresses image processing
needs? I recall that DEC is in charge of an image processing protocol
extension.  What's the status of this?  Are there draft documents that
describe such an extension? But if I'm going to sell X as a display
platform for image processing to my research group,
it'd be nice if I knew what else was going on out there.

(I'm kind of partial to 8-bit range data myself) ;-)

thx,
--
Patrick Flynn, Dept. of Computer Science, Michigan State University
flynn@cpsvax.cps.msu.edu flynn@eecae.UUCP FLYNN@MSUEGR.BITNET
"First we break 'em in half.... then we mash 'em to a pulp."