- Dillo-dev - lists.mailman3.com

Connection problems on Mac OS X 10.6.7

by corvid＠lavabit.com

reza wrote: > But at least for me loading a page is a hit or miss experiment. Sometimes it > waits for a long time (maybe 2-3 minutes) and couldn't connect, as if there > was a DNS problem, other times it loads the same page easily in a few > seconds. Just out of curiosity, does anything change if you configure with --disable-threaded-dns? I tried valgrind's helgrind tool a couple of weeks ago, and it complains and complains about threads, but I didn't know whether any of it had any significance.

May 26, 2011

Connection problems on Mac OS X 10.6.7

by corvid＠lavabit.com

reza wrote: > I'm trying to > compile and run dillo on Mac OS 10.6.7 (and report the bugs I find :D ). That's great! > http.c: In function ?Http_connect_queued_sockets?: > http.c:177: warning: cast from pointer to integer of different size > dialog.cc: In function ?int a_Dialog_choice5(const char*, const char*, const > char*, const char*, const char*, const char*)?: > dialog.cc:177: warning: suggest a space before ?;? or explicit braces around > empty body in ?for? statement Should be fixed now.

May 26, 2011

Connection problems on Mac OS X 10.6.7

by obeythepenguin＠gmail.com

On Thu, 26 May 2011 03:34:06 -0400, reza farivar <rf.opensource(a)gmail.com> wrote: > Hi guys, > > First post here, thanks for all your hard work on Dillo! I'm trying to > compile and run dillo on Mac OS 10.6.7 (and report the bugs I find :D ). > I > followed instructions that Jorge sent me earlier, and it compiled > without an > error but a few warnings: > > [...] > > The good news is that Dillo runs. It also seems to eventually connect to > websites, which is good news too. > > But at least for me loading a page is a hit or miss experiment. > Sometimes it > waits for a long time (maybe 2-3 minutes) and couldn't connect, as if > there > was a DNS problem, other times it loads the same page easily in a few > seconds. Here's the output from the terminal, after trying to connect to > yahoo.com site unsuccessfully (waiting for a long time): > > $ src/dillo > paths: creating directory /Users/farivar2/.dillo. > paths: Cannot open file '/Users/farivar2/.dillo/dillorc' > paths: Using /usr/local/etc/dillo/dillorc > paths: Cannot open file '/Users/farivar2/.dillo/keysrc' > paths: Using /usr/local/etc/dillo/keysrc > dillo_dns_init: Here we go! (threaded) > Cookies: Created file: /Users/farivar2/.dillo/cookiesrc > Disabling cookies. > Nav_open_url: new url='about:splash' > Nav_open_url: new url='http://www.yahoo.com' > Dns_server [0]: www.yahoo.com is 209.191.122.70 69.147.125.65 > 67.195.160.76 > Connecting to 209.191.122.70 > > and it almost hangs here. During this time the CPU utilization hovers > around > 134% (on a dual core machine), with 3 threads and 48MB of memory usage. > > Is this behavior expected? Perhaps it's related to the warnings above? My > guess is that it's either a DNS problem or an HTTP connection problem, > resulting into a time-out case. The warnings are just the compiler noting ambiguous syntax; they shouldn't affect the compilation beyond that. It could be in the DNS or HTTP code. It could also be FLTK. After you send an HTTP request, Dillo uses some FLTK functions to watch the socket for activity. I had a similar problem when I did the Windows port, and it turns out it wasn't Dillo, but buggy and broken FLTK code. > P.S.3 Are there reference rendering snapshots available? The Yahoo's web > site and even Google's both render in a strange way (similar to the way > links2 renders them). In fact the only website that I could get to render > correctly is dillo.org (when it opens, other times it just decides not to > open even after 5 minutes of waiting). That's normal. Dillo still has extremely limited HTML support, so most pages do look rather funny (and it doesn't help that most sites don't recognize Dillo's user agent). A lot of sites, including Google, render better with a Mozilla/4.0 user agent. I actually have the Windows port default to "Mozilla/4.0 (compatible; Dillo 2.2)" for that reason. Cheers, ~Benjamin

May 26, 2011

Connection problems on Mac OS X 10.6.7

by rf.opensource＠gmail.com

Hi guys, First post here, thanks for all your hard work on Dillo! I'm trying to compile and run dillo on Mac OS 10.6.7 (and report the bugs I find :D ). I followed instructions that Jorge sent me earlier, and it compiled without an error but a few warnings: $ make|grep : http.c: In function ?Http_connect_queued_sockets?: http.c:177: warning: cast from pointer to integer of different size dialog.cc: In function ?int a_Dialog_choice5(const char*, const char*, const char*, const char*, const char*, const char*)?: dialog.cc:177: warning: suggest a space before ?;? or explicit braces around empty body in ?for? statement make[2]: Nothing to be done for `all'. make[2]: Nothing to be done for `all-am'. The good news is that Dillo runs. It also seems to eventually connect to websites, which is good news too. But at least for me loading a page is a hit or miss experiment. Sometimes it waits for a long time (maybe 2-3 minutes) and couldn't connect, as if there was a DNS problem, other times it loads the same page easily in a few seconds. Here's the output from the terminal, after trying to connect to yahoo.com site unsuccessfully (waiting for a long time): $ src/dillo paths: creating directory /Users/farivar2/.dillo. paths: Cannot open file '/Users/farivar2/.dillo/dillorc' paths: Using /usr/local/etc/dillo/dillorc paths: Cannot open file '/Users/farivar2/.dillo/keysrc' paths: Using /usr/local/etc/dillo/keysrc dillo_dns_init: Here we go! (threaded) Cookies: Created file: /Users/farivar2/.dillo/cookiesrc Disabling cookies. Nav_open_url: new url='about:splash' Nav_open_url: new url='http://www.yahoo.com' Dns_server [0]: www.yahoo.com is 209.191.122.70 69.147.125.65 67.195.160.76 Connecting to 209.191.122.70 and it almost hangs here. During this time the CPU utilization hovers around 134% (on a dual core machine), with 3 threads and 48MB of memory usage. Is this behavior expected? Perhaps it's related to the warnings above? My guess is that it's either a DNS problem or an HTTP connection problem, resulting into a time-out case. P.S. Sometimes it seems if I open another tab and enter another address it will help the first tab to load, but I can't get it to consistently act like that. Other times, it seems a tab can get stuck waiting for the host and can never load the page. It also seems adding http:// to the beggining of addresses help some times, but not consistently. P.S.2 I checked my network connection with my other browser (chrome) and it has no problem connecting the mentioned websites. P.S.3 Are there reference rendering snapshots available? The Yahoo's web site and even Google's both render in a strange way (similar to the way links2 renders them). In fact the only website that I could get to render correctly is dillo.org (when it opens, other times it just decides not to open even after 5 minutes of waiting). P.S.4 Jorge's instructions to compile dillo-1.3 for Mac OS X are as follows: 1.- <install fltk-1.3-rc5 from fltk.org> 2.- <install auto* tools, X devel, C/C++, jpeg, png, etc> 3.- <install mercurial> 4.- $ hg clone http://hg.dillo.org/dillo_port1.3 5.- $ cd dillo_port1.3 6.- $ ./autogen.sh 7.- $ CFLAGS="-g -O0" CXXFLAGS="-g -O0" ./configure --enable-ssl 8.- $ make|grep : 9.- $ sudo make install (this will install dillo, dpid, dpidc and the dpis) 10.- $ src/dillo -Reza

May 26, 2011

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

by rogerx.oss＠gmail.com

> On Wed, May 25, 2011 at 03:13:54PM +0000, corvid wrote: >Jorge wrote: >> On Sun, May 15, 2011 at 09:04:43PM +0200, Johannes Hofmann wrote: >> > >> > - There is a tab title even if there is only one tab. >> >> FYI, I'm testing a patch that does this. It uses a trick to >> receive events on a hidden tabbar and is designed so it's easy to >> set permanent tab buttons too (i.e. as now). >> >> Quick poll: What's your preferred mode? > >I prefer that the tab bar goes away when there's only one tab. > >I will feel surprise if anyone wants to have it visible when >there's only one tab. Well, be surprised. I like to see a tab even though there's no more then one visible. Reason being, Firefox tends (or tended) to resize the webpage and toolbars when migrating from one to more then one tabs, it boggled my mind when comprehending, "Now what changed??" It would take a few seconds to regain field of view, etc. (No glasses, 20/20 here, no drugs or alcohol, etc) But I'm guessing with FLTK, it won't make such vast changes when going from tabs to no tabs. Also, the Title of the webpage is usually kept within the tab. <shrugs, for what it's worth> -- Roger http://rogerx.freeshell.org/

May 26, 2011

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

by Johannes.Hofmann＠gmx.de

On Wed, May 25, 2011 at 04:15:35PM -0400, Jorge Arellano Cid wrote: > On Wed, May 25, 2011 at 08:41:35PM +0200, Johannes Hofmann wrote: > > On Wed, May 25, 2011 at 01:37:26PM -0400, Jorge Arellano Cid wrote: > > > On Wed, May 25, 2011 at 03:13:54PM +0000, corvid wrote: > > > > Jorge wrote: > > > > > On Sun, May 15, 2011 at 09:04:43PM +0200, Johannes Hofmann wrote: > > > > > > > > > > > > - There is a tab title even if there is only one tab. > > > > > > > > > > FYI, I'm testing a patch that does this. It uses a trick to > > > > > receive events on a hidden tabbar and is designed so it's easy to > > > > > set permanent tab buttons too (i.e. as now). > > > > > > > > > > Quick poll: What's your preferred mode? > > > > > > > > I prefer that the tab bar goes away when there's only one tab. > > > > > > > > I will feel surprise if anyone wants to have it visible when > > > > there's only one tab. > > > > > > The patch "almost" works, but sometimes when resizing the > > > window, strange resize problems arise, and things go wild. I'm > > > glad I finally isolated and STRed a part of the problem: > > > > > > http://fltk.org/str.php?L2639+P0+S-2+C0+I0+E0+Q > > > > > > I hesitate to fight it much more before the resolution for > > > STR#2639 comes out. It's like herding cats: you can make them all > > > move, but not make them go where you want. > > > > I'm currently working on a fix for the dwm resize issue. The idea is > > to get rid of Fl_Pack entirely. > > Well, that's the way to go if Fl_Pack is not fixed in FLTK-1.3. > > Although I hope Fl_Pack is fixed, because things become much > simpler with it. I actually prefer not to use Fl_Pack, as it relayouts on every redraw which feels a bit like a hack. Please test attached patch. In my opinion it simplifies things and also fixes the dwm resize issues I was seeing. Cheers, Johannes

May 25, 2011

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

by jcid＠dillo.org

On Wed, May 25, 2011 at 08:41:35PM +0200, Johannes Hofmann wrote: > On Wed, May 25, 2011 at 01:37:26PM -0400, Jorge Arellano Cid wrote: > > On Wed, May 25, 2011 at 03:13:54PM +0000, corvid wrote: > > > Jorge wrote: > > > > On Sun, May 15, 2011 at 09:04:43PM +0200, Johannes Hofmann wrote: > > > > > > > > > > - There is a tab title even if there is only one tab. > > > > > > > > FYI, I'm testing a patch that does this. It uses a trick to > > > > receive events on a hidden tabbar and is designed so it's easy to > > > > set permanent tab buttons too (i.e. as now). > > > > > > > > Quick poll: What's your preferred mode? > > > > > > I prefer that the tab bar goes away when there's only one tab. > > > > > > I will feel surprise if anyone wants to have it visible when > > > there's only one tab. > > > > The patch "almost" works, but sometimes when resizing the > > window, strange resize problems arise, and things go wild. I'm > > glad I finally isolated and STRed a part of the problem: > > > > http://fltk.org/str.php?L2639+P0+S-2+C0+I0+E0+Q > > > > I hesitate to fight it much more before the resolution for > > STR#2639 comes out. It's like herding cats: you can make them all > > move, but not make them go where you want. > > I'm currently working on a fix for the dwm resize issue. The idea is > to get rid of Fl_Pack entirely. Well, that's the way to go if Fl_Pack is not fixed in FLTK-1.3. Although I hope Fl_Pack is fixed, because things become much simpler with it. > So that patch might also fix the issue > you are now seeing with tabs and resizing. I'm trying a different approach now, and so far it works! :-o -- Cheers Jorge.-

May 25, 2011

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

by Johannes.Hofmann＠gmx.de

On Wed, May 25, 2011 at 01:37:26PM -0400, Jorge Arellano Cid wrote: > On Wed, May 25, 2011 at 03:13:54PM +0000, corvid wrote: > > Jorge wrote: > > > On Sun, May 15, 2011 at 09:04:43PM +0200, Johannes Hofmann wrote: > > > > > > > > - There is a tab title even if there is only one tab. > > > > > > FYI, I'm testing a patch that does this. It uses a trick to > > > receive events on a hidden tabbar and is designed so it's easy to > > > set permanent tab buttons too (i.e. as now). > > > > > > Quick poll: What's your preferred mode? > > > > I prefer that the tab bar goes away when there's only one tab. > > > > I will feel surprise if anyone wants to have it visible when > > there's only one tab. > > The patch "almost" works, but sometimes when resizing the > window, strange resize problems arise, and things go wild. I'm > glad I finally isolated and STRed a part of the problem: > > http://fltk.org/str.php?L2639+P0+S-2+C0+I0+E0+Q > > I hesitate to fight it much more before the resolution for > STR#2639 comes out. It's like herding cats: you can make them all > move, but not make them go where you want. I'm currently working on a fix for the dwm resize issue. The idea is to get rid of Fl_Pack entirely. So that patch might also fix the issue you are now seeing with tabs and resizing. Cheers, Johannes

May 25, 2011

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

by jcid＠dillo.org

On Wed, May 25, 2011 at 03:13:54PM +0000, corvid wrote: > Jorge wrote: > > On Sun, May 15, 2011 at 09:04:43PM +0200, Johannes Hofmann wrote: > > > > > > - There is a tab title even if there is only one tab. > > > > FYI, I'm testing a patch that does this. It uses a trick to > > receive events on a hidden tabbar and is designed so it's easy to > > set permanent tab buttons too (i.e. as now). > > > > Quick poll: What's your preferred mode? > > I prefer that the tab bar goes away when there's only one tab. > > I will feel surprise if anyone wants to have it visible when > there's only one tab. The patch "almost" works, but sometimes when resizing the window, strange resize problems arise, and things go wild. I'm glad I finally isolated and STRed a part of the problem: http://fltk.org/str.php?L2639+P0+S-2+C0+I0+E0+Q I hesitate to fight it much more before the resolution for STR#2639 comes out. It's like herding cats: you can make them all move, but not make them go where you want. -- Cheers Jorge.-

May 25, 2011

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

by corvid＠lavabit.com

Jorge wrote: > On Sun, May 15, 2011 at 09:04:43PM +0200, Johannes Hofmann wrote: > > > > - There is a tab title even if there is only one tab. > > FYI, I'm testing a patch that does this. It uses a trick to > receive events on a hidden tabbar and is designed so it's easy to > set permanent tab buttons too (i.e. as now). > > Quick poll: What's your preferred mode? I prefer that the tab bar goes away when there's only one tab. I will feel surprise if anyone wants to have it visible when there's only one tab.

May 25, 2011