- Dillo-dev - lists.mailman3.com

FLTK 1.3 and current development version
by mailbox＠georgpotthast.de June 28, 2011

June 28, 2011

An HTML attachment was scrubbed... URL: /pipermail/attachments/20110628/c474985d/attachment.html

2 1

can't bind action to backslash
by corvid＠lavabit.com June 27, 2011

June 27, 2011

Alexander discovered that binding an action to backslash does not work. I was thinking that the line-continuation code in dGetline came from Tim's work on the parser, but it appears to have been there since the dawn of dillo2. I personally would be tempted to remove the special code for '\' because I'd be surprised if we keep this possibility in mind every time that we use dGetline() somewhere -- and I don't believe it's documented anywhere. But if there's resistance to that, then there are also the options of 1) Making it a line continuation character only if everything following it is whitespace. 2) A special key name for backslash.

1 0

Rearrange link menu
by Hole.destructor＠gmx.de June 25, 2011

June 25, 2011

Dear Dillo Developers, I would like to propose a small change in Dillo's link menu (the menu which pops up when you right click on a link), which I think would increase the usability a bit. The current link menu shows as first item "Open link in new window", and as the second item "Open link in new tab". I think it would be more convenient for the user to have these two interchanged, because It seems that the users use tabs more than multiple browser windows. What do you think? Kind regards, Alexander

3 2

Mouse buttons in keysrc
by Hole.destructor＠gmx.de June 25, 2011

June 25, 2011

Dear Dillo developers, I noticed that the key configuration via keysrc does not recognize mouse keys. So I am wondering whether anybody already thought about adding mouse keys? I think for many users something like <shift>mouse1 = new-tab mouse9 = forward mouse8 = back in keysrc would be very convenient. (This would probably make the options middle_click_opens_new_tab and middle_click_drags_page in dillorc obsolete.) Kind regards, Alexander

3 5

Quit Button Window Size fixed with latest fltk-1.3.0 release
by rogerx.oss＠gmail.com June 24, 2011

June 24, 2011

It appears the latest release of fltk-1.3.0 fixed a problem I was seeing with the quit window size for Dillo-port-1.3.0 being full size within the DWM (window manager). (Either that, or a patch within dillo-port-1.3 fixed it, but it doesn't appear so because I don't think I've pulled Dillo-port-1.3.0 dev sources for awhile here, except for the recent fltk-1.3.0 release upgrade.) Cheers! -- Roger http://rogerx.freeshell.org/

2 1

printer symbols in dillo
by corvid＠lavabit.com June 20, 2011

June 20, 2011

I put dillo through nm, and I saw a bunch of Fl_Paged_Device, Fl_PostScript_Printer, T Fl_PostScript_File_Device in there. I didn't pay any attention when they were all enthusiastic about printer support for a while there. Is there a justifiable reason that this gets pulled in, as opposed to an oversight on their part when #ifdef'ing or something?

4 7

Time to celebrate!
by jcid＠dillo.org June 17, 2011

June 17, 2011

Hi, This means a lot to us: http://fltk.org/articles.php?L1086 !! :-) !! -- Cheers Jorge.-

3 2

Development schedule for version 1.3
by rf.opensource＠gmail.com June 15, 2011

June 15, 2011

Hi guys, It seems that FLTK will release their final 1.3 version next week on June 8th. Are we waiting on that to release our own dillo 1.3? The reason I'm asking is that as you know I'm preparing an installable Mac OS package, which I hope to go on dillo's download page (and hopefully introduce dillo to many non-developer users). So I'd like to know if we are just waiting on that final release of FLTK 1.3, or whether there are still open bugs remaining for our next release? Thanks, Reza

7 23

Update on segfault issues
by mr_semantics＠hotmail.com June 11, 2011

June 11, 2011

I have been playing around with the 1.3 port on my "broken" machine. Still no luck with sorting out the segfault. I have spent a fair amount of time in gdb and valgrind trying to track down the source of the trouble, but no luck. The best I can do when compiling with gcc is to use -O0, which produces an executable which does not segfault. I have tried gcc 4.4, 4.5, and 4.6, to no avail. I have wondered if it was something to do with my architecture; I am running an AMD E-350 fusion processor in my machine. In light of this, I tried using the appropriate -march setting with gcc 4.6, but again no luck. The only bright side of all of this was that I decided to compile with Clang, and it built nicely with only one warning (which I could not see the reason for): chain.c:189:50: warning: too many arguments in call to 'Chain_debug_msg' Chain_debug_msg(FuncStr, Op, Branch, Dir, Info); ~~~~~~~~~~~~~~~ ^ I will keep playing with this, to see if I can figure out the problem with gcc, but my hope is fading with regards to finding a solution. Rob

3 2

Table::addCell() leak
by corvid＠lavabit.com June 9, 2011

June 9, 2011

http://starurchin.org/dillo/valgrind/10ca58f617a0693638facdb40bcf319af1bdfc… has a leak at dw/table.cc:323, and I found a way to trigger it: <table border=2> <tr><td>first<td rowspan=2>tall<td>third <tr><td colspan=2>wide<td>last </table> Jorge, you might remember a little something about tables. Can we simply check children->get() before putting anything there, or do we have to fix things somewhere if part of a span is stolen away?

2 1