Hi, On Mon, Oct 22, 2007 at 06:39:09PM +0000, place wrote:
Turning off double buffering means that the default code from the tree is unusably slow and annoying on my ancient(*) computer. This might dissuade someone who comes along at the wrong time intending to give the fltk dillo a look.
Though admittedly it might be my configuration...
When testing in a Pentium I, 233Mhz, 96MB ram, the results were mixed, varied and confusing to me! For instance with dillo2-noDB, I get faster scrolling in a down-arrow-always-pressed-test, varying from 25% to 95% more or less of CPU depending on what is to be rendered and the X server's internal memory usage. Mouse drag-scrolling sometimes is better, some others worst and others the same !? With dillo2-DB, sometimes I get faster mouse drag-scrolling, others the same. Down-arrow-always-pressed-test is consistently worst, but sometimes pages render much faster and others the same. Frankly, I don't understand what this means. Ah, I also noticed that in a fast machine dillo2-noDB is much better than dillo2-DB (but annoying at flickering). -- Cheers Jorge.-