- Dillo-dev - lists.mailman3.com

Invitation to connect on LinkedIn
by sdliyong＠gmail.com June 2, 2011

June 2, 2011

LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - Yong Yong Li platform software engineer at Hewlett-Packard China Confirm that you know Yong Li https://www.linkedin.com/e/m1sm8i-gofifhm7-1e/isd/2018522004/2K69vPKA/ -- (c) 2011, LinkedIn Corporation

1 0

Connection problems on Mac OS X 10.6.7
by jcid＠dillo.org June 2, 2011

June 2, 2011

On Wed, Jun 01, 2011 at 03:47:32PM +0000, corvid wrote: > > How do you think that bug eluded detection for so many years? > I was very surprised by it all... I) Very special conditions are necessary to trigger the bug, so the code works for most cases, hiding the bug (e.g. the test case in fltk works). It is a race condition where you need: - Multiple file descriptors being watched. - Some of them being closed while others remain in activity. - The closing being in such a way that the fd with the higher number is closed before the others. and on top of it there's also a semantic problem, which is very hard to spot while reviewing the code: [in remove_fd():] ... if (n == _maxfd) _maxfd--; ... It looks quite correct, but a callback may be pending in the queue, and if so, it will not be honoured. -- Cheers Jorge.-

2 1

Connection problems on Mac OS X 10.6.7
by rf.opensource＠gmail.com June 1, 2011

June 1, 2011

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

6 41

A chronology of discussions on floating elements support
by rf.opensource＠gmail.com June 1, 2011

June 1, 2011

A chronology of discussions on floating elements support, (or the floating element blues!) IMHO the number one missing feature of Dillo now is support for floating elements, which makes the rendering of majority of web sites unappealing / unreadable. So I became curious to see what sort of discussions has been going on in the past regarding this issue. It appears that this has been a goal for some time, at least as far back as 2004. Interestingly no one mentioned it in between 2004 and 2008, but from 2008 there has been interest in it again. Here's a little chronology I've put together from the discussions on the mailing list. I hope it raises interest in the community to finally address this feature. Oct 1, 2004 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-October/002218.html Jorge mentions that bug#598 is because Dillo doesn't support floating elements. I couldn't find bug#598 in the bugtracker page. Nov 6, 2004 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2004-November/002414.html<http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-May/006415.html> Jorge makes a priority task list of remaining issues. (This is before porting to FLTK2.) Based on this list support for floating objects should be added to DwPage. There Jorge claims "This is a bit difficult, since I'm not yet able to estimate the work." April 20, 2008 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-April/004101.html Jorge: "Planning for CSS, floating objects and TABS.(these are important features to a nice browsing experience)". Later Enrico mentions that he plans to write a universal but small CSS parser as a separate library to fix the missing CSS issue. Jorge suggests he look at RCSS by Raph Levien. July 3, 2008 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-July/004652.html As part of future of dillo2, Jorge: "In the near future, I'd like to have CSS and proper floating text rendering (DIV element), plus an API as a help browser." Nobody follows it up in that thread. Oct 22, 2008 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-October/005274.html Johannes proposes a plan to support CSS, and in parallel to make floating objects work in dw/textblocks.cc. Jorge mentions in reply that "currently I don't know which of these two is more urgent: * floats in textblock, * DIV element. I'd say DIV." Nov 7, 2008 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-November/005381.html Jorge mentions that Sebastian is apparently working on floating objects support. Jan 5, 2009 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-January/005608.html Jorge: "BTW, after we merge CSS into the main branch, it seems like floating objects will be the highest priority. Dillo rendering would improve a lot by using both!" Mar 4, 2009 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-March/006122.html Jorge mentions as a future goal: "Improve rendering: especially floating objects and the already good-looking CSS." May 10, 2009 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-May/006415.html Some discussion (with no clear conclusion) on "treatment of white spaces inside text blocks" between corvid, Jorge and Johannes. Jorge mentions that it will need changes to the textblock and that it is a task for dillo 2.2. Corvid hopes Johannes fixes it, Johannes hopes someone else fixes it, and Jorge mentions that Sebastian wanted to fix it but there's no news of him and apparently he has to tackle it himself. Jorge: "I remember doing this with table rendering algorithms, and it took months, but the end result was worth the effort. If somebody here wants to help along the way, it'd be more than welcomed." June 23, 2009 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-June/006645.html Jorge: "The column layout problem is mainly a lack of implementation of floating elements in the textblock. it is one of the top priorities for the next release (if not the topmost). We'll work on it and try to fix it. We're yet to find out how much work it will be." Oct 14, 2009 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-October/006918.html Jorge: "Right now, I see these ones very close: 1.Rendering of floating objects.(very visible for users)" Dec 11, 2009 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2009-December/007077.html TIm and Johannes give it s shot, but the issue remains unfixed. Johannes: "The real problem is what to do with those values. We need a way to render floating elements in dw/*" Oct 13, 2010 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2010-October/007760.html Jorge mentions: "Personally I believe the collapsing model and its baroque combinations are seldom used in the Web. Most sites are structured around floating DIVs these days,and even the last SPEC more or less recognizes the problem." Jan 26, 2011 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-January/008022.html Benjamin Johnson: "- Twelve years and three toolkits later, there's still no support for such basic functionality as floating elements (HTML "align=" or CSS "float:")." May 26, 2011 http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-May/008352.html Jorge mentions: "Dillo doesn't have support for "floating elements" yet. The web has become full of them because of slow rendering of tables. Well, we're supposed to work on it in the near future. For the meanwhile, you'll see weird "unrolled" pages."

1 0

Two bugs in the Dillo GUI (both Mac and ubuntu)
by rf.opensource＠gmail.com June 1, 2011

June 1, 2011

I've found a few obvious bugs in the current dillo_port1.3. They first two are present both in Linux (ubuntu 10.4) and Mac OS X (10.6.7). 1. There is no shortcut icon, the system uses a generic "exec" icon instead. 2. The X icon on the tab bar is missing, so the only way to close a tab is to press ctrl+w. 3. This might be a bug in the Linux version, albeit a minor one. When opening www.slashdot.org, Dillo in ubuntu uses a light brown background color. In the Mac version a grey background color is used. As reference, chrome uses grey too. 4. This one is more of a feature request. Like most Mac applications, the shortcuts should work with Command key instead of control key. (I know it's low priority, and I might give it a shot myself later on). General note: I think dillo (FLTK in general?) renders better / more beautifully in Mac than Ubuntu. The fonts are less jaggy (It seems the linux version is not using vector fonts at all?), and I can scroll both horizontally and vertically using touchpad gestures on Mac, while only vertical scrolling works in dillo under Linux. And at least for slashdot.orgthe colors are rendered more faithfully. P.S. I guess now we can officially claim in the dillo website that dillo 1.3 is fully compatible with Mac OS X 10.6. I'll get my hands on a 10.5.8 machine next week and will try it there too. -Reza

3 2

Connection problems on Mac OS X 10.6.7
by rf.opensource＠gmail.com May 28, 2011

May 28, 2011

On Fri, May 27, 2011 at 4:57 PM, Benjamin Johnson <obeythepenguin(a)gmail.com>wrote: > On Fri, 27 May 2011 17:22:47 -0400, reza farivar <rf.opensource(a)gmail.com> > wrote: > > Thanks Benjamin. I suggest we wait for a day or two before committing to >> back-porting. As Jorge mentioned, it might not be related to the sockets >> after all, in which case it might be fixed with his small patch. I also >> like >> to see what Manolo has to say on the issue, he seems to be quite active >> these days (lots of patches committed to FLTK1.3 in the last month). >> > > Well, for what it's worth, there were actually two different things on > Windows. First sockets didn't work at all, because of a broken select > implementation, then it had 100% CPU usage because it didn't check if FLTK > was idling. I sent in a patch for both and never heard back, though then > again no one's really maintaining 2.x any more. > Well if sockets didn't work at all on win32 you couldn't get any network traffic, right? So you probably had to fix the socket code anyway. Here, I do have network traffic, it just seems it needs a push to get stuff working. Maybe the event queue has to have more than one element to return something? I'm confused. By the way, unfortunately Jorge's patch (setting timeout to something other than 0.0) didn't solve the problem. So I'm running out of ideas, unless Manolo comes to rescue ;-) > Anyway, good luck, and hope you get a response! :-) > > ~Benjamin >

1 0

1.3 port
by jcid＠dillo.org May 27, 2011

May 27, 2011

Hi there, FWIW, I've been using the 1.3 branch for months now with no problems (i.e. as stable as 2.0). It's more or less 99% done, with some new features (as improved tabs). ! :-) ! The 1% remaining is the ability to switch panel sizes on-the-fly, which could take me 1 day of work aprox. I'd like to get your feedback on this browser because it will sooner than later become the official branch. Comments? -- Cheers Jorge.-

10 85

dillo_port1.3: ctrl-q randomly kills dillo and all tabs
by rogerx.oss＠gmail.com May 19, 2011

May 19, 2011

I took a snapshot of dillo_port1.3 a week or so ago and have been finding on CTRL+Q randomly acts like ALT+Q (or kills the Dillo session with all open tabs). One way I've been able to reproduce this, loading several websites and letting them to load completely and then do CTRL+Q. (This bug doesn't present itself on simpler web pages such as google.com or a simple weather forecasting website. Need something with some junk in it. :-/)

4 10

fltk getting close to 1.3.0 release
by corvid＠lavabit.com May 19, 2011

May 19, 2011

Seen in http://fltk.org/newsgroups.php?s11135+gfltk.development+v11151+T0 "1.3.0 will go final Sunday unless there is a major show-stopper."

1 0

dillo_port1.3 - dpid not starting
by rogerx.oss＠gmail.com May 19, 2011

May 19, 2011

Anybody else seeing this with dillo port 1.3? I'm seeing this after I completely uninstalled dillo-1 & dillo-2 from my system, leaving only dillo_port1.3 installed. $ install/bin/dillo dillo_dns_init: Here we go! (threaded) Enabling cookies as from cookiesrc... Nav_open_url: new url='dpi:/bm/' Dpi_get_server_port: can't read server port from dpid. ** ERROR **: dpi.c: can't start dpi daemon -- Roger http://rogerx.freeshell.org/

3 10