Abdelrazak Younes wrote:
Juergen Spitzmueller wrote:
In this first status update, I don't want to come up with an extensive
bug
list, but rather outline some main goals I have in mind for the next
release, and list some of the really important bugs (please fill in).
As far as 1.5.2 is concerned, we seemed to have made a huge progress in
terms of stability. We fixed many crashes, and we didn't get many new
crash
reports yet, so 1.5.2 appears to be rather stable.
However, we also introduced some regressions, and ironing these out is
one
of the main tasks. In this context, I'd like to encourage everybody to
use
and stress-test the stable branch in real work. I think we could have
detected some regressions (such as those introduced by the pixmap
cache and
the AMS classes rewrite) before the release this way. I will probably
freeze the stable branch for bigger patches earlier this time for exactly
the same reason.
So here are some major goals:
* Pixmap cache: there are still some remaining issues. First and
foremost,
some users are not pleased by the on-screen quality of the pixmap cache
(subpixel hinting etc.), some even attributed this a showstopper. We have
to find a solution for 1.5.3. The best would be to improve the cache.
It's possible but not without major surgery of the way we do background
painting. I'll try to do some experiment.
One simple solution would be to add a backgoundColor() member to Font
and to update that when we pass PainterInfo at draw(). Is that
acceptable? I personnally think it is and this new information could be
useful for other needs anyway.
Objection if I do that in trunk?
Abdel.
