Re: Lo-Res Hijinks ... Enjoy!

["John B. Matthews" <nospam@nospam.com>]

In article <3pSne.23119$HI.3357@edtnps84>,
 "Craig Bower" <to.email.me@post.a.request.message> wrote:

> "John B. Matthews" <nospam@nospam.com> wrote in message 
> nospam-3303F8.23170602062005@news-rdr-01.ohiordc.rr.com">news:nospam-3303F8.23170602062005@news-rdr-01.ohiordc.rr.com...
> > In article <C9wne.31214$9A2.23366@edtnps89>,
> > "Craig Bower" <to.email.me@post.a.request.message> wrote:
> 
> > Are you using a lookup table for gbascalc? See, for example,
> > <http://www.wright.edu/~john.matthews/apple2.html#lr>.
> 
> Hi John,
> 
> I just had a quick run through the lookup table assembly on your site.
> 
> Nice work indeed! :)
> 
> It's a great idea if you wanted to skip the jump to GBASCALC
> for sure.  But the speed of GBASCALC works pretty good with
> Lo-Res and the only improvement I could see with using a lookup
> table for graphics is speed.  Especially if you were using GBASCALC,
> offseting it for drawing to the Hi-Res Screen. Where 8 times the data
> is needed to create a comparable picture.
> 
> Did I mention, Lo-Res Rocks?! :)
> 
> Later,
> Craig 

You're right, a lookup table is only marginally faster than GBASCALC, which is 
instructive in its own right. I just can't resist tinkering:-)

Hires is just a brand of root beer; lores* rules!

-- 
John
jmatthews at wright dot edu
www dot wright dot edu/~john.matthews/