May 2004 - Dillo-dev - lists.mailman3.com

[Dillo-dev]Tabs/Frames/Kbnav

by Jorge Arellano Cid

Hi, Now that dillo 0.8.1 is done, I want to clarify what happened with the Tabs/Frames/KeybNav patch. Sometime has passed since, but at the time we decided to not stir an already ungrateful situation. Here I'm forwarding a couple of emails that should be enough to do it (dillo-dev archives holds the rest). Sincerely Jorge.- -------------------------------------------------------------------------- From akemnade(a)informatik.uni-bremen.de Mon May 17 08:44:51 2004 Date: Sat, 27 Mar 2004 14:25:31 +0100 From: Andreas Kemnade <akemnade(a)informatik.uni-bremen.de> To: Sebastian Geerken <s.geerken(a)ping.de> Cc: jcid(a)dillo.org Subject: Re: [Dillo-dev]Frame support in CVS Hi Sebastian, Hi Jorge, On Sun, 7 Mar 2004 22:14:49 +0100 Sebastian Geerken <s.geerken(a)ping.de> wrote: > Hi Andreas. > > (I'm writing this in English to make forwarding etc. simpler.) > > Jorge and I would indeed like to incorporate Frank's work into the > main trunk, but unfortunately Frank refused to clean up the code, and > finally, he quit the project, and plans to make an own version of > dillo. I've a mail of 8 Jan, which I can forward you, if you are > interested. > Please send me that mail. Ok, perhaps I was not deep enough in the archives. I just did not find any statement about what has to be done with the patch. I think other readers of dillo-dev do not know about that, too. Perhaps it would be better if that was more clarified but I also understand that you do not want to repeat yourself too often. > If you want to commit some work, you may clean up the patch, > especially split it up into several parts. Most important, there are > three parts: DilloDoc (which I'd like to be renamed), frames, and > tabs. They are of course related, but it would be handy to have single > patches for them (because of the over-linear correlation of patch size > and review time). > Most the time I was just happy to be able to apply the frames patch. I was not forced to look at the code. But with the massive conflicts the patch produces when I applied it to 0.8 I really had to start to look at the patch. Sometimes being not a maintainer has really big advances... If I checked the patch size before fixing the conflicts I guess I would have given up. I have never noticed before how big the patch was. If splitting does not work, then there is something really wrong with the code. So let's divide and conquer. I think an important part is to remove nice (but not very important) features from the patch which can be added separetely later on. I think I can find time in the next month to split and clean up the frame patch. Greetings Andreas Kemnade -------------------------------------------------------------------------- From s.geerken(a)ping.de Mon May 17 08:44:37 2004 Date: Sat, 10 Jan 2004 13:04:11 +0100 From: Sebastian Geerken <s.geerken(a)ping.de> To: Jorge Arellano Cid <jcid(a)dillo.org> Subject: Fwd: Re: Notes on keyboard navigation FYI. [ Part 2: "Included Message" ] Date: Thu, 08 Jan 2004 22:31:10 +0100 From: Frank de Lange <frank(a)unternet.org> To: Sebastian Geerken <s.geerken(a)ping.de> Subject: Re: Notes on keyboard navigation Sebastian Geerken wrote: >Hi Frank. > >First of all, a happy new year! > >Several notes on keyboard navigation: > >1. Jorge and I decided, that we do not immediately support keyboard > configuration, also because it is rather unclear what widget > toolkit will be used in the future. So the version of keyboard > navigation, which will be integrated the first time, should have > hard-coded keys. > >2. Some days ago, I committed some changes to iterators, you may be > interested in. There is some description within doc/Dw.txt, section > "Anchors and Scrolling", subsection "Scrolling". Especially, > scrolling has now two dimensions, there is a new scrolling > position, DW_[HV]POS_INTO_VIEW, and DwIterator::scroll_to has been > replaced by the more general DwIterator::get_allocation. > >3. I noticed some performance problems with stress tests, I'm not sure > they play a role in real life. Anyway, you wrote on the list that > you are already working on in. > >Sebastian > > Happy new year as well... and thanks for the notice. For keyboard navigation to work in a sensible way x coördinate support is useful... so useful that I had already implemented it. The performance problems have been solved in my tree as well, as I have stated in my last message to the list. They are caused by the use of g_list_search_custom to find the focusable in focus.c. Using a hash table solved this. But... I have decided to discontinue support to the Dillo project as of the 'infringer' message to the list, so I will no longer post or update patches to Dillo. Instead, I am working on a new browser which should fill the same niche as Dillo (small, fast, enough features for most sites so it can be used as main browser). Starting point for this is my patched version of Dillo, with additional changes: - dpi and dpid and related things are gone (DONE) - library plugins for everything dpi did, and more (mime decoders, schemes, etc) (DONE) - ccc is on the way out, to be replaced by something less convoluted and more general (WORK IN PROGRESS) - DOM support with new xml parser (WORK IN PROGRESS) The project currently uses GTK+ as toolkit, but might switch to something else (FLTK is a candidate). A side goal for this project is to be developer-friendly. Patches are welcome, they will get their own space on the site (which will be on savannah, which is still not completely recovered from the break-in yet... hence the delay). I may post a short notice to the list if/when the project is up and ready for testing. Good luck with Dillo. Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]

May 20, 2004

[Dillo-dev]Re: White spaces handling (was: Weird glitch with rendering)

by Jorge Arellano Cid

Hi Sebastian, One thing that puzzles me about the patch that collapses whitespace at the parser level, is that some tables no longer are centered! For instance: http://www.dillo.org/stats/ http://www.dillo.org/stats/usage_200405.html Cheers Jorge.-

May 19, 2004

[Dillo-dev]0.8.1 text centering error?

by Gregg

Hello, I have compiled and run Dillo 0.8.1 flawlessly on Debian woody. However, I notice the browser "centering text" that wasn't on 0.8.0 and earlier. Example: http://www.cknw.com - my daily news, now shows the headlines as centred. Is this supposed to be? Thanks, -- Gregg

May 18, 2004

[Dillo-dev]Re: White spaces handling (was: Weird glitch with rendering)

by Jorge Arellano Cid

Hi Sebastian, This HTML example shows the black row (after patch): <table border="1" cellspacing="1"> <tr> <td bgcolor=black> <table width=100% bgcolor=white> <tr> <td>1</td> <td>2</td> <td>3</td> </tr> </table> </td> </tr> </table> HTH Jorge.-

May 17, 2004

[Dillo-dev]Re: White spaces handling (was: Weird glitch with rendering)

by Jorge Arellano Cid

Sebastian, > [Jorge wrote:] > > (...) > At this point I see that applying patch 1, plus making the > parser ignore whitespaces after a start tag and before an end tag > is a correct solution that can endure a reality test. Now I have a patch that does this (your patch 1.-, plus whitespace ignoring at the parser level). It works very well so far and passes these test pages: 1.- underline-strike-and-spaces.html 2.- bms.html 3.- Underlining of "PRE" in HTML 4.01 SPEC section 9.1 (the page itself, as HTML, has a good test case) Please download it and send me your comments: http://www.dillo.org/download/Jdiff.SPC2 Note: if you modify the patch like this, html.c:1007: - if (html->PrevWasOpenTag) { + if (0 && html->PrevWasOpenTag) { then, the splash page's tables render with a black row at the bottom. It'd be interesting to find out why. Cheers Jorge.-

May 17, 2004

[Dillo-dev]dillo-0.8.1 was officialy released.

by Jorge Arellano Cid

Hi folks, The new dillo-0.8.1 is just released now, waiting to appear on the freshmeat front page. It's been a long road 'til here, so please let me thank all of you that have participated in dillo-dev. Now, let's party! ;-) Jorge.-

May 15, 2004

Re: [Dillo-dev]dillo-0.8.1.tar.bz2 final

by Riccardo Mottola

Jorge Arellano Cid wrote: > > Hi there, > > Has anyone tested on *BSD yet? > and Solaris? It builds on OpenBSD 3.5 (sparc). I did onlz a quick testing by browsing some sites and it seems to work. Except download troubles with dpi stuff, whcih sometimes are not started the first time and I might end with a dpi.core in my home. I'll test it on solaris this weekend hopefully. -Riccardo

May 15, 2004

Re: [Dillo-dev]dillo-0.8.1.tar.bz2 final

by Kelson Vibber

On Friday 14 May 2004 9:18 am, Jorge Arellano Cid wrote: > Has anyone tested on *BSD yet? It builds and runs on FreeBSD 4.8 for i386. (pthreads are detected.) -- Kelson Vibber www.hyperborea.org

May 15, 2004

Re: [Dillo-dev]dillo-0.8.1.tar.bz2 final

by Jorge Arellano Cid

On Fri, 14 May 2004, Kelson Vibber wrote: > On Friday 14 May 2004 06:00 am, Jorge Arellano Cid wrote: > > On Fri, 14 May 2004, Maarten Sander wrote: > > > I've just compiled and used Dillo on my Fedore Core 1 (Athlon-)machine. > > > It's updated with all the latest and greatest (*cough*) packages from > > > Dag, ATrpms, etc. GCC is 3.3.2, glibc 2.3.2, GTK 1.2.10. During > > > ./configure it gave a big warning that it could not find libpng-config, > > > but it detected png.h after that and compiled without problems. > > > > libpng is not easy to detect, maybe the Fedora team decided to > > go back to the simple header/library pair to avoid problems. > > Don't worry. > > I think I can shed some light on this: For some reason, Red Hat has never > included libpng-config in their libpng packages. I assume it's related to > their practice of maintaining binary compatibility when possible by using > backported patches instead of moving to newer upstream versions. > > The stock libpng even in FC2 Test3 is still 1.2.2, and I suspect (though I > don't remember for certain) that libpng-config was added later in the 1.2 > series. > > This practice does make it easier to deal with third-party software. Last > night, just to try it, I built Dillo on Fedora Core 2. I was able to run it > on Red Hat 8 - three versions behind! By contrast, if you build Dillo on > Mandrake 8.2, it will not run on Mandrake 8.1! As a result, I only have to > post 3 RPMs to cover 4 years of Red Hat/Fedora releases. Thanks for the explanation. BTW, what's configure's warning message? > > > You have a quite current GNU/Linux. Can you tell whether Dillo > > was linked against NPTL? > > I'm curious - what should show up in the output from ldd? The binary I built > on a very similar system to the one Maarten described (Athlon, FC1, with > third-party packages from Dag, FreshRPMs, ATrpms and so on) is linked > like this: > libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00324000) > libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x00ee9000) > libpng12.so.0 => /usr/lib/libpng12.so.0 (0x00f24000) > libm.so.6 => /lib/tls/libm.so.6 (0x0020a000) > libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x00a22000) > libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x00b84000) > libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x00111000) > libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x00cac000) > libdl.so.2 => /lib/libdl.so.2 (0x004fe000) > libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x001ac000) > libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x00114000) > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x0022c000) > libz.so.1 => /usr/lib/libz.so.1 (0x007e6000) > libc.so.6 => /lib/tls/libc.so.6 (0x00334000) > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00753000) I'm not an expert on RedHat/Fedora, but if you look at the libpthread line in the listing above, it appears under tls/, and TLS (GNU's SSL) is required for NPTL. That is a sign towards thinking it may be linked with NPTL, but NPTL also requires an NPTL enabled kernel (this you have to look for in the distro's spec), and finally there was an environment variable planned for RedHat 9, that could be set to keep using the old libpthread. I don't know if it survived but should be investigated too. Cheers Jorge.-

May 14, 2004

Re: [Dillo-dev]dillo-0.8.1.tar.bz2 final

by Kelson Vibber

On Friday 14 May 2004 06:00 am, Jorge Arellano Cid wrote: > On Fri, 14 May 2004, Maarten Sander wrote: > > I've just compiled and used Dillo on my Fedore Core 1 (Athlon-)machine. > > It's updated with all the latest and greatest (*cough*) packages from > > Dag, ATrpms, etc. GCC is 3.3.2, glibc 2.3.2, GTK 1.2.10. During > > ./configure it gave a big warning that it could not find libpng-config, > > but it detected png.h after that and compiled without problems. > > libpng is not easy to detect, maybe the Fedora team decided to > go back to the simple header/library pair to avoid problems. > Don't worry. I think I can shed some light on this: For some reason, Red Hat has never included libpng-config in their libpng packages. I assume it's related to their practice of maintaining binary compatibility when possible by using backported patches instead of moving to newer upstream versions. The stock libpng even in FC2 Test3 is still 1.2.2, and I suspect (though I don't remember for certain) that libpng-config was added later in the 1.2 series. This practice does make it easier to deal with third-party software. Last night, just to try it, I built Dillo on Fedora Core 2. I was able to run it on Red Hat 8 - three versions behind! By contrast, if you build Dillo on Mandrake 8.2, it will not run on Mandrake 8.1! As a result, I only have to post 3 RPMs to cover 4 years of Red Hat/Fedora releases. > You have a quite current GNU/Linux. Can you tell whether Dillo > was linked against NPTL? I'm curious - what should show up in the output from ldd? The binary I built on a very similar system to the one Maarten described (Athlon, FC1, with third-party packages from Dag, FreshRPMs, ATrpms and so on) is linked like this: libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00324000) libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x00ee9000) libpng12.so.0 => /usr/lib/libpng12.so.0 (0x00f24000) libm.so.6 => /lib/tls/libm.so.6 (0x0020a000) libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x00a22000) libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x00b84000) libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0 (0x00111000) libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x00cac000) libdl.so.2 => /lib/libdl.so.2 (0x004fe000) libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x001ac000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x00114000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x0022c000) libz.so.1 => /usr/lib/libz.so.1 (0x007e6000) libc.so.6 => /lib/tls/libc.so.6 (0x00334000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00753000) -- Kelson Vibber www.hyperborea.org

May 14, 2004