Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!shelby!agate!ucbvax!UTCVM.BITNET!MQUINN From: MQUINN@UTCVM.BITNET Newsgroups: comp.sys.apple2 Subject: Re: updating windows fast Message-ID: <9102161440.AA13264@apple.com> Date: 16 Feb 91 14:36:00 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 26 On Sat, 16 Feb 91 05:17:29 GMT Doug Gwyn said: >In article <1991Feb15.212254.10659@ux1.cso.uiuc.edu> bazyar@cs.uiuc.edu (Jawaid > Bazyar) writes: >>Doing anything against the rules (i.e. not using QuickDraw for everything) >>will, guaranteed, make your program incompatible with this board. > >And having your application run too slow may make it unusable too. >The tradeoffs have to be carefully considered. While I'm a big fan >of portability, that is just one aspect of whether or not software >meets certain general goals. The other aspects are important too. Here's something I've thought of doing before: Have an option in the Application called FAST/RELIABLE or something to that affect. What it would do is switch between using fast, unreliable, technieques to using routines that follow the rules that would be more reliable. Then, people that have a graphics board could use the GS's native mode for speed or the graphics board for higher resolution & colors. And, of course, tell the user of the advantages and dissadvantages of both modes and when and when not to use them. Would that be practical or not? ---------------------------------------- Michael J. Quinn University of Tennessee at Chattanooga BITNET-- mquinn@utcvm pro-line-- mquinn@pro-gsplus.cts.com