On Tue, Apr 08, 2008 at 09:41:33PM +0000, corvid wrote:
Johannes wrote:
On Tue, Apr 08, 2008 at 08:35:44PM +0000, corvid wrote:
Johannes wrote:
On Tue, Apr 08, 2008 at 08:02:05PM +0000, corvid wrote:
Jeremy wrote:
There are no regressions that I can see. It feels just as fast and somewhat less flickery. Mind you, this is a fairly fast machine, it would be useful if someone with a more low-end box tried it out.
I wonder who you could be talking about :) I applied it, but running without double buffering is just not an option for me. Drawing is just very slow no matter what.
Is dillo-fltk useable for you with the patch, but with clear_double_buffer() as in current cvs? If not, what exactly is the problem?
Drawing a page of text takes a couple of seconds, as I've always seen with clear_double_buffer().
Well, I don't expect it to be faster with my patch, but there should be less flicker, so you should be able to start reading while the page is loading. The same effect would I expect from commenting out clear_double_buffer(). Or is the drawing itself faster if you comment out clear_double_buffer()?
With clear_double_buffer(), I hit page down on an already-loaded page. It takes four seconds to draw the screen of text (well, and then it performs a redraw for another three or four seconds).
Ouch, 4 seconds is really slow... And there should be now additional redraw in this case.
If I comment out clear_double_buffer(), it takes no perceived time.
This is interesting. I will try to reproduce this on my old laptop. Can you please run xdpyinfo on your machine and check whether or not you have RENDER and XDBE extensions enabled in your X-server?
The point of my patch is to make drawing flicker free as with clear_double_buffer() commented out, but without the memory overhead.
What machine do you have? Perhaps I should try to revive an old laptop of mine...
a thinkpad 380XD. It had its tenth birthday in February. I've been really meaning to get something newer for... a year now. (If you think that's bad, I used a Commodore until 1993 -- if you're old enough for that to mean much to you, anyway).
Old enough - yes, but I had an Atari 800XL back then :-)
Speaking of slow, I wonder whether this menu is usable for the rest of you. http://www.irs.gov/formspubs/lists/0,,id=97817,00.html
Hm, I see something... And I can click on the "Individual", "Businesses"... images.
Is it slow when you scroll around through the items in the menu of forms at the bottom?
It's certainly usable. However you might have noticed that drawing antialiased fonts consumes much more CPU than raster fonts. So you might try fltk2 configured with the --disable-xft option. I actually like good raster fonts better than antialiased ones, but that's a matter of taste.
It currently must take like a minute to go from one item to the next. Probably more. I'll try --disable-xft.
_______________________________________________ Dillo-dev mailing list Dillo-dev@dillo.org http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev