- Dillo-dev - lists.mailman3.com

Fw: [Dillo-dev] FLTK 1.3 and current development version

by Johannes.Hofmann＠gmx.de

On Sun, Jul 03, 2011 at 10:53:38PM +0200, Georg Potthast wrote: > I looked at the log and saw this error message: > > Nav_open_url: new url='dpi:/vsource/:about:splash' > ** ERROR **: [Dpi_read_comm_keys] No such file or directory (ENOENT) > Dpi_start_dpid: Not enough memory (ENOMEM) > ** ERROR **: dpi.c: can't start dpi daemon > > I tried to view the source of the splash page. Is there really not enough memory or is this a follow-up error to the first one? Did you run "make install"? Is the dpid binary somewhere in your PATH? You can check with "type dpid" Cheers, Johannes

July 4, 2011

Fw: [Dillo-dev] FLTK 1.3 and current development version

by mailbox＠georgpotthast.de

I looked at the log and saw this error message: Nav_open_url: new url='dpi:/vsource/:about:splash' ** ERROR **: [Dpi_read_comm_keys] No such file or directory (ENOENT) Dpi_start_dpid: Not enough memory (ENOMEM) ** ERROR **: dpi.c: can't start dpi daemon I tried to view the source of the splash page. Is there really not enough memory or is this a follow-up error to the first one? Georg

July 3, 2011

FLTK 1.3 and current development version

by mailbox＠georgpotthast.de

I have some trouble using Dillo 1.3. When I click on the "Book" icon, select "view page source" from the menu or try to load a page from disk I get the message: "ERROR: can't start dpid daemon (URL scheme='dpi') or 'file' What could be a possible cause for this problem? Where in the code does it try to start this daemon? Georg

July 3, 2011

Tooltips bug

by Johannes.Hofmann＠gmx.de

On Fri, Jul 01, 2011 at 05:02:41PM -0400, Jorge Arellano Cid wrote: > Hi, > > I'm giving a look into the old dragging-tooltip bug: e.g. show > an HTML image's tooltip, then scroll out of it with keyboard or > mousewheel, and the tooltip will not be erased. > > Funny how FltkTooltip::onLeave() is called, but the tooltip > window stays anyway. > > Has anybody looked into this one? I looked into this a few times. When scrolling the moved content just gets copied server side and only the newly exposed part is actually drawn. That's how the tooltip moves up or down. However the disappearing tooltip should request the area to be redrawn that it had covered. For some reason it redraws not the right rectangle. I think redraws the area where the tooltip had been before the scroll or something like that. You can see what's going on like this: diff -r 86cc8fe82da0 dw/fltkviewbase.cc --- a/dw/fltkviewbase.ccMon Jun 27 21:01:21 2011 -0400 +++ b/dw/fltkviewbase.ccSun Jul 03 21:20:54 2011 +0200 @@ -182,6 +182,8 @@ fl_rectf (X, Y, W, H); theLayout->expose (this, &r); } +fl_color(FL_RED); +fl_rect(X, Y, W, H); exposeArea = NULL; } Cheers, Johannes

July 3, 2011

Latest round of Win32 patches

by obeythepenguin＠gmail.com

On Sun, 03 Jul 2011 14:29:32 -0400, Johannes Hofmann <Johannes.Hofmann(a)gmx.de> wrote: >> - Cleaned up sockets portability layer (dsock) >> - Transparent SSL support (through dsock) using OpenSSL/CyaSSL > > I haven't looked at the code yet, but if this could be extended to > get proper SSL support it would be really great. You mean certificate checking, error prompting, etc.? >> - Sane in-memory cookies implementation (no cookies.txt needed) > > But that means it doesn't support persistent cookies, right? They can be re-enabled with a ./configure option. ~Benjamin

July 3, 2011

Latest round of Win32 patches

by Johannes.Hofmann＠gmx.de

Hi Benjamin, On Sat, Jul 02, 2011 at 01:12:51PM -0400, Benjamin Johnson wrote: > In case anyone's still interested, I've got the latest round of > Win32 patches up: > http://dillo-win32.sourceforge.net/dillo/patches.php > > It's still based on dillo2, but since most of the patches are > "behind the scenes" (network code, etc.), they should work fine with > dillo3. (I'm planning to switch over eventually.) Apart from the > portability code, most of it isn't even Windows-specific; I've > personally been using it quite a bit lately on OpenBSD. > > Some highlights: > - Cleaned up sockets portability layer (dsock) > - Transparent SSL support (through dsock) using OpenSSL/CyaSSL I haven't looked at the code yet, but if this could be extended to get proper SSL support it would be really great. > - Built-in libcurl-based downloader with glitch-free user interface ;-) > - Built-in preferences GUI (no manual dillorc editing needed) This is the old plugin or not-plugin discussion, I guess. > - Sane in-memory cookies implementation (no cookies.txt needed) But that means it doesn't support persistent cookies, right? > - Various small tweaks, usability improvements, and bugfixes > > Just thought I'd share, > ~Benjamin That's always appreciated. Cheers, Johannes

July 3, 2011

FLTK 1.3 and current development version

by mailbox＠georgpotthast.de

Thank you for your messages. I had used Mercurial for Windows and after moving the files to Linux the "IO" directory had become an "io" directory so autogen.sh did not run right away. This had irritated me. I managed to get autogen.sh run now. Georg

July 3, 2011

Latest round of Win32 patches

by obeythepenguin＠gmail.com

In case anyone's still interested, I've got the latest round of Win32 patches up: http://dillo-win32.sourceforge.net/dillo/patches.php It's still based on dillo2, but since most of the patches are "behind the scenes" (network code, etc.), they should work fine with dillo3. (I'm planning to switch over eventually.) Apart from the portability code, most of it isn't even Windows-specific; I've personally been using it quite a bit lately on OpenBSD. Some highlights: - Cleaned up sockets portability layer (dsock) - Transparent SSL support (through dsock) using OpenSSL/CyaSSL - Built-in libcurl-based downloader with glitch-free user interface ;-) - Built-in preferences GUI (no manual dillorc editing needed) - Sane in-memory cookies implementation (no cookies.txt needed) - Various small tweaks, usability improvements, and bugfixes Just thought I'd share, ~Benjamin

July 2, 2011

FLTK 1.3 and current development version

by jcid＠dillo.org

On Sat, Jul 02, 2011 at 09:50:31AM +0200, Georg Potthast wrote: > Using Mercurial I was able to clone dillo port1.3. However, it has no configure nor makefile and no makefiles in the subdirectories. Are there instructions how to use autoconf and automake for that? > > Or can you make a dillo 1.3 preview version available? Please follow directions from: http://www.dillo.org/source.html but use fltk-1.3 and dillo_port1.3 (I'll update the directions soon) -- Cheers Jorge.-

July 2, 2011

FLTK 1.3 and current development version

by mailbox＠georgpotthast.de

Using Mercurial I was able to clone dillo port1.3. However, it has no configure nor makefile and no makefiles in the subdirectories. Are there instructions how to use autoconf and automake for that? Or can you make a dillo 1.3 preview version available? Georg

July 2, 2011