Hi There! Once again, thanks for the patches and keep them flowing. The new CVS repository is up and updated with the patches: e.g. (with "-cur" terminated directories being the working directories) alias dcvs='cvs -z3 -djcid@auriga.wearlab.de:/sfhome/cvs/dillo' dcvs co dillo2 dcvs co dw2 cp -r dillo2 dillo2-cur cp -r dw2 dw2-cur ln -s dw2-cur dw-testbed find dw2-cur -name CVS -exec rm \{\} \; find dillo2-cur -name CVS -exec rm \{\} \; cd dw2-cur ./autogen.sh make cd ../dillo2-cur ./autogen.sh make Here follow my comments on the patches. Please test this CVS code and send feedback:

[Johannes wrote] * the namespace "signal" in dw-testbed/lout/signal.hh conflicts with the declaration in /usr/include/sys/signal.h: __sighandler_t *signal (int, __sighandler_t *); I renamed the namespace to loutsignal.

Johannes: please send me the patch for this.

[Vincent wrote (va_list issue)] Sure, though i'm not at all sure this is the correct way to fix this issue.

Vincent: AFAIS, the problem is looping without the va_copy, so the patch is OK. Anyway, please test the CVS code and tell us how it works.

[Andreas wrote] Ok, then I got it to compile finally for my ipaq with familar 0.8.4 on it. I runs with X-forwarding so that I get the window on my notebook display. But it segfaults without x forwarding:

Andreas: please let us know the procedure when you have cleaned it up.

[Alexander wrote (strndup)] Hm, right. I had used malloc() in my replacement function, but with calloc() it is indeed unnecessary.

I have wrapped this in autoconf, see attached patch. I also made autoconf in dillo and dw-testbed check for the path to the perl binary and substitute it in dpidc and Doxyfile, respectively, see other patch. Actually, these patches can't simply be applied: first, dillo-f15/dpid/dpidc and dw-testbed-0.0.43j/Doxyfile have to be moved to *.in.

Alexander: as strndup is a GNU extension, and we have kept the code as portable as possible, I just added the wrapper for it based on the patch. With regard to Perl, I'd like to get rid of that dependence either with bash (if possible) or C. BTW, if Sebastian agrees it may also be a good idea to use Dlib in dw2. That way those problems could be layered down...

[Johannes wrote] here is a new version of dillo-fltk scroll performance improvements. This patch is against vanilla dillo-fltk.

New in this patch:

* Hotkey bindings for arrow keys, Home- and EndKey. This only works when the focus is on the display area.

* Only unclipped area is exposed which improves performance on large pages (e.g. http://www.w3.org/TR/xslt).

* Limit scrolling to reasonable values.

It improves not only performance on large pages but also avoids overlapped rendering. Applied.

[Matthias wrote] Fine! Only using the arrow keys is quite slow and consumes all CPU time on my machine. In contrast, srolling with the old Dillo was quick and produced almost no CPU load.

A question: Would it be difficult to add mouse wheel support as well? On my machine that does not work. (Or is thia a configuration issue regarding FLTK?)

Dillo1 didn't render antialiased text, and was heavily optimized. The optimization phase of rendering in dillo2 has just started (thanks Johannes :). I hope we can tune it to a dillo1 similar CPU-consumtion.

[Matthias wrote] Compilation on Debian Etch worked well. I had to use the "--x-includes" and "--x-libraries" options when configuring FLTK, and the test glpuzzle did not compile.

I'm also using Etch here and didn't need those options. I also have a running glpuzzle. The CPU, hogs when scrolling on vanilla but not with the scrolling patch, and entities work. I also don't experience CPU-hogs from the over-link-quick-switch-from arrow-to-hand test. Maybe this is related to something not installed or not configured in your machine... (This system has: x11proto-gl-dev, freeglut3, freeglut3-dev, libxft2, libxft2-dev, libgl1-mesa-{dev,dri,glx} among others that I don't know whether relevant or not! ;). BTW, I'm testing on a fast machine. It will be interesting to see what the old one produces.

[Johannes wrote] Mouse wheel is a matter of binding. Place your mouse pointer over the scroll bar and use the mouse wheel (it needs to be bound to the viewport).

It is slow, because the default linesize (the amount a scrollbar scrolls when pushing on the arrow is 1. I could change that, but what would be a reasonable value?

The height of a word in normal text (i.e. line height). We know the font and font factor from dillorc2 (or defaults). This number is a good candidate. ---------------- Side Note to all: Have you right-clicked over the search button? :-) -- Cheers Jorge.-