- Dillo-dev - lists.mailman3.com

What's currently broken in... (Re: [Dillo-dev] 1.3 port)

by corvid＠lavabit.com

- xembed - the preferred font code in dillo.cc. - The test/ programs have UI problems (scrollbars, PgUp, etc.). - drawing with nested layouts (Amazing what you can get used to and forget about!)

May 2, 2011

Fw: Re: [Dillo-dev] next release of dillo?

by jcid＠dillo.org

On Sun, May 01, 2011 at 08:12:39AM -0700, Globe Trotter wrote: > --- On Sun, 5/1/11, corvid <corvid(a)lavabit.com> wrote: > > From: corvid <corvid(a)lavabit.com> > > Subject: Re: [Dillo-dev] next release of dillo? > > To: Dillo-dev(a)dillo.org > > Date: Sunday, May 1, 2011, 1:18 AM > > Globe Trotter wrote: > > > just wondering when the next release of dillo will be, > > > i.e. if there is a planned timeline? we appear to be at > > > dillo2.2 for a while now? > > > > > IIRC, maybe a month or two ago, Jorge wanted to wait until > > FLTK 1.3 was released before making any Dillo releases at all, > > but it seems that users find fltk bugs at the same rate that > > developers fix them ( http://fltk.org/roadmap.php#1.3 ), so... > > > Yes, i know, thanks! Hopefully, fltk1.3 will not go the same > way as fltk2. Fortunately fltk1.3 seems to be going in a very different way, with near five active core developers, which have done lots of work on it the last months. Since rc3, the devs focused on utf8 issues on different platforms and also widget printing (these tasks are quite complex), while also doing STR work. OTOH, for years (as I do review the changelogs) FLTK2 has mainly "nominal" updates (i.e. one-line patches or really minor stuff). This group is responsive too: e.g. http://www.fltk.org/str.php?L2615 (closed in one day) > IMO, dillo's adoption seems to be negatively > affected largely because of the uncertain pace and status of > fltk....for instance, fedora repos are not updating dillo from > 0.8.6 simply because it is based on fltk2, which is not > released and perhaps will never be, That's was exactly my main point for going with fltk1.3. We saw that our way into official distro repositories (i.e a distro-packaged dillo) is banned because of the unreleased library. The possibility of a statically linked package, though technically possible, is banned by distro's policy too: they don't include statically linked apps. because of the nightmare of maintenance/security it conveys (quite understandable). So, while we don't have an officially released underlying toolkit we're out of distros. :-P Making a new, dillo-2.3 release is not much of a point because people using dillo already have to get it from us and build it themselves, which they already do. When fltk-1.3 is released we could make a dillo-2 final release letting users know we're going with the dillo-3 series. Although if somebody comes with a good reason to make a dillo-2 final release now, we can make it. -- Cheers Jorge.-

May 2, 2011

Bookmarks sections

by dukeofperl＠ml1.net

Hi ... I created a section, and immediately under that "top-level" section, 3 additional "sub-sections". No problems here. I now want to create another (and additional) "top-level" sections. I can't seem to figure out how to do that. Each new section, is created as a "sub-section" of the original "top-level" one. Anybody know if it's possible to do what I'm after? TIA ... -- Duke

May 2, 2011

Issues building Dillo

by dukeofperl＠ml1.net

On Sun, 1 May 2011, corvid wrote: > Duke wrote: > > In file included from /usr/include/bits/errno.h:25, > > from /usr/include/errno.h:36, > > from dlib.c:25: > > /usr/include/linux/errno.h:4:23: error: asm/errno.h: No such file or > > directory > > What do you get from > ls -l /usr/include/asm/errno.h > and > cpp -v > ? I fixed the problem and got Dillo rebuilt! :D had to do some fancy symlinking. If anybody is on a Debian-flavored outfit and having the same issue, the following fixed it: sudo ln -s /usr/src/linux-headers-2.6.38-8/include/asm-generic/ /usr/include/asm -- Duke

May 2, 2011

What's currently broken in... (Re: [Dillo-dev] 1.3 port)

by jcid＠dillo.org

On Sun, May 01, 2011 at 09:42:30PM +0000, corvid wrote: > I wrote: > > Looks like we still need > > - xembed > > - the preferred font code in dillo.cc. > > - The test/ programs have UI problems (scrollbars, PgUp, etc.). > - The show_progress_box pref doesn't do anything. Patch committed for the last one. -- Cheers Jorge.-

May 2, 2011

1.3 port

by rogerx.oss＠gmail.com

> On Sun, May 01, 2011 at 05:57:36AM +0200, Thomas Orgis wrote: >Am Sat, 30 Apr 2011 12:20:37 -0800 >schrieb Roger <rogerx.oss(a)gmail.com>: > >> Standard Browser such as Seamonkey/Firefox: >> Right Click on Tab = Open tab menu >> Middle Click on Tab/Page = Paste URL and load page > >Middle-Click on the tab handle itself closes ... middle-click into the page area loads URL. Right? No. Mozilla/Seamonkey -> Middle click on tab or page loads a URL from the copy/paste buffer.

May 2, 2011

What's currently broken in... (Re: [Dillo-dev] 1.3 port)

by corvid＠lavabit.com

I wrote: > Looks like we still need > - xembed > - the preferred font code in dillo.cc. - The test/ programs have UI problems (scrollbars, PgUp, etc.). - The show_progress_box pref doesn't do anything.

May 1, 2011

patch: [Re: [Dillo-dev] Linked image borders.]

by Johannes.Hofmann＠gmx.de

On Sun, May 01, 2011 at 08:30:44PM +0000, corvid wrote: > I wrote: > > I wrote: > > > Rob wrote: > > > > On this page,?http://www3.sympatico.ca/rsquared/gdb/, there are two images at the bottom which link to the W3C HTML and CSS validation pages. ?The inline style for the images is as follows: > > > > style="border:0;width:88px;height:31px" > > > > On every browser I have used, including Dillo 2.2, the blue link box around the images has not been displayed. ?Under the Dillo FLTK 1.3 port, it shows them. ?My question is, why? ?Which is the correct behaviour? > > > > > > Must be a parsing problem. It works if I change border:0 to > > > border:0px, but the unit is optional after 0. > > > > My impression is that we broke it when implementing line-height, > > with the length type changing from CSS_LENGTH_TYPE_PX to > > CSS_LENGTH_TYPE_NONE, and computeValue() not expecting that. > > I'll leave this to Johannes, since he'll know what he'll want > > to do about it. > > For the sake of having something, see attached. > diff -r 5b4c489423d2 src/styleengine.cc > --- a/src/styleengine.cc Wed Apr 20 02:45:55 2011 +0000 > +++ b/src/styleengine.cc Sun May 01 20:26:40 2011 +0000 > @@ -619,6 +619,9 @@ > case CSS_LENGTH_TYPE_EX: > *dest = roundInt (CSS_LENGTH_VALUE(value) * font->xHeight); > return true; > + case CSS_LENGTH_TYPE_NONE: > + *dest = 0; > + return true; > default: > break; > } Thanks for bringing this up again. Committed with an additional assert(). Cheers, Johannes

May 1, 2011

patch: [Re: [Dillo-dev] Linked image borders.]

by corvid＠lavabit.com

I wrote: > I wrote: > > Rob wrote: > > > On this page,?http://www3.sympatico.ca/rsquared/gdb/, there are two images at the bottom which link to the W3C HTML and CSS validation pages. ?The inline style for the images is as follows: > > > style="border:0;width:88px;height:31px" > > > On every browser I have used, including Dillo 2.2, the blue link box around the images has not been displayed. ?Under the Dillo FLTK 1.3 port, it shows them. ?My question is, why? ?Which is the correct behaviour? > > > > Must be a parsing problem. It works if I change border:0 to > > border:0px, but the unit is optional after 0. > > My impression is that we broke it when implementing line-height, > with the length type changing from CSS_LENGTH_TYPE_PX to > CSS_LENGTH_TYPE_NONE, and computeValue() not expecting that. > I'll leave this to Johannes, since he'll know what he'll want > to do about it. For the sake of having something, see attached.

May 1, 2011

next release of dillo?

by dukeofperl＠ml1.net

On Sun, 1 May 2011, corvid wrote: > Duke wrote: > > On Sun, 1 May 2011, corvid wrote: > > > > > Globe Trotter wrote: > > > > IMO, dillo's adoption seems to be negatively affected largely because of the uncertain pace and status of fltk. > > > > > > Are there others that make a point of being fast and light? > > > > xlinks2 i.e. links2 in graphics mode. Ordinary links2 is pretty good also > > Oops, I meant graphical toolkits. Sorry about that! -- Duke

May 1, 2011