> > Looks good. Where are the functions to select and load/free fonts ?
> It looks like you have to use the freetype library.

Ah - I see. But that somewhat defeats glyph caching - right ?

I have done a similar thing once, for a commercial contract, and glyph 
caching really improved things ...

> > I'd like, if loading fonts could be done alternatively by font name or
> > by
> > an alias that is looked up through an alias database, maybe allowing to
> > give alternatives at open, like on web 
> > <FONT FACE="Helvetica, Arial, Verdana") - guess you get the point.
> > We might as well want to define a bunch of standard aliases that are
> > used
> > like kind of "user preferences".
> Then it might be useful to define a 'ggi_font' abstraction.

Yes - I had thought of something that decouples GGI from a specific font 
rendering engine. We might want to add other renderers (e.g. pixel fonts,
Type1, etc.) later.

> Just a comment on the api: since all functions require a font argument,
> wouldn't it be more convenient to keep a font context for each visual,
> accessed via Set/GetFont calls?

Then you would have to make it a LibGGI extension. A good thing to do anyway 
IMHO. I will gladly give guidance on that point.

Having it as an extension might as well enable us to make use of native
font rendering abilities of the target, like in X ...

And as usually switching the font is relatively rare, yes, I'd think it 
would be a good idea to have some notion of the "current font".

CU, ANdy

-- 
Andreas Beck              |  Email :  <[EMAIL PROTECTED]>

Reply via email to