- Dillo-dev - lists.mailman3.com

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

triggering buttons with the keyboard
by corvid＠lavabit.com May 18, 2011

May 18, 2011

In fltk2, Button.cxx had case KEY: if (event_key() == ' ' || event_key() == ReturnKey || event_key() == KeypadEnter) goto EXECUTE; In fltk 1.3, Fl_Button.cxx has if (Fl::focus() == this && Fl::event_key() == ' ' && !(Fl::event_state() & (FL_SHIFT | FL_CTRL | FL_ALT | FL_META))) { ... if (when() & FL_WHEN_RELEASE) do_callback(); Our fltkui button widget callbacks check for FL_Enter/ReturnKey before emitting clicked. A couple of months ago, I had some confusion with the fltk people where I expected Enter to trigger something, but ' ' was doing it. My recollection was that they seemed to think one should expect ' ' to be what triggers actions. Is ' ' some sort of standard in the gui world nowadays?

1 0

configure.in -Wno-unused-parameter
by corvid＠lavabit.com May 16, 2011

May 16, 2011

if eval "test x$GCC = xyes"; then .. if test "`echo $CFLAGS | grep '\-W[^a]' 2> /dev/null`" = ""; then if test "`$CC -v 2>&1 | grep 'version 3'`" != ""; then CFLAGS="$CFLAGS -W -Wno-unused-parameter" fi fi .. fi It checks for 3.x specifically. 3.0 came out on June 18, 2001. And of course 4.x has been out since...let's see...April 20, 2005. 2.95 was still apparently around back in http://lists.auriga.wearlab.de/pipermail/dillo-dev/2003-December/001565.html , which prompted this code at the time. Can I rip out the version-checking and make it into an ordinary case of adding the argument if it isn't already in CFLAGS?

3 7

next release of dillo?
by itsme_410＠yahoo.com May 15, 2011

May 15, 2011

hi, just wondering when the next release of dillo will be, i.e. if there is a planned timeline? we appear to be at dillo2.2 for a while now? thanks again for a great browser which fulfils my needs for many purposes.... t

2 3

What's currently broken in... (Re: [Dillo-dev] 1.3 port)
by johannes.hofmann＠gmx.de May 12, 2011

May 12, 2011

Xembed works for me now (tested with tabbed) Cheers, Johannes corvid <corvid(a)lavabit.com> schrieb: > >- xembed >- the preferred font code in dillo.cc. >- The test/ programs have UI problems (scrollbars, PgUp, etc.). >- drawing with nested layouts >- tab titles >- scrollbar sometimes thinks the page is slightly larger than it is. >- When scrolling with the keyboard, with buffered_drawing 0 or 1, > tooltips leave grey boxes. > > > >_______________________________________________ >Dillo-dev mailing list >Dillo-dev(a)dillo.org >http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

1 0