- Dillo-dev - lists.mailman3.com

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

Issues building Dillo

by dukeofperl＠ml1.net

On Sun, 1 May 2011, Rob S. wrote: > > > > dnormandin@select-man:~$ > > ls -l /usr/include/asm/errno.h > > ls: cannot access /usr/include/asm/errno.h: No such file or directory > > dnormandin@select-man:~$ > > cpp v > > cpp: v: No such file or directory > > cpp: warning: '-x c' after last input file has no effect > > cpp: no input files > > Well, for the second test, all you need to do there is add the - to the v > cpp -v > or? > CC -v > or g++ -v > The '-' indicates to the shell that what comes next is a switch, and in the case of the GCC C++ compiler, the option -v gives the version. ?Alternatively, the Solaris C++ compiler uses -V. Too early in the morning here in Canada, when I tested and wrote the reply. :) Here we go again: dnormandin@select-man:~/ cpp -v Using built-in specs. Target: i486-linux-gnu Configured with: ../gcc-4.1.2+gm2-20101211/configure --enable-languages=c,c++,gm2 --prefix=/opt/gm2 --libexecdir=/usr/lib/gm2/libexec --infodir=/opt/gm2/share/info --mandir=/opt/gm2/share/man --disable-nls --enable-long-long --without-included-gettext --with-dwarf2 --disable-libssp --disable-multilib --enable-libstdcxx-debug --enable-shared --build=i486-linux-gnu --host=i486-linux-gnu Thread model: posix gcc version 4.1.2 /usr/lib/gm2/libexec/gcc/i486-linux-gnu/4.1.2/cc1 -E -quiet -v - -mtune=i486 ignoring nonexistent directory "/opt/gm2/lib/gcc/i486-linux-gnu/4.1.2/../../../../i486-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /usr/local/include /opt/gm2/include /opt/gm2/lib/gcc/i486-linux-gnu/4.1.2/include /usr/include End of search list. dnormandin@select-man:~/ locate errno.h /usr/include/errno.h /usr/include/asm-generic/errno.h /usr/include/bits/errno.h /usr/include/i386-linux-gnu/asm/errno.h /usr/include/linux/errno.h /usr/include/sys/errno.h /usr/lib/syslinux/com32/include/errno.h /usr/local/include/apr_errno.h /usr/local/include/mailutils/errno.h /usr/share/doc/fp-docs/2.4.0/rtl/baseunix/fpgeterrno.html /usr/share/doc/fp-docs/2.4.0/rtl/baseunix/fpseterrno.html /usr/share/doc/fp-docs/2.4.0/rtl/oldlinux/errno.html /usr/src/linux-headers-2.6.38-8/arch/alpha/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/arm/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/arm/mach-bcmring/include/csp/errno.h /usr/src/linux-headers-2.6.38-8/arch/avr32/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/blackfin/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/cris/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/frv/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/h8300/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/ia64/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/m32r/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/m68k/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/microblaze/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/mips/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/mn10300/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/parisc/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/powerpc/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/s390/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/score/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/sh/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/sparc/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/tile/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/x86/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/arch/xtensa/include/asm/errno.h /usr/src/linux-headers-2.6.38-8/include/asm-generic/errno.h /usr/src/linux-headers-2.6.38-8/include/linux/errno.h /usr/src/linux-headers-2.6.38-8-generic/include/linux/errno.h -- Duke

May 1, 2011

Issues building Dillo

by corvid＠lavabit.com

Duke wrote: > dnormandin@select-man:~$ > ls -l /usr/include/asm/errno.h > ls: cannot access /usr/include/asm/errno.h: No such file or directory > dnormandin@select-man:~$ > That means that my system is missing ......? I don't know anything about xubuntu and what its kernel-headers package may do exactly, but something's not right.

May 1, 2011

Issues building Dillo

by mr_semantics＠hotmail.com

> dnormandin@select-man:~$ > ls -l /usr/include/asm/errno.h > ls: cannot access /usr/include/asm/errno.h: No such file or directory > dnormandin@select-man:~$ > cpp v > cpp: v: No such file or directory > cpp: warning: '-x c' after last input file has no effect > cpp: no input files Well, for the second test, all you need to do there is add the - to the v cpp -v or? CC -v or g++ -v The '-' indicates to the shell that what comes next is a switch, and in the case of the GCC C++ compiler, the option -v gives the version. ?Alternatively, the Solaris C++ compiler uses -V.

May 1, 2011

next release of dillo?

by corvid＠lavabit.com

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.

May 1, 2011

next release of dillo?

by obeythepenguin＠gmail.com

On Sun, 01 May 2011 12:06:49 -0400, corvid <corvid(a)lavabit.com> 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? I can think of a couple other light ones (FOX, among others), but I don't think any of them make it as high a priority as FLTK. They don't seem to be as well-maintained or documented, either. Of course, we could in theory program it against straight Xlib. I think Opera actually does that now, when Gtk+ and Qt aren't available (they apparently have a lot of free time on their hands). But that would be messy and a real portability nightmare. Or we could fork FLTK and ship it in our own source tree. A lot of larger projects -- OpenOffice.org and Audacity, for example -- include dependencies with their stable tarballs, especially when they're lesser known or require a specific version. That's essentially what I've done with the Windows port; where FLTK was broken, I went ahead and fixed it myself. Granted, Dillo's not a large project, and including our own FLTK would be kludgy to say the least. But then again, we'd always have a "known good" version, and we wouldn't have to wait for the FLTK people to get their acts together. The low-level APIs (Xlib, Win32, etc.) don't change too often, so there shouldn't be much worry about it breaking. (And we only have to do it in stable releases, not hg. Granted, it adds some size to the tarball, but not a ridiculous amount, and IMHO it's worth it if it could lead to more widespread Dillo adoption.) Just a thought. ~Benjamin

May 1, 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 dnormandin@select-man:~$ ls -l /usr/include/asm/errno.h ls: cannot access /usr/include/asm/errno.h: No such file or directory dnormandin@select-man:~$ cpp v cpp: v: No such file or directory cpp: warning: '-x c' after last input file has no effect cpp: no input files That means that my system is missing ......? -- Duke

May 1, 2011

next release of dillo?

by dukeofperl＠ml1.net

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 -- Duke

May 1, 2011

next release of dillo?

by corvid＠lavabit.com

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?

May 1, 2011