Xref: utzoo comp.sys.amiga:74988 comp.sys.amiga.tech:17181 Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!wuarchive!bcm!shell!nuchat!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga,comp.sys.amiga.tech Subject: Re: Retargetable graphics. Temporary Stop-gaps. Message-ID: <7345@sugar.hackercorp.com> Date: 21 Dec 90 11:26:57 GMT References: <7307@sugar.hackercorp.com> <1990Dec19.175634.19203@mintaka.lcs.mit.edu> <1990Dec20.054258.1952@mintaka.lcs.mit.edu> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 35 In article <1990Dec20.054258.1952@mintaka.lcs.mit.edu> rjc@wookumz.ai.mit.edu (Ray Cromwell) writes: > Let Commodore do this. What I am suggesting is a method of allowing > software to render to a 'custom' screen display. Most video software > does not use Intuition windows, instead they use custom screens. True. But if the retargetable graphics library interface isn't close to the standard graphics.library/intuition.library interface (and those custom screens do use intuition.library, they just aren't *workbench* screens), then (a) you might prevent Commodore from getting a viable intuition interface for these devices, if your standard takes on a life of its own, and (b) it'll be harder to switch to the regular graphics libraries when C= gets their device independent graphics.library working. > >could open a new screen on the frame buffer. The new screen could then > >take over the monitor completely (like the A2024) or show up on a > >separate monitor. Somehow it would be possible to drag the mouse over > >to the other monitor and make its screen the active one. And nothing > >would stop us from having any number of monitors, (as many as we can > >fit graphics cards into the machine). > This is almost the same as tossing out intuition. No it *isn't*. Remember the Hedley monitor... you can't drag *that* screen down, but you can run a workbench on it just fine. Programs that are too bitplane-dependent won't work on a pixel-mapped screen, but that's their problem. That's what you get when you write hardware specific software. It's not as portable. Plenty of programs should still run. (why did you take comp.sys.amiga.tech out of the newsgroups line? This is certainly an appropriate topic for tech, or for programmer once the great renaming takes place) -- Peter da Silva. `-_-' .