June 2009 - Dillo-dev - lists.mailman3.com

dillo-2.1.tar.bz2
by newman.x＠gmail.com June 23, 2009

June 23, 2009

On Tue, Jun 16, 2009 at 11:46 PM, Kelson Vibber<kelson(a)pobox.com> wrote: > Michal Nowak wrote: >> >> I'd like to create Fedora RPM's (since I am Fedora packager), the >> problem is that fltk2 is not in Fedora (Package Review's pending [1], >> help welcomed), so, only unofficial packages are doable now. >> >> Problem with Fedora 11 is that fltk2 can't be built with recent g++ [2]. I >> might check with with F-10, it used to work. > > I've just built FLTK2 r6786 and Dillo 2.1 on a Fedora 10 system, so it does > work there. In http://fltk.org/str.php?L2205 I was suggested to make a code change in FLTK2, I did so and it compiles fine now. I am not sure of the root cause because fltk guys suggested that the problem is glibc-2.10 and pointed to patch but the patch looks to be incorporated in F-11 glibc. > > If you want to take a look, my SRPMS are available at > http://www.hyperborea.org/software/dillo/rpms/ > > The spec for FLTK2 is *very* rough, and the spec for Dillo has a lot of > cruft from back when I was maintaining packages for a bunch of different > distros. While looking at [1] it looks like you are using static archives (.a), while I turned on shared libs [2] option in FLTK2 and provide them instead. I fixed the remaining issues from package review [3], I guess FLTK2 might be in Fedora in near future. But now: FLTK2 packages for Fedora 10, 11, 12 (Rawhide) for ix86 and x86-64 ---> http://mnowak.fedorapeople.org/fltk2/ Enjoy [1] http://www.hyperborea.org/software/dillo/rpms/fltk2-2.0.x.r6786-0.1.f10.x86… [2] http://mnowak.fedorapeople.org/fltk2/ [3] https://bugzilla.redhat.com/show_bug.cgi?id=fltk2 > > -- > Kelson Vibber > Hyperborea.org - SpeedForce.org > Michal

6 31

Re: Dillo 2.1 questions
by jcid＠dillo.org June 23, 2009

June 23, 2009

Hi, On Mon, Jun 22, 2009 at 02:33:51PM +0200, Donjan Rodic wrote: > Hello Jorge > > First off, Dillo 2.1 is awesome. It got exactly the features I hoped for Good! > and isn't noticably more resource hungry. In fact it has half the memory footprint of the dillo1 series. http://www.dillo.org/memory.html > Too bad it doesn't support column layouts in CSS yet... can we expect > this in the next release? I hope! The column layout problem is mainly a lack of implementation of floating elements in the textblock. it is one of the top priorities for the next release (if not the topmost). We'll work on it and try to fix it. We're yet to find out how much work it will be. > One thing I can't figure out are the available keybinding commands. For > example, how would I call "scroll-one-screen-up", which I'd like to bind > to <Shift>Space. Similar to how Space scrolls one screen down. > Also "open-link-in-new-tab" to <Ctrl>"left-mouse-click"... > I couldn't find any documentation on such commands, except for the keys > listed in .dillo/keysrc. You should have an installation-wide keysrc file along with dillorc. If not, just read http://www.dillo.org/keysrc. AFAIS, we haven't included that keybinding, but will probably exist in the source repository soon. Maybe: coarse-scroll-down, coarse-scroll-up, fine-scroll-down, fine-scroll-up > Another topic: is the adblock.txt in the .dillo folder supposed to work? > Is there any recent documentation on this? No, AFAIK it isn't in the release. I'd really like to have it in the next release though. -- Cheers Jorge.-

1 0

css font-size and nested tables
by Johannes.Hofmann＠gmx.de June 23, 2009

June 23, 2009

Hi, trying to find the reason for the tiny fonts in gmail, I found the following: <html> <head> <style type="text/css"> td {font-family: arial; font-size:50%} </style> </head> <body> <table> <tr> <td> foo bar </td> </tr> <tr> <td> <table> <tr> <td>foo bar</td> </tr> </table> </td> </tr> </table> </body> </html> is rendered with the same font size in both lines in firefox, konqueror, and opera. Can someone enlighten me why the nested <td> does not decrease the font size again in the second line? If I change the CSS to act on <table> instead of <td> it works as expected. Cheers, Johannes

3 4

form widgets, ascent/descent
by corvid＠lavabit.com June 22, 2009

June 22, 2009

I was playing around in dw, and noticed that, whereas form widgets normally like to put much of their height into descent, when style sets the height, Textblock::calcWidgetSize() puts it all into ascent. I checked firefox and saw that their form widgets ascend. If we made everything ascend and just put font->descent into the descent, it would make life simpler. Or, nearly. I guess there is RELIEF_Y_THICKNESS, but I could almost ignore that...

3 4

trimming system includes
by corvid＠lavabit.com June 22, 2009

June 22, 2009

Johannes wrote: > On Mon, Jun 22, 2009 at 02:08:01AM +0000, corvid wrote: > > Johannes wrote: > > > I'm all for it and will be happy to test it on DragonFly BSD. > > > > Does this come reasonably close to compiling? > > Works just fine here. Well, if it works for Johannes... :) Anyway, I looked through the cvs archive a little, and it was interesting to see the prehistoric origins of some of this stuff, dating as far back as gzilla presumably. One is unavoidably reminded of how a living thing today bears the mark of billions of years of evolutionary past.

2 1

trimming system includes
by corvid＠lavabit.com June 21, 2009

June 21, 2009

Would anyone have strong objections if I go through and make some patches to remove system includes where I can't see any evidence that any code now in that file still needs that header?

3 3

experimental patch: nowrap
by corvid＠lavabit.com June 20, 2009

June 20, 2009

Currently dillo does not handle the case where certain regions of a line can be wrapped and other regions cannot. A prominent example is the list of browsers at the bottom of http://en.wikipedia.org/wiki/Dillo Here is a patch that minimizes memory use (adds one int per textblock) at some cost of recalculating things http://www.dillo.org/test/nowrap.patch When whitespace isn't WHITE_SPACE_NORMAL, Textblock::add* functions still add words to the word list, but postpone wrapping until the entire nowrap/pre chunk has been added or a break has been seen. This is so that we know whether to put it all on a new line. Some possibilities: Putting some kind of spanWidth in each Word, calculating it in addNowrapWords and sticking this nonzero value into the beginning word. We'd have to remember to deal with it if things in the span changed size, or if dillo got on-the-fly display:none someday or whatever. Taking the time to stick the whole chunk into one word when the style is all the same. (Similar difficulties as the above.) I'm not sure whether that would make life more difficult if dillo got bidirectional text someday. Putting the nowrap Words into a Something, so that what is now a Word list would contain Word Word Word Something Word Something Word... That sounds complicated. Let the add* functions put the nowrap Words through wordWrap, and keep track of shifts between normal/nowrap in a line. When a line is completed, set up rewrap to do it over. This would be in an effort to "push down the bubble" of ickiness around add*/addNowrapWords/rewrap, although the resulting new bubble of ickiness that would pop up next to it would perhaps be similar. Small things that might or might not be improvements: make breaks have normal whitespace, and make lines with only one word have normal whitespace (text/plain).

1 0

dillo-2.1.tar.bz2
by jcid＠dillo.org June 18, 2009

June 18, 2009

Hi, Working on: 1.- Solve the OpenSSL license issue and upload rc3. On Thu, Jun 18, 2009 at 05:24:25PM +0200, Devid Antonio Filoni wrote: > On Wed, Jun 17, 2009 at 11:45 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > > On Wed, Jun 17, 2009 at 10:01:12PM +0200, Devid Antonio Filoni wrote: > > [...] > > ?Devid: please send me the .deb and its directions when done. > DONE! You can find it at https://launchpad.net/~d.filoni/+archive/ppa > . However I found an error checking my package using lintian: > > E: dillo: possible-gpl-code-linked-with-openssl > N: > N: This package appears to be covered by the GNU GPL but depends on the > N: OpenSSL libssl package and does not mention a license exemption or > N: exception for OpenSSL in its copyright file. The GPL (including version > N: 3) is incompatible with some terms of the OpenSSL license, and therefore > N: Debian does not allow GPL-licensed code linked with OpenSSL libraries > N: unless there is a license exception explicitly permitting this. > N: > N: If only the Debian packaging, or some other part of the package not > N: linked with OpenSSL, is covered by the GNU GPL, please add a lintian > N: override for this tag. Lintian currently has no good way of > N: distinguishing between that case and problematic packages. > N: > N: Severity: serious, Certainty: wild-guess > > Can you please fix it? AFAIS, the only program that links to OpenSSL is the https dpi. i.e. The ssl-enabled dillo binary doesn't link to it. https.filter.dpi links to it. IANAL, but it looks like giving permission for this dpi is enough, and it's already done in its sources (dpi/https.c): * [...] * As a special exception permission is granted to link the code of * the https dillo plugin with the OpenSSL project's "OpenSSL" * library, and distribute the linked executables, without including * the source code for OpenSSL in the source distribution. You must * obey the GNU General Public License, version 3, in all respects * for all of the code used other than "OpenSSL". * */ Please let me know if this is _really_ enough or if some extra legal formula must be added somewhere else. TIA. -- Cheers Jorge.-

2 2

dillo-2.1.tar.bz2
by jcid＠dillo.org June 18, 2009

June 18, 2009

On Thu, Jun 18, 2009 at 05:24:25PM +0200, Devid Antonio Filoni wrote: > On Wed, Jun 17, 2009 at 11:45 PM, Jorge Arellano Cid<jcid(a)dillo.org> wrote: > > [...] > > ?BTW, the rc2 version of dillo-2.1 (hopefully final) was > > just uploaded to http://www.dillo.org/download/ so packagers > > can make the respective files. > > > > ?The idea is to make the announcement tomorrow in the morning. > > > > ?Devid: please send me the .deb and its directions when done. > DONE! You can find it at https://launchpad.net/~d.filoni/+archive/ppa > . However I found an error checking my package using lintian: > > E: dillo: possible-gpl-code-linked-with-openssl > N: > N: This package appears to be covered by the GNU GPL but depends on the > N: OpenSSL libssl package and does not mention a license exemption or > N: exception for OpenSSL in its copyright file. The GPL (including version > N: 3) is incompatible with some terms of the OpenSSL license, and therefore > N: Debian does not allow GPL-licensed code linked with OpenSSL libraries > N: unless there is a license exception explicitly permitting this. > N: > N: If only the Debian packaging, or some other part of the package not > N: linked with OpenSSL, is covered by the GNU GPL, please add a lintian > N: override for this tag. Lintian currently has no good way of > N: distinguishing between that case and problematic packages. > N: > N: Severity: serious, Certainty: wild-guess > > Can you please fix it? OK guys, don't hurry! ---------------------------------------------------- Let's make the announcement early this Saturday 20. ---------------------------------------------------- That way we have until tomorrow to sort out the packaging problem and this license issue. I'd proceed in this order: 1.- Solve the OpenSSL license issue and upload rc3. 2.- To enable-ssl or not enable-ssl (define what to do). 3.- Get to the less painful package-system for the user given the current situation. (most probably distribution repositories) 4.- Future planning: how to get dillo2 into distros to enlarge its user base. FLTK2 vs FLTK-1.3 * I have plenty of info here, but will hold on until the previous points are done. Thanks for all the help. -- Cheers Jorge.-

1 0

dillo-2.1.tar.bz2
by jcid＠dillo.org June 17, 2009

June 17, 2009

On Wed, Jun 17, 2009 at 03:33:56AM +0000, corvid wrote: > I just remembered that the README needs to be updated > since it talks about all of the new things that 2.0 brought. I just updated the repo. Please give it a review and fix the grammar where necessary. The patch for working keyboard under numlock was also committed (overlooked by me). Those having trouble with rc1, please confirm the repo (rc2) works OK now. When I get both OKs, I'll upload a new tarball for making the respective packages. If there's anything else pending, speak now! -- Cheers Jorge.-

1 0