Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!oz.cis.ohio-state.edu!jgreely From: jgreely@oz.cis.ohio-state.edu (J Greely) Newsgroups: comp.sys.next Subject: Re: Where's the Bits Message-ID: Date: 27 Jul 89 15:58:18 GMT References: <3562@frame.UUCP> Sender: news@tut.cis.ohio-state.edu Reply-To: J Greely Distribution: usa Organization: Ohio State University Computer and Information Science Lines: 28 In-reply-to: glc@frame.UUCP's message of 27 Jul 89 10:30:06 GMT In article <3562@frame.UUCP> glc@frame.UUCP (Greg Cockroft) writes: >The NeXT manuals do not document how to get at screen bits. >I want to make a fancy info box for FrameMaker, and I want to write >directly into screen bits. Personally I refuse to buy one of these >boxes unless they change their minds about documenting this stuff. Personally, if the only way you can do what you want is by ignoring *all* of the graphics support provided by NeXT, I refuse to buy your product. So there. What exactly are you trying to do? If you've managed to identify something that's impossible or extremely difficult to accomplish with the current graphics libraries, I'm interested in knowing what it is, and I'm sure NeXT is, too. Of course, I want the frame buffer information, too, but I want to do things like port MGR and screen hacks. The screen hacks are for fun, and MGR is for an odd form of political commentary. "Look, Max! It's those pyramid- building aliens I've heard about in speculative films and books! They came to Earth to build these immense structures to keep their razor blades sharp and their hamburger fresh." -=- J Greely (jgreely@cis.ohio-state.edu; osu-cis!jgreely)