- Dillo-dev - lists.mailman3.com

dillo-2.0 rc1 is in CVS

by corvid＠lavabit.com

I see that by default we end up with -g and -O2 for CFLAGS, but neither for CXXFLAGS. It would be nice to be able to teach autoconf (or whatever it is that decides that) to make this consistent.

Oct. 11, 2008

dillo-2.0 rc1 is in CVS

by jcid＠dillo.org

Hi there, CVS has rc1! Was moved into dillorc/dillo/2.0. A simple workaround patch for sylpheed was committed. Please get it from: http://www.dillo.org/test/dillo-2.0rc1.tar.bz2 and give it a compilation, installation and some testing. If it's OK, maybe Sunday is a good day for release. Comments are welcome. -- Cheers Jorge.-

Oct. 11, 2008

patch: close windows from menubar

by jcid＠dillo.org

On Fri, Oct 10, 2008 at 04:13:01PM +0200, Johannes Hofmann wrote: > On Thu, Oct 09, 2008 at 04:26:02PM -0400, Jorge Arellano Cid wrote: > > On Wed, Oct 08, 2008 at 05:04:29PM +0200, Joerg Sonnenberger wrote: > > > On Wed, Oct 08, 2008 at 03:32:42PM +0100, Jeremy Henty wrote: > > > > On Wed, Oct 08, 2008 at 01:09:48PM +0200, Joerg Sonnenberger wrote: > > > > > > > > > ... why would you want dillo1 and dillo2 at the same time. > > > > > > > > I don't know. But when you start saying "No-one could *possibly* want > > > > to do that, so let's stop supporting it" then you are riding for a > > > > fall. Why make ourselves hostages to fortune? Why not make *sure* we > > > > avoid the problem rather than gambling that we've second-guessed our > > > > entire user base? Murphy's law applies, so play it safe unless > > > > there's a compelling reason not to. > > > > > > You are adding the overhead of changing user behavior though. The claws > > > backend might be a good reason, frankly it is the only one I see so far. > > > > OK, just checked Debian and Ubuntu and both have the dillo > > viewer plugin for sylpheed with a dependency on the plain "dillo" > > package. > > > > Looking around in the FLTK docs, there's this function: > > > > CreatedWindow::set_xid() > > > > It looks promising. Unfortunately I haven't found a full > > code example to make it work. > > > > If somebody knows how to use it, it'd be simple to make a "drop > > in" replacement for dillo1, and avoid the problems discussed in > > this thread. > > I think it's supposed to work more or less like in attached test program. > When called with a (decimal) window id (from xlsclients) it draws a small > but visible frame on that window. > I don't know why it doesn't work correctly. Probabely some more > setup necessary... Dejan L. sent me this code as an example: http://www.dillo.org/test/gnash.cc ufortunately I can't get to make something that works with it. -- Cheers Jorge.-

Oct. 10, 2008

patch: close windows from menubar

by Johannes.Hofmann＠gmx.de

On Thu, Oct 09, 2008 at 04:26:02PM -0400, Jorge Arellano Cid wrote: > On Wed, Oct 08, 2008 at 05:04:29PM +0200, Joerg Sonnenberger wrote: > > On Wed, Oct 08, 2008 at 03:32:42PM +0100, Jeremy Henty wrote: > > > On Wed, Oct 08, 2008 at 01:09:48PM +0200, Joerg Sonnenberger wrote: > > > > > > > ... why would you want dillo1 and dillo2 at the same time. > > > > > > I don't know. But when you start saying "No-one could *possibly* want > > > to do that, so let's stop supporting it" then you are riding for a > > > fall. Why make ourselves hostages to fortune? Why not make *sure* we > > > avoid the problem rather than gambling that we've second-guessed our > > > entire user base? Murphy's law applies, so play it safe unless > > > there's a compelling reason not to. > > > > You are adding the overhead of changing user behavior though. The claws > > backend might be a good reason, frankly it is the only one I see so far. > > OK, just checked Debian and Ubuntu and both have the dillo > viewer plugin for sylpheed with a dependency on the plain "dillo" > package. > > Looking around in the FLTK docs, there's this function: > > CreatedWindow::set_xid() > > It looks promising. Unfortunately I haven't found a full > code example to make it work. > > If somebody knows how to use it, it'd be simple to make a "drop > in" replacement for dillo1, and avoid the problems discussed in > this thread. I think it's supposed to work more or less like in attached test program. When called with a (decimal) window id (from xlsclients) it draws a small but visible frame on that window. I don't know why it doesn't work correctly. Probabely some more setup necessary... Cheers, Johannes

Oct. 10, 2008

Altavista search does not work

by corvid＠lavabit.com

