Re: [ngl-devel] nglFontLayout perfs

[Sebastien Metrot]

Ha! Very good news! I hope to improve things in the long run but any 
help is welcome :).
Next big goals are:
- rewrite nuiEditText to use nglFontLayout derived classes. (and 
implement word wrap, justification... my be have better text handling 
functions too)
- try again to enable partial widget/screen redraw. I had a working 
implementation this summer but noticed that the nuiTopLevel widget had 
to be implemented first in order to get this to work.
- implement new widgets and containers! (knobs, sliders, multistate 
buttons, etc...).
- optims optims optims (even look at how we could gain some speed by 
using some new 1.3 -> 1.5 and other exts features).
- Add scripting support (that'd be so cool). Preliminary look at this 
have shown that LUA seems like the best bet but it might be possible to 
implement a language agnostic scripting support layer.
- Better SVG rengering, anyone cares enough to start this project? ;)
- Better XML parsing.
- ... :)

Sebastien


advertsux wrote:
> Great work Sebastien, today I firsttime saw a such high numbers - about 
> 60FPS :o) - I'm going to make my first NUI app today.
>
> Thanks
>
> Martin
>
>
>
> Vincent Caron wrote:
>
> > Sebastien Metrot wrote:
> >
> > > Going from nglFont1 to nglFont have been quite a perf hit for nui. 
> > > Maybe we are not using it correctly and you could advise us after a 
> > > quick look at the code?
> >
> >
> >
> >   nuiLabel code looks alright. Maybe it would be simpler if the layout 
> > was actually a non-dynamic member, but you could not change the font 
> > in a single lifecycle of the widget. Maybe we could add font switching 
> > in nglFontLayout (I remember I had one good reason not to do it, but 
> > forgot it :)).
> >
> >   Otherwise, there is something really odd in nglFontBase : the 
> > FreeType cache is set to 2KB! nglFontLayout::GetMetrics _will_ be slow 
> > as hell since it will rasterize glyphs everytime. I must have 
> > postponed this problem and set an horrible number to make sure it 
> > would not be forgotten. Rats, missed.
> >
> >   I really don't know what number will do. Will depends on the target. 
> > I'll put a good megabyte and wait for complaints about heavy memory 
> > usage by nglFontBase. It's only a limit, it will eat less if you 
> > require less (growing buffer).
> >
> >   Fix commited.