- Dillo-dev - lists.mailman3.com

patch: a quick and ugly source searcher

by corvid＠lavabit.com

- TextBuffer also has search_backward and a matchCase argument. - show_insert_position() often doesn't want to scroll quite far enough to bring the text into view.

Oct. 21, 2008

LWN.net comment about Dillo2

by bradreed1＠gmail.com

I just wanted to thank jh33 (Johannes I presume?) for his help straightening out my messed up build of fltk2 so I could get dillo2 running properly. I rebuilt fltk2 without the --enable-cairo option, and rebuilt dillo. It is working fine, and I reposted at lwn.net to say that. Thank you for another great release of dillo. Brad

Oct. 20, 2008

display issues with dillo2

by corvid＠lavabit.com

Johannes wrote: > Yes, we should mention that somewhere. > FAQ or README? dillo's configure.in could grep for cairo in LIBFLTK_LIBS, right? In the meantime, I just stuck warnings on download.html and cvs.html. Guess I'll add something to the FAQ as well...

Oct. 20, 2008

display issues with dillo2

by Johannes.Hofmann＠gmx.de

On Mon, Oct 20, 2008 at 05:19:03PM +0200, Thomas Orgis wrote: > Am Mon, 20 Oct 2008 16:59:34 +0200 > schrieb Johannes Hofmann <Johannes.Hofmann(a)gmx.de>: > > > With these options I can reproduce the problem. I guess > > --enable-cairo is the problematic one. > > Can you try to compile dillo with a manually compiled fltk2 without > > --enable-cairo? > > Nothing easier than that with the source-based distro;-) Yes, that's nice. I use pkgsrc;-) > I have a system fltk2 lib now without cairo and now dillo2 works nicely! > So cairo in FLTK2 is buggy? > Or its usage in dillo... but I suppose that FLTK2 should abstract that away. Not sure, but given the fact that cairo support is switched off by default, I guess it's just not stable enough yet. > > This could meant that we can close the bug; but the information about > the cairo issue should be FAQed somewhere -- ideally, of course, solved > upstream. Yes, we should mention that somewhere. FAQ or README? > > Btw: FLTK2 not having a stable release is a bit of a problem with replacing > the old "stable" dillo with dillo2... I hope that situation is resolved soon. > Well, and the missing feature of frames; whatever one's opinion, the > dillo patch that enabled this is commonplace and this missing is a de facto > regression... Nobody would be opposed to a clean patch that implements frames I think. Cheers, Johannes

Oct. 20, 2008

Heavy load on X

by Johannes.Hofmann＠gmx.de

On Tue, Oct 21, 2008 at 12:02:53AM +0900, ???? wrote: > 2008/10/20 Johannes Hofmann <Johannes.Hofmann(a)gmx.de>: > > Is there still a high CPU usage after the page has finished loading? > > Yes, as long as I see this page, CPU usage is high. I don't do > anything else but just see the page. > > > What font are you using? > > I used sazanami-gothic to see Japanese. I change font to times then > CPU usage became about 67%. Can you try to run dillo with xtrace as described in http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-September/004911.ht… (at the end). xtrace will output a lot. What I'm interested in is the output after the page has loaded. Cheers, Johannes PS: Anyone else on the list using FreeBSD?

Oct. 20, 2008

Heavy load on X

by onepoint＠starurchin.org

On Mon, Oct 20, 2008 at 02:26:31PM +0000, corvid wrote: > furaisanjin wrote: > > I'm running dillo2 on FreeBSD 6.3. When I visit this page > > http://www.itmedia.co.jp/bizid/, somehow Xorg occupies lot of > > processing power and value of CPU in top command shows more than 85%. > > Does anybody have an idea? What would be the reason? > > I don't know; it seems fine for me in Linux... Same here, running Linux, whole page loads with very little CPU usage. Jeremy Henty

Oct. 20, 2008

display issues with dillo2

by thomas-forum＠orgis.org

Am Mon, 20 Oct 2008 16:59:34 +0200 schrieb Johannes Hofmann <Johannes.Hofmann(a)gmx.de>: > With these options I can reproduce the problem. I guess > --enable-cairo is the problematic one. > Can you try to compile dillo with a manually compiled fltk2 without > --enable-cairo? Nothing easier than that with the source-based distro;-) I have a system fltk2 lib now without cairo and now dillo2 works nicely! So cairo in FLTK2 is buggy? Or its usage in dillo... but I suppose that FLTK2 should abstract that away. This could meant that we can close the bug; but the information about the cairo issue should be FAQed somewhere -- ideally, of course, solved upstream. Btw: FLTK2 not having a stable release is a bit of a problem with replacing the old "stable" dillo with dillo2... I hope that situation is resolved soon. Well, and the missing feature of frames; whatever one's opinion, the dillo patch that enabled this is commonplace and this missing is a de facto regression... But I'm really delighted to see that dillo is still alive, really. I dream of a lean, stable browser that can do https and CSS. Perhaps that dream comes true, finally. Alrighty then, Thomas.

Oct. 20, 2008

display issues with dillo2

by Johannes.Hofmann＠gmx.de

On Mon, Oct 20, 2008 at 04:54:38PM +0200, Thomas Orgis wrote: > Am Mon, 20 Oct 2008 16:23:07 +0200 > schrieb Johannes Hofmann <Johannes.Hofmann(a)gmx.de>: > > > You've built FLTK2 manually then, right? > > Yes and no. The version dillo is using is built by the distribution > scripts. This being a source-based distro sort of means that still, > I have it built locally... > But for the FLTK2 tests, I indeed built it manually and ran them > in the build directory -- but that has not been installed. > > > Which snapshot are you using? > > The newest I know, fltk-2.0.x-r6403 (I included this info in my bug > submission, but had to delete stuff because of text size limit...). > > > Any special configure options for FLTK2? > > Well, the distro build is tunable and included these: > > --enable-shared --enable-threads --enable-xdbe --enable-xinerama > --enable-xft --enable-cairo --enable-png --enable-zlib --enable-gl With these options I can reproduce the problem. I guess --enable-cairo is the problematic one. Can you try to compile dillo with a manually compiled fltk2 without --enable-cairo? Thanks for testing, Johannes

Oct. 20, 2008

display issues with dillo2

by thomas-forum＠orgis.org

Am Mon, 20 Oct 2008 16:23:07 +0200 schrieb Johannes Hofmann <Johannes.Hofmann(a)gmx.de>: > You've built FLTK2 manually then, right? Yes and no. The version dillo is using is built by the distribution scripts. This being a source-based distro sort of means that still, I have it built locally... But for the FLTK2 tests, I indeed built it manually and ran them in the build directory -- but that has not been installed. > Which snapshot are you using? The newest I know, fltk-2.0.x-r6403 (I included this info in my bug submission, but had to delete stuff because of text size limit...). > Any special configure options for FLTK2? Well, the distro build is tunable and included these: --enable-shared --enable-threads --enable-xdbe --enable-xinerama --enable-xft --enable-cairo --enable-png --enable-zlib --enable-gl > Is it possible that there is another FLTK2 installation on your > system (e.g. one in /usr/ and one in /usr/local)? No, in the system there is only the one installed by the distro scripts. > Does changing the buffered_drawing option in dillorc to 0 or 2 make > a difference? Hm... the FLTK2 test for the buffering worked fine (in case we are talking about the same)... testing this now with dillo. It makes a difference, at least. No setting fixes the whole experience, but with 2, the refresh on uncovering the window works and the main body seems to be stable. What remains is the clutter from text lines over the menu bar and status bar. When scrolling down, text fragments appear and stay at the top, when scrolling up, text fragments appear and stay at the bottom. Alrighty then, Thomas.

Oct. 20, 2008

display issues with dillo2

by Johannes.Hofmann＠gmx.de

On Mon, Oct 20, 2008 at 01:28:32PM +0200, Thomas Orgis wrote: > Am Mon, 20 Oct 2008 12:20:29 +0100 > schrieb Jeremy Henty <onepoint(a)starurchin.org>: > > > I also run dillo2 on GNU/Linux and modular X.org and I see nothing > > like this. Do you see these problems all all the time? Can you tell > > us more about your setup (Linux distro, X.org version, window manager > > etc.)? Without more information it's going to be hard to help. > > Well, this is happening with plain > > startx /usr/bin/dillo -- :1 > > So, perhaps we can rule out the window manager;-) -- it would be fluxbox, btw. > > xorg stuff is _very_ recent, as this is SourceMage GNU/Linux with test grimoire, rolling release. > xorg-server 1.5.2 and associated versions... > > And yes, it is happening all the time. > The test apps in FLTK2 build directory work fine, though. You've built FLTK2 manually then, right? Which snapshot are you using? Any special configure options for FLTK2? Is it possible that there is another FLTK2 installation on your system (e.g. one in /usr/ and one in /usr/local)? Does changing the buffered_drawing option in dillorc to 0 or 2 make a difference? Cheers, Johannes

Oct. 20, 2008