Christopher wrote: > Doing web searches using www.altavista.com does not work. It is as > if the search terms are not submitted. The following HTML errors > are detected: > > HTML warning: line 2, the required DOCTYPE declaration is missing (or invalid) > HTML warning: line 68, - forcing close of open tag: <form> > HTML warning: line 68, FORM lacks a Submit button > HTML warning: line 94, unexpected closing tag: </form>. -- expected </table> > > Searching for "Images", "MP3/Audio", or "Video" instead of "Web" > or "News" works well. > > Is this a problem with altavista rather than with dillo? It looks like altavista just threw together their form and table tags rather than nesting them.

Oct. 10, 2008

Altavista search does not work

by christopher.illies＠ki.se

Doing web searches using www.altavista.com does not work. It is as if the search terms are not submitted. The following HTML errors are detected: HTML warning: line 2, the required DOCTYPE declaration is missing (or invalid) HTML warning: line 68, - forcing close of open tag: <form> HTML warning: line 68, FORM lacks a Submit button HTML warning: line 94, unexpected closing tag: </form>. -- expected </table> Searching for "Images", "MP3/Audio", or "Video" instead of "Web" or "News" works well. Is this a problem with altavista rather than with dillo? I am using the latest dillo from cvs and fltk-2.0.r6305. Christopher

Oct. 10, 2008

patch: close windows from menubar

by jcid＠dillo.org

On Thu, Oct 09, 2008 at 08:22:22PM +0000, corvid wrote: > Johannes wrote: > > On Thu, Oct 09, 2008 at 06:16:21PM +0000, corvid wrote: > > > Johannes wrote: > > > > Anyway, what about a runtime option to choose the buffering scheme > > > > (patch attached). > > > > Please review the wording especially in the dillo2rc comment. > > > > > > I just noticed that when I use findtext now, the line above the > > > highlighted line is a bit darker/bolder than the rest. > > > Clicking on a link causes the same thing. > > > > Ouch. I forgot the clipping calls in my compile-time to run-time > > conversion of the double buffering option. > > > > Please test attached fix. > > Looks good so far... Committed. -- Cheers Jorge.-

Oct. 9, 2008

patch: close windows from menubar

by jcid＠dillo.org

On Wed, Oct 08, 2008 at 05:04:29PM +0200, Joerg Sonnenberger wrote: > On Wed, Oct 08, 2008 at 03:32:42PM +0100, Jeremy Henty wrote: > > On Wed, Oct 08, 2008 at 01:09:48PM +0200, Joerg Sonnenberger wrote: > > > > > ... why would you want dillo1 and dillo2 at the same time. > > > > I don't know. But when you start saying "No-one could *possibly* want > > to do that, so let's stop supporting it" then you are riding for a > > fall. Why make ourselves hostages to fortune? Why not make *sure* we > > avoid the problem rather than gambling that we've second-guessed our > > entire user base? Murphy's law applies, so play it safe unless > > there's a compelling reason not to. > > You are adding the overhead of changing user behavior though. The claws > backend might be a good reason, frankly it is the only one I see so far. OK, just checked Debian and Ubuntu and both have the dillo viewer plugin for sylpheed with a dependency on the plain "dillo" package. Looking around in the FLTK docs, there's this function: CreatedWindow::set_xid() It looks promising. Unfortunately I haven't found a full code example to make it work. If somebody knows how to use it, it'd be simple to make a "drop in" replacement for dillo1, and avoid the problems discussed in this thread. BTW, I'm inclined to using dillorc/dillo/2.0 in the release. -- Cheers Jorge.-

Oct. 9, 2008

patch: close windows from menubar

by corvid＠lavabit.com

Johannes wrote: > On Thu, Oct 09, 2008 at 06:16:21PM +0000, corvid wrote: > > Johannes wrote: > > > Anyway, what about a runtime option to choose the buffering scheme > > > (patch attached). > > > Please review the wording especially in the dillo2rc comment. > > > > I just noticed that when I use findtext now, the line above the > > highlighted line is a bit darker/bolder than the rest. > > Clicking on a link causes the same thing. > > Ouch. I forgot the clipping calls in my compile-time to run-time > conversion of the double buffering option. > > Please test attached fix. Looks good so far...

Oct. 9, 2008

patch: close windows from menubar

by Johannes.Hofmann＠gmx.de

On Thu, Oct 09, 2008 at 06:16:21PM +0000, corvid wrote: > Johannes wrote: > > Anyway, what about a runtime option to choose the buffering scheme > > (patch attached). > > Please review the wording especially in the dillo2rc comment. > > I just noticed that when I use findtext now, the line above the > highlighted line is a bit darker/bolder than the rest. > Clicking on a link causes the same thing. Ouch. I forgot the clipping calls in my compile-time to run-time conversion of the double buffering option. Please test attached fix. Cheers, Johannes

Oct. 9, 2008