- Dillo-dev - lists.mailman3.com

[patch]: change the default tab label to "Dillo"

by jcid＠dillo.org

On Mon, Oct 20, 2008 at 12:21:49PM +0100, Jeremy Henty wrote: > > *ahem*, replying to myself. > > > ... I think it looks a little sad when a new tab pops up with the > > pointless label "Label", so I changed it to "Dillo". > > No comments on this? It seems to have vanished without trace. It doesn't seem to make much difference (and we have no comments so far). Although I see one point with the "Label" label ;), it suggests that there goes a label that's yet unset. -- Cheers Jorge.-

Oct. 21, 2008

dillo-2.0 compilation failure

by corvid＠lavabit.com

Ben wrote: > corvid wrote: > >> form.cc: In member function ?Dstr* DilloHtmlForm::encodeText(void*, > >> Dstr**)?: > >> form.cc:1261: error: invalid conversion from ?const char**? to ?char**? > >> form.cc:1261: error: initializing argument 2 of ?size_t iconv(void*, > >> char**, size_t*, char**, size_t*)? > > > Did you run configure yourself? What type does inbuf_t have in config.log? > > yes, I ran configure first, with: > ./configure --prefix=/usr --host=i686-pc-linux-gnu > --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share > --sysconfdir=/etc --localstatedir=/var/lib --enable-gif --disable-ipv6 > --enable-jpeg --enable-png --enable-ssl --build=i686-pc-linux-gnu > > > % grep inbuf_t work/dillo-2.0/config.log > #define inbuf_t const char Hmm... A minute with google teaches me that gentoo people run into problems when system versions of things conflict with portage versions, but then I don't know enough to have any idea whether our config test would be picking up the wrong one for some reason...

Oct. 21, 2008

dillo-2.0 compilation failure

by akemnade＠tzi.de

On Tue, 21 Oct 2008 19:39:51 +0200 Ben de Groot <yngwin(a)gentoo.org> wrote: > corvid wrote: > >> form.cc: In member function ?Dstr* DilloHtmlForm::encodeText(void*, > >> Dstr**)?: > >> form.cc:1261: error: invalid conversion from ?const char**? to ?char**? > >> form.cc:1261: error: initializing argument 2 of ?size_t iconv(void*, > >> char**, size_t*, char**, size_t*)? > > > Did you run configure yourself? What type does inbuf_t have in config.log? > > yes, I ran configure first, with: > ./configure --prefix=/usr --host=i686-pc-linux-gnu > --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share > --sysconfdir=/etc --localstatedir=/var/lib --enable-gif --disable-ipv6 > --enable-jpeg --enable-png --enable-ssl --build=i686-pc-linux-gnu > > > % grep inbuf_t work/dillo-2.0/config.log > #define inbuf_t const char > The iconv test is done with gcc in c-mode, form.cc in c++-mode. The first one might be less strict so the iconv test code in configure.in,configure does not produce errors. But -Wall should be added already to CFLAGS earlier.... Just some guesses. Greetings Andreas Kemnade

Oct. 21, 2008

dillo-2.0 compilation failure

by yngwin＠gentoo.org

corvid wrote: >> form.cc: In member function ?Dstr* DilloHtmlForm::encodeText(void*, >> Dstr**)?: >> form.cc:1261: error: invalid conversion from ?const char**? to ?char**? >> form.cc:1261: error: initializing argument 2 of ?size_t iconv(void*, >> char**, size_t*, char**, size_t*)? > Did you run configure yourself? What type does inbuf_t have in config.log? yes, I ran configure first, with: ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-gif --disable-ipv6 --enable-jpeg --enable-png --enable-ssl --build=i686-pc-linux-gnu % grep inbuf_t work/dillo-2.0/config.log #define inbuf_t const char -- Ben de Groot Gentoo Linux developer (lxde, media, desktop-misc) Gentoo Linux Release Engineering PR liaison __________________________________________________ yngwin(a)gentoo.org http://ben.liveforge.org/ irc://chat.freenode.net/#gentoo-media irc://irc.oftc.net/#lxde __________________________________________________

Oct. 21, 2008

dillo-2.0 compilation failure

by corvid＠lavabit.com

