msevior@physics.unimelb.edu.au wrote:
>>Fixed using getFont() instead of search font (suggested by Dom). Hope
>>that's ok.
>>Credits go to all the people who commented in bugzilla.
>>
>>Completely unrelated to that i'm wondering about your opinion to move
>>that UnixFont stuff to Pango entirely in a future version of AbiWord.
>
>
> Hi Rob,
> We'll need to test the speed of pango-based rendering vs xft. I've
> nnoticed a significant lag when openning the drop down list and an
> increase in start up time since your commit to use pango-based
> combo-box. I have all the MS Word fonts installed on my PC so my
> case really amplifies the problem.
>
> That said there are really significant benefits to a pango-based graphics
> class. Tomas has done quite a lot of work on it already and I'm sure he'd
> *LOVE* some help.
>
The Pango based graphics class must use PangoFont, and that will make
the whole xft font system in AW completely obsolete; this is not
optional, but a consequence of the Pango API. This is not a bad thing
per se, but it means that all the GR_Graphics functions that use fonts
have to implemented from scratch, none of it can be inherited from
gr_UnixGraphics class. Some of it is already in place, some of it is not.
Tomas
Received on Sat May 14 20:38:17 2005
This archive was generated by hypermail 2.1.8 : Sat May 14 2005 - 20:38:18 CEST