Remove colour attributes from body and strip most of the font tags out

34-04.html

@@ -24,7 +24,7 @@
 <!--CHAPTER=34//-->
 <!--PAGES=648-650//-->
 <!--UNASSIGNED1//-->
-<!--UNASSIGNED2//--></HEAD><BODY LINK=#0000FF ALINK=#000099 VLINK=#0000FF BGCOLOR=#FFFFFF>
+<!--UNASSIGNED2//--></HEAD><body>
 
 <CENTER>
 <TABLE BORDER>
@@ -47,7 +47,7 @@
 <P>If, however, <B>NOT_8088</B> is 1, indicating that the processor is a 286 or better (perhaps <B>AT_LEAST_286</B> would have been a better name), then after the initial DAC Write Index value is set, all 768 DAC locations are loaded with a single <B>REP OUTSB</B>. This is clearly the fastest approach, but it runs the risk, albeit remote, that the loading sequence will be interrupted and the DAC registers will become garbled.</P>
 <P>My own experience with Listing 34.1 indicates that it is sometimes possible to load all 256 locations cleanly but sometimes it is not; it all depends on the processor, the bus speed, the VGA, and the DAC, as well as whether autoincrementation and <B>REP OUTSB</B> are used. I&rsquo;m not going to bother to report how many DAC locations I <I>could</I> successfully load with each of the various approaches, for the simple reason that I don&rsquo;t have enough data points to make reliable suggestions, and I don&rsquo;t want you acting on my comments and running into trouble down the pike. You now have a versatile tool with which to probe the limitations of various DAC-loading approaches; use it to perform your own tests on a sampling of the slowest hardware configurations you expect your programs to run on, then leave a generous safety margin.</P>
 <P>One thing&rsquo;s for sure, though&mdash;you&rsquo;re not going to be able to cycle all 256 DAC locations cleanly once per frame on a reliable basis across the current generation of PCs. That&rsquo;s why I said at the outset that brute force isn&rsquo;t appropriate to the task of color cycling. That doesn&rsquo;t mean that color cycling can&rsquo;t be used, just that subtler approaches must be employed. Let&rsquo;s look at some of those alternatives.</P>
-<H3><A NAME="Heading8"></A><FONT COLOR="#000077">Color Cycling Approaches that Work</FONT></H3>
+<H3><A NAME="Heading8"></A>Color Cycling Approaches that Work</H3>
 <P>First of all, I&rsquo;d like to point out that when color cycling does work, it&rsquo;s a thing of beauty. Assemble Listing 34.1 so that it doesn&rsquo;t use the BIOS to load the DAC, doesn&rsquo;t guard against interrupts, and uses 286-specific instructions if your computer supports them. Then tinker with <B>CYCLE_SIZE</B> until the color cycling is perfectly clean on your computer. Color cycling looks stunningly smooth, doesn&rsquo;t it? And this is crude color cycling, working with the default color set; switch over to a color set that gradually works its way through various hues and saturations, and you could get something that looks for all the world like true-color animation (albeit working with a small subset of the full spectrum at any one time).</P>
 <P>Given that, how can we take advantage of color cycling within the limitations of loading the DAC? The simplest approach, and my personal favorite, is that of cycling a portion of the DAC while using the rest of the DAC locations for other, non-cycling purposes. For example, you might allocate 32 DAC locations to the aforementioned sunset, reserve 160 additional locations for use in drawing a static mountain scene, and employ the remaining 64 locations to draw images of planes, cars, and the like in the foreground. The 32 sunset colors could be cycled cleanly, and the other 224 colors would remain the same throughout the program, or would change only occasionally.</P>
 <P>That suggests a second possibility: If you have several different color sets to be cycled, interleave the loading so that only one color set is cycled per frame. Suppose you are animating a night scene, with stars twinkling in the background, meteors streaking across the sky, and a spaceship moving across the screen with its jets flaring. One way to produce most of the necessary effects with little effort would be to draw the stars in several attributes and then cycle the colors for <I>those</I> attributes, draw the meteor paths in successive attributes, one for each pixel, and then cycle the colors for those attributes, and do much the same for the jets. The only remaining task would be to animate the spaceship across the screen, which is not a particularly difficult task.</P>
@@ -66,7 +66,7 @@
 
 <hr width="90%" size="1" noshade>
 <div align="center">
-<font face="Verdana,sans-serif" size="1">Graphics Programming Black Book &copy; 2001 Michael Abrash</font>
+Graphics Programming Black Book &copy; 2001 Michael Abrash
 </div>
 <!-- all of the reference materials (books) have the footer and subfoot reveresed -->
 <!-- reference_subfoot = footer -->