nanogui@linuxhacker.org

> : void GdFontSetPath(char* path)
> : FONTID GdFontLoad(char* filename)
> : void GdFontUnload(FONTID font)
> : void GdFontSetAntialiasing(FONTID font, BOOL aa)
> : void GdFontSetKerning(FONTID font, BOOL kern)
> : void GdFontSetSize(FONTID font, int ptsize)
> : void GdFontSetAngle(FONTID font, int degrees)
> : void GdFontSetPalette(FONTID font, PIXELVAL[] palette) /* For
> : antialiasing */
> : 

My concern here is how "micro" are we when we support this type of
stuff?  Also what sort of CPU usage are we talking about when all the
fonts now have to be processed before outputing on the screen?  (I
hate to be the dissenter :-()  Basically, I think this would be pretty
cool..., it would make life a lot easier in terms of how fonts are
supported in fltk and other tool kits..., BUT,

We have to keep in mind the target machine.  I think all these
features could be implemented quite well... like cached computations
on fonts.  I don't know, I'd have to see how it was being done.  Is
the calculation done for the font when you call a GdFontSetSize, etc.?
Is it cached/can that font be cached? (If it's being calculated once)
Clearly we can't recalculate fonts when we draw, that would result in
fairly poor performance in general.

Thanks,
Shane.