On Fri, Oct 12, 2007 at 10:28:38PM +0200, Johannes Hofmann wrote:
So could it be that it has to do with RENDER and that most of you have decent hadware acceleration for that?
Yes, I guess that's the reason. You can compile fltk with the --disable-xft flag. In this case you will get the artefacts you mentioned before, but the performance should be similar to dillo1.
I've compiled fltk with "--disable-xft". Now it doesn't use RENDER any more (checked with xtrace). But I don't notice any performance difference to dillo2 with xft. In particular, performance is far from being that of dillo1. So, xft / RENDER does not seem to be the reason. Maybe a detailed comparison of the xtrace logs of dillo1 and dillo2-noxft could help? I've seen that dillo2 uses many "ChangeGC", "SetClipRectangles" and "PolyFillRectangle" requests, which are not used by dillo1. I don't know which requests are particularly expensive.
We should try to get rid of those artefacts for users that can't use xft.
I agree. As Johannes has found out, this is an fltk bug. Cheers, -- Matthias Franz