aa font speed

[Alexander R. Pruss]

I'm now working on an antialiased font hack for OS 5 units.  Currently 
it works in conjunction with Fonts4OS5 and a modified version of 
Plucker's grayscale font format.  The code is proprietary (though based 
on Plucker's grayscale font code, minus the portions of it not written 
by me) and the hack will probably be shareware (or rolled into Fonts4OS5).

Anyway, the hack's current rendering speed appears to be about twice as 
good as Plucker's, in part because the hack is ARM code and in part 
because the hack writes directly to the screen bitmap (which is 
non-portable;  of course, I have a compile-time option to turn this 
off).  The speed of aa font rendering is a problem for users of 
low-speed OS 5 devices like the Clie TH or UX.  Moreover, the hack uses 
a modified version of the font format which uses fonts that are about 
25% smaller.  I would be happy to roll all of this back into Plucker, I 
guess, but it would be a fair bit of work (ARM-68K communication is a 
nuisance).  How important is the aa rendering speed?

Alex
--
Dr. Alexander R. Pruss
Department of Philosophy
Georgetown University
Washington, DC 20057-1133  U.S.A.
e-mail: [EMAIL PROTECTED]
online papers and home page: www.georgetown.edu/faculty/ap85
--------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
        - Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev