- Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] patches

by Livio Baldini Soares

Hey folks! Phillip Warner writes: > On Wed, 19 Feb 2003 17:15:33 +0100 > Nicola Girardi <nicola(a)g-n-u.de> wrote: > > > > > > <alt>-w closes the window (instead of <ctrl>-q) > > > > > > > > Why isn't this C-w as in most GTK applications? In most GTK > > > > apps(well all the apps I've ever used) I see C-w means close > > > > window and C-q means close all windows and exit. [...] > I did not take it as a direct complaint. :^) I think this is a very > relevant question (and thread) as well, and worthy of a short > discussion. However, I shall not lead it, as I do not know the > initial reasons why these default keybindings were chosen. > > I thought I would give you my reasons for choosing what I did, which > could open the discussion further. In my very humble opinion what needs to be discussed is a way for everyone to be pleased with whatever key bindings Dillo is setup with. How? I think we should have a "default" set of key bindings, which may or may not please everyone, _but_, more importantly, add the possibly of specifying alternate ones in the dillorc file. The code shouldn't be too hard to do, but perhaps a tad bit tedious. The options might look like: key_close_window=C-w key_quit=C-q key_back=backspace key_forward=F8 Discussions on key bindings keep reappearing on this list, which leads me to think that a more general solution like the one I've proposed is needed. Unfortunately, my hacking time has been cut down drastically. If someone wants to implement this, I'll be gald to help out. best regards, -- Livio <livio(a)ime.usp.br>

Feb. 19, 2003

Re: [Dillo-dev] patches

by Phillip Warner

On Wed, 19 Feb 2003 17:15:33 +0100 Nicola Girardi <nicola(a)g-n-u.de> wrote: > > > > <alt>-w closes the window (instead of <ctrl>-q) > > > > > > Why isn't this C-w as in most GTK applications? In most GTK > > > apps(well all the apps I've ever used) I see C-w means close > > > window and C-q means close all windows and exit. > > > > > > > I, for one, do not know. > > Oh, I didn't mean to complain to you directly--I just chose an > appropriate thread for the issue. :) > I did not take it as a direct complaint. :^) I think this is a very relevant question (and thread) as well, and worthy of a short discussion. However, I shall not lead it, as I do not know the initial reasons why these default keybindings were chosen. I thought I would give you my reasons for choosing what I did, which could open the discussion further. Cheers, --Phil ------------------------------ Don't ever slam a door; you might want to go back.

Feb. 19, 2003

Re: [Dillo-dev] patches

by Nicola Girardi

> > > <alt>-w closes the window (instead of <ctrl>-q) > > > > Why isn't this C-w as in most GTK applications? In most GTK apps > > (well all the apps I've ever used) I see C-w means close window and > > C-q means close all windows and exit. > > > > I, for one, do not know. Oh, I didn't mean to complain to you directly--I just chose an appropriate thread for the issue. :)

Feb. 19, 2003

Re: [Dillo-dev] patches

by Phillip Warner

On Wed, 19 Feb 2003 15:03:25 +0100 Nicola Girardi <nicola(a)g-n-u.de> wrote: > > <alt>-w closes the window (instead of <ctrl>-q) > > Why isn't this C-w as in most GTK applications? In most GTK apps > (well all the apps I've ever used) I see C-w means close window and > C-q means close all windows and exit. > I, for one, do not know. I chose alt for my patch because that is what I am used to (Netscape). IMO, alt is certainly easier on a laptop. Cheers, --Phil

Feb. 19, 2003

Re: [Dillo-dev] patches

by Nicola Girardi

> <alt>-w closes the window (instead of <ctrl>-q) Why isn't this C-w as in most GTK applications? In most GTK apps (well all the apps I've ever used) I see C-w means close window and C-q means close all windows and exit.

Feb. 19, 2003

Is this the right mailng list?

by William Trenker

I notice I am getting messages from this list (dillo-dev(a)lists.auriga.wearlab.de) and from dillo-dev(a)auriga.wearlab.de. Which list should I use for general questions about Dillo? By the way, Dillo 0.7.0 is great! It's a perfect companion for browsing html-mail with my email client, Sylpheed. Regards, Bill

Feb. 19, 2003

patches

by Phillip Warner

Hi, I'm typically a lurker, but I thought I would release a few modifications I made to dillo. My patch also includes someone's (I can't recall whose) patch that adds external downloading and opening in external browsers. I thought someone may be interested. Here are the modifications I made: <alt>-w closes the window (instead of <ctrl>-q) <alt>-b in viewport opens a new window with the bookmarks <alt>-u view source <ctrl>-r in viewport reloads the current page (bookmark button loads bookmarks in current viewport <ctrl>-h loads homepage vi-style scroll (h = left, j = down, k = up, l = right) <esc> button stops loading the current page (this has no effect on images--they still load if page is fully loaded) The patchfile can be found at: http://www.xmission.com/~locutus/various-locutus.patch and the modifications above can be seen at: http://www.xmission.com/~locutus/index.html#dillo If you find this useful, enjoy! Boa, --Phil

Feb. 19, 2003

dillo-0.7.0 release

by Daniel Pfurtscheller

Works great on my system: Slackware Current (9.0 Beta) and gcc version 3.2.1. Keep up the good work! pfu -- "Contrariwise," continued Tweedledee, "if it was so, it might be, and if it were so, it would be; but as it isn't, it ain't. That's logic!" -- Lewis Carroll

Feb. 18, 2003

dillo 0.7

by Richard A Downing

Best yet. Compiled and rinning fine with LinuxFromScratch V4 using gcc3.2.2 and glibc3.2.1. Jorge, Many thanks! -- Cheers, Richard Richard A Downing FBCS

Feb. 18, 2003

Re: [Dillo-dev] bug tracking engine

by Joe Crayne

On Sun, Feb 16, 2003 at 10:45:49PM +0100, Sebastian Geerken wrote: > > I've been thinking about it (and hacking on dw_page.c) and > > have a partial implementation. It involved adding a pointer > > line->last_float_line which points to the last line that has > > a floater hanging down in the margin of the current line. > > Dw_page_draw_line() traces that pointer and draws that line > > too (and hence also its last_float_line and so on). > > Dw_page_draw_line (which is called by Dw_page_draw, the > implementation of DwWidget::draw) just does the actual drawing > (putting the pixels on the screen), and since you cannot > predict that it is called for all lines (normally it will be > called for those lines seen in the viewport), it should not > change the state of a DwPage. It doesn't. Dw_page_draw_line() traces the pointer and causes possibly other lines to be drawn other than the one it is called for. > - Floats may exceed the allocation of the DwPage, so they may not be > a child widget, instead, an interaction between two DwPage's is > necessary. When does a float exceed the allocation of the DwPage? Is there a new DwPage for new paragarphs? > - Since a float may be defined at a point, where there is > already a float at the respective side, you do not only need > one pointer, but rather a list or a tree, depending on how the > second float is positioned (below or left/right, both is > allowed by the CSS2 spec, but from what I've thought about it, > I believe that the second variant is simpler to implement). How about this: Floats are drawn in sequence just as other words on the line. Nothing special, except that now, line->ascent and line->descent doesnt count floats. Consequently, if the portion of the screen being refreshed doesn't yeild the DwPageLine where the float occurs, then that float wont get properly refreshed. The pointer points to the lowest (highest index) line containing a float that hangs down low enough that it may need to be refreshed also. (Note that if there's another float, then it will be either on the same line or refered back to by the pointer for the float line so that all the floats in the margin get refreshed.) Thanks.

Feb. 18, 2003