Ben wrote: > Hi, > > I'm trying to get an ebuild together to get dillo-2.0 into Gentoo Linux' > portage repository. But compilation fails for me with: > > form.cc: In member function ?Dstr* DilloHtmlForm::encodeText(void*, > Dstr**)?: > form.cc:1261: error: invalid conversion from ?const char**? to ?char**? > form.cc:1261: error: initializing argument 2 of ?size_t iconv(void*, > char**, size_t*, char**, size_t*)? > make[3]: *** [form.o] Error 1 > > This is with gcc-4.3.2. If anybody could have a look at this and shed > some light on it (as I'm not a C++ coder myself), I would be grateful. Did you run configure yourself? What type does inbuf_t have in config.log?

Oct. 21, 2008

Heavy load on X

by Johannes.Hofmann＠gmx.de

On Tue, Oct 21, 2008 at 12:19:15PM +0000, corvid wrote: > furaisanjin wrote: > > I find the reason now. I selected this option. > > > > limit_text_width=YES > > > > I missed the comment just above. > > > > # *** NOT HOOKED UP YET *** > > > > So after I set NO on limit_text_width, the problem has disappeared. > > Oh! > You have still found something interesting because I added that > comment _not_ because it was known to break anything, but because > there is not enough limit_text_width code for it to have > much of an observable effect -- that is, I didn't want people to > be disappointed when they set the option and nothing happened. > > (Johannes will know, but...) maybe it's triggering queueResize()s in a loop. void Textblock::setWidth (int width) { /* If limitTextWidth is set to YES, a queue_resize may also be * necessary. */ if (availWidth != width || limitTextWidth) { looks like a candidate... But I have not seen a page where limit_text_width=YES makes a difference anyway. Cheers, Johannes

Oct. 21, 2008

dillo-2.0 compilation failure

by yngwin＠gentoo.org

Hi, I'm trying to get an ebuild together to get dillo-2.0 into Gentoo Linux' portage repository. But compilation fails for me with: form.cc: In member function ?Dstr* DilloHtmlForm::encodeText(void*, Dstr**)?: form.cc:1261: error: invalid conversion from ?const char**? to ?char**? form.cc:1261: error: initializing argument 2 of ?size_t iconv(void*, char**, size_t*, char**, size_t*)? make[3]: *** [form.o] Error 1 This is with gcc-4.3.2. If anybody could have a look at this and shed some light on it (as I'm not a C++ coder myself), I would be grateful. Regards, -- Ben de Groot Gentoo Linux developer (lxde, media, desktop-misc) Gentoo Linux Release Engineering PR liaison __________________________________________________ yngwin(a)gentoo.org http://ben.liveforge.org/ irc://chat.freenode.net/#gentoo-media irc://irc.oftc.net/#lxde __________________________________________________

Oct. 21, 2008

Heavy load on X

by corvid＠lavabit.com

furaisanjin wrote: > I find the reason now. I selected this option. > > limit_text_width=YES > > I missed the comment just above. > > # *** NOT HOOKED UP YET *** > > So after I set NO on limit_text_width, the problem has disappeared. Oh! You have still found something interesting because I added that comment _not_ because it was known to break anything, but because there is not enough limit_text_width code for it to have much of an observable effect -- that is, I didn't want people to be disappointed when they set the option and nothing happened. (Johannes will know, but...) maybe it's triggering queueResize()s in a loop.

Oct. 21, 2008

Heavy load on X

by corvid＠lavabit.com

furaisanjin wrote: > <button type="submit">search</button> Hmm... I wonder whether it has something to do with ComplexButton. Does the following cause the problem as well? <html> <head> <title>test</title> </head> <body> <form action="http://search.itmedia.co.jp/" method="GET"> <input name="img" type="image" src="http://www.dillo.org/main-small.jpg"> </form> </body> </html>

Oct. 21, 2008

Heavy load on X

by furaisanjin＠gmail.com

2008/10/21 Jeremy Henty <onepoint(a)starurchin.org>: > Just guessing, but is your fltk2 using cairo? That's been the cause > of other problems. no, I didn't add any option for fltk2. I find the reason now. I selected this option. limit_text_width=YES I missed the comment just above. # *** NOT HOOKED UP YET *** So after I set NO on limit_text_width, the problem has disappeared. Regards, furaisanjin

Oct. 21, 2008