On Thu, 2002-07-18 at 16:05, Oleg Tkachenko wrote:
> Keiron Liddle wrote:
> > - handle font lists, resolving on a char basis
> Do we really need it? It'll slow down rendering. btw, neither xep nor antenna 
> don't support it.

Normally it does a lookup on every char anyway.
I would have to check but most of the time it should be the same lookup
as it does now. It is only of a list is specified and it doesn't find
the char the first go.

> > - reduce number of FontState objects if information is the same (or
> > similar?)
> That's good idea, now we create new FontState for each text node. What about 
> FontState pool?
> > - allow for serialization as part of area tree
> > 
> > Do we need the FontInfo and FontMetric inside the FontState?
> Not sure about FontMetric but FontInfo object is actually 1 for the whole 
> rendering process and each FontState doesn't have to remember it.

The font metric has a number of sets that remain constant for the

> -- 
> Oleg Tkachenko
> Multiconn International, Israel

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to