October 2003 - Dillo-dev - lists.mailman3.com

Re: [Dillo-dev] [PATCH] version 11 of tab/frame patch, added keyboard navigation

by johannes leimbach

Hi! You're patch works fine, thanks for the good work. One (minor) bug though: It seems to mess up the tab order of the elements. Take for example an online forum (phpbb). Go to "Login", so you must enter an username+password. Before the patch (in 0.7.3) i could set the focus from textbox 2 textbox with TAB, now it "jump" to a (for me) random element. Would be nice if you could check this out. Cheers, johannes :)

Oct. 15, 2003

Re: [Dillo-dev] Development

by Jorge Arellano Cid

On Mon, 13 Oct 2003, Carlos Daniel Ruvalcaba Valenzuela wrote: > Hi everyone > > It sems i lost a lot of the development cycle, now even plugins > are implemented! > > Anyways, here is my wasted effort with dillo-0.7.3: > > [...] > What a shame you've missed the large work being done on dpid :( > Any comments?, anyone wants the patches? Certainly your expertise can be reused. Do you have some more time? For instance, there's a guy working on the Gtk+ interface to the downloads plugin. You could work together. Preferences is another interesting area... Cheers Jorge.-

Oct. 15, 2003

Re: [Dillo-dev] Problem: Dillo not rendering /. correctly

by Victor Sahlstedt

On Wed, 15 Oct 2003 16:36:17 +0200 johannes leimbach <johannes.leimbach(a)gmx.de> wrote: > Do you have any ideas what might cause this visual annoyance? http://validator.w3.org/check?uri=www.slashdot.org Maybe the 348 errors has something to do with it.. - Victor

Oct. 15, 2003

A short potpourri

by Eythan Weg

Hi, I have read that people use dillo to read documents, long documents, and perhaps whole books, or chapters... In such cases there comes a time when a use of a dictionary is a must. Is it possible to have a dpi that will allow for the running of any shell command on a highlighted portion of the screen? In this example running a dictionary on a word? The output of the command would go into a new tab, or window or split of the current window, horizontally or vertically, depending on the key-binding. On another vein, I have two problems with version 8-pre of about two weeks ago patched with the tab-frame feature (I compiled yesterday's version with the new patch, but could not figure how to start the dpis... can someone tell how in some more details, please?) The first is over-tabbing. For example browsing http://mail.gnome.org/archives/gnomemeeting-list/ choose any thread and it opens on a new tab. Read any post and again it opens in a new tab. The second is that copy and/or paste do not work reliably. I am not sure this is dillo's issue though. Sincerely, eythan

Oct. 15, 2003

Fw: Slashdot's HTML fix (fwd)

by Jorge Arellano Cid

Hi, Here I quote the email Andreas sent to Rob Malda with regard to Slashdot's HTML (rendering problems). We haven't got an answer, so if you can contact Rob, please do so. I have tried. Currently also with gnu-darwin's maintainer we're trying to contact Slashdot's webmasters with a view to fix it. The problem is that we don't have anything but the generic email address, and surely it collects tons of emails. :( Please, if someone in this list has an inner track to /.'s webmasters, please help us to deliver this email. Cheers Jorge.- ---------------------------------------------------------------- Begin forwarded message: Date: Mon, 29 Sep 2003 17:07:31 +0200 From: Andreas Kemnade <akemnade(a)informatik.uni-bremen.de> To: malda(a)slashdot.org Subject: Slashdot's HTML fix Hello Rob, I (and many others) have some problems reading http://slashdot.org/ with dillo (http://www.dillo.org) It was ok for years but since some weeks the page is almost completely unreadable. Screenshot: http://users.auriga.wearlab.de/~andi/slash2.png Seeing so much black is really depressing ;-) tidy (a html cleanup program from the w3c) shows lots of warnings. But after tidy has cleaned up the html, dillo shows it almost correctly. After some more investigation, I have found the error which makes the page black:  <A HREF="//science.slashdot.org">Science</A>   3 more</TD></TR> <TR><TD >  <A HREF="//yro.slashdot.org">YRO</A></TD></TR> </TD></TR> ^^^^^^^^^^ There has to be only one </td></tr> pair. So it has to be this way:  <A HREF="//science.slashdot.org">Science</A>   3 more</TD></TR> <TR><TD >  <A HREF="//yro.slashdot.org">YRO</A></TD></TR>  without the extra </td></tr>. I guess after removing that table, you have forgotten the </td></tr>. Screenshot with that correction: http://users.auriga.wearlab.de/~andi/slash1.png It looks quite nice again. I hope you can easily find the html bug in the perl code. You'll make a lot of dillo users happy and the page a bit more W3C compiliant. Greetings Andreas Kemnade PS: Your site http://CmdrTaco.net/ also looks nice with dillo.

Oct. 15, 2003

Selection leak

by Jorge Arellano Cid

Hi there! Finally the selection riddle is clear: there were some GTK+ warnings very seldomly appearing sometimes, but not in 0.7.3. In 0.7.3 one of the popups was being set as the permanent owner for all the selections, and it was initialized at browser window creation time. As 0.7.3 leaked the popups (not destroying them with the window) the widget remained valid all the time! In CVS the popup leak is fixed, so the selection owner can be destroyed with its window, and thus the warnings. I fixed it like I originally suggested: > Perhaps it'd be better to add a widget parameter to > a_Commands_set_selection: > > void a_Commands_set_selection(GtkWidget *widget, gchar *str) > > So we can set the owner properly. AFAIU the owner gets the > "clear selection" event on the handler it set. For instance, when > the user selects text from the location bar, the "clear > selection" callback is called. This can help to set a custom > handler for when the selected text comes from the rendered area. > This new handler can toggle the selection highlighting off, and > then call a_Commands_clear_selection_callback() to finish the > work. Sebastian: I used "GTK_BIN(bw->docwin)->child" as the selection owner for the rendered area. Is there a better candidate? Commited! Cheers Jorge.-

Oct. 15, 2003

Problem: Dillo not rendering /. correctly

by johannes leimbach

Hi! I have a really strange problem with dillo 0.7.3 as well as with the most recent CVS checkout+tab/frames patch: Dillo does not render slashdot.com correctly.. in fact rendering is so bad i even have to load another browser (yuck!) to be able to read the stories. How does it look like then? (I'd love to send a screenshot, but I think I'm not allowed too?) The /. menu & links are displayed correctly, though there are no news. White background. Right of that, I have a black background, with what seems to be the captions of the news - with black font on black background not very useful. Even more right of that, I have the poll menu and the login stuff and so.. In short: Totally unusable for that page. Other (read: all other) pages are shown correctly. If I wouldn't know /. is supposed to be displayed correctly, I wouldn't ask.. but so... Do you have any ideas what might cause this visual annoyance? Thanks for your help :) Cheers, johannes

Oct. 15, 2003

Re: [Dillo-dev] Development

by Scorpio Rising

Behold, Carlos Daniel Ruvalcaba Valenzuela scribed in runic symbols on a tube chassis: > * ddm_srv.c Dillo Download Manager, a download plugin using wget, will be able to download multiple files and show their progress in dpi:/ddm/downloads Oy! Could I use this one :-)

Oct. 15, 2003

[PATCH] version 1 of keyboard navigation patch

by Frank de Lange

Hi'all, The first version (1) of my keyboard navigation patch is ready. See the end of this message for download instructions. Do note that the tab/frame patch already contains this functionality, so there is no need (and no way) to apply this patch on top of that or the other way around. The patch adds Keyboard navigation with configurable key bindings to (the CVS version of) Dillo. Please test it and let me know what you (don't) like. Even though keyboard navigation does not make much sense with devices without keyboards (pda's, etc), there is no configure option to disable it. Let me know if there is a need for such an option (it is easily implementable). Personally I think there is... For keyboard navigation to work Dillo has to track the position of individual words in a document, which increases memory overhead with 4 bytes per word. However, there seems to be some animosity against the added complexity of conditionally compiled code (enclosed in #ifdef ... #endif). More information on keyboard navigation can be found in the document "Keyboard_Navigation.txt" in the doc/ directory which I'll just reproduce it here: Keyboard Navigation =================== You can use the keyboard to navigate links and controls in Dillo. In the default configuration, the following keys are used: Alt-Up: link UP Alt-Down: link DOWN Alt-Left: link LEFT Alt-Right: link RIGHT Enter: follow link or activate GTK+ widget Escape: unhighlight link In a non-frames version of Dillo the following keys are also used: Tab: NEXT link Shift-Tab: PREVIOUS link these keys are not bound by default in a frames-capable version of Dillo because they are used to navigate between frames. You are free to bind them (or any other key combination) to these functions though (see Keyboard bindings) Sometimes the result of link UP and link DOWN seems a bit unpredictable. This can happen when the next UP or DOWN link is currently not visible (below the bottom or above the top of the window). The screen coordinates for words are only known when they are in the visible area of the viewport, so off-screen links are accessed sequentially instead. Search and keyboard navigation ------------------------------ Keyboard navigation works with the Search feature: if search hits a link, it will be focused. Press <Enter> in the viewport to follow the link, <Esc> to unhighlight it. When using the status bar for search (an optional feature in the tabbed version of Dillo), press <Esc> to close the search entry followed by <Enter> to follow the link. A second <Esc> will unhighlight the focused link. Pressing <Enter> in the search entry (popup or status bar) repeats the search. History ------- The focus location is saved when navigating to another document in the same window or tab. This makes it possible to go back in history and continue to the next link on the page. Form fields ----------- The same keys used for link navigation work for form field navigation. Do note however that form fields, being embedded GTK+ widgets, can have their own bindings for some functions. As an example, the space bar is bound to the activate function in radio buttons. Keyboard bindings ================= It is possible to change the keyboard bindings used for keyboard navigation, either through editing the dillorc or by adding a section to any of the current GTK+ rc-files. The syntax is the same, the only difference is the addition of the preference keyword "key_bindings" in the dillorc and the fact that the bindings have to be enclosed in double quotes. As an example, this configuration (in gtkrc) uses the numerical keypad for link navigation: binding "keypad-keys" { bind "KP_Add" { "focus_move" (0) } bind "KP_Subtract" { "focus_move" (1) } bind "KP_8" { "focus_move" (2) } bind "KP_2" { "focus_move" (3) } bind "KP_4" { "focus_move" (4) } bind "KP_6" { "focus_move" (5) } bind "KP_Enter" { "focus_activate" () } } class "GtkDwScrolledFrame" binding "keypad-keys" You can also use 'widget "*dillo-content" instead of 'class "GtkDwScrolledFrame" if you prefer to use widget names: widget "*dillo-content" binding "keypad-keys" This one (in dillorc, note the enclosing double quotes, the use of single quotes and the preference name 'key_bindings') makes Dillo behave like the vi editor when it comes to link navigation: key_bindings = "binding 'vi-keys' { bind 'k' { 'focus_move' (2) } bind 'j' { 'focus_move' (3) } bind 'h' { 'focus_move' (4) } bind 'l' { 'focus_move' (5) } } class 'GtkDwScrolledFrame' binding 'vi-keys'" The numerical values after "focus_move" are actually GTK enumeration values, but the current implementation does not support this. It would of course look much better to be able to write "focus_move" (GTK_DIR_DOWN) instead of "focus_move" (3)... It is also possible to bind a sequence of actions to a single keypress by adding more actions after the first. Bugz^Hs ======= - Image links without alt text do not work with keyboard navigation. - Image links with alt text work, but Dillo is currently not able to scroll to them. This can lead to 'hidden' focused links, use the scroll keys or scroll bars to bring them in to view. This problem is shared with the Search feature. It is caused by a deficiency in the widget iterator function which is used for scrolling. - The sometimes unpredictable behaviour of link UP/DOWN can be classified as a bug. Or not. It is probably hard to solve this. The root cause is the use of incremental display in dw_page, which is in itself a good feature. To good to mess it up with some hack to get each and every link in the right place before using keyboard navigation. TODO ==== Well, apart from fixing those bugs... Maybe merge focus with search, they have quite a lot in common. This would save some code and memory. It would also mess up the current design, so maybe this is not such a good idea. Add more GTK+ bindings, replacing current key_press event handling. ... Download instructions ===================== There is currently only one version of the patch, made against 20031014 CVS. Sorry, no 0.7.3 support (yet...). As always, have a look at the patch website (http://www.geocities.com/ikbenfrank/) for the latest version of the patch. This patch does NOT apply on top of the tab/frame patch, and the tab/frame patch does not apply on top of this one! The tab/frame patch already contains this functionality, so it is not needed. Also, there is some overlap in the patched files, so I'd have to create a special version of this patch for this purpose. http://www.geocities.com/ikbenfrank/dillo-200310142300-kbnav.patch.gz size: 14336 bytes (gzipped, as downloaded) 62481 bytes (uncompressed) md5sum: 06c21168960cc5de12437ab4abff6d45 (gzipped, as downloaded) a1317f63190ad0df9501bbb257f8c137 (uncompressed) Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ] -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / \ \ `--| _/ <Hacker for Hire> \ `---' \ +46-734352015 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]

Oct. 15, 2003

[PATCH] version 11 of tab/frame patch, added keyboard navigation

by Frank de Lange

Hi'all, The next version (11) of my tab patch is ready (see bottom of this message for download instructions). The big new features are keyboard navigation and configurable key bindings (currently only for keyboard navigation and scrolling, more will be added later). See below for more information on these features. Keyboard navigation is also available in a separate patch, for those who do not want to apply the tab/frame patch. Watch the mailing list and/or see the patch website (http://www.geocities.com/ikbenfrank/) for more information. New features: - keyboard navigation! - configurable key bindings (for keyboard navigation and scrolling) Fixed bugs - solved the 'missing frames' problem for German (and other?) users. Stephan Goetter pointed me in the right direction (the German locale uses the "," as a decimal separator). Some behavioural changes with regard to stock (CVS) Dillo: - Shift-Ctrl-L (instead of Ctrl-L) for "open URL" dialog - Ctrl-L for "focus location bar" - Ctrl-S for "Save page As..." - Ctrl-U for "view source" while in a document, "clear entry" everywhere else (in stock Dillo this key is bound to "focus location bar" while in a document) - Ctrl-B for "Bookmark this page" - Alt-H for "Home" - "/" starts incremental search instead of normal search. For normal (non-incremental) search use Ctrl-F Support for the 0.7.3 branch has been dropped as of this version of this patch. Sorry, folks, but that is the price you pay for progress... Currently, both tab and frame support can be turned off completely, producing a smaller binary. I might (on request of other Dillo developers) remove the conditional compilation, thereby making tab and frame support a permanent feature of Dillo. If you want to keep the conditional compilation feature, speak out on the mailing list! Keyboard navigation can currently NOT be turned off, let me know if this is needed. Frameset (and iframe) support is enabled by default, it can be disabled using the configure option --enable-xhtml-dtd=strict. You can also use --enable-xhtml-dtd=transitional, which will give you iframe but no frameset support. The default option, --enable-xhtml-dtd=frameset, gives both iframe and frameset support. As usual, tab support can be disabled using --disable-tabs. What does not work yet: - the full_screen_off_button is not shown in frame documents. Use double-click instead to toggle the full screen setting... - the frameborder attribute works, but dw_gtk_scrolled_frame always draws a (focus) shadow around itself - even with the border size is set to 0. This can be solved in several ways - adding a 'borderless' attribute to dw_gtk_scrolled_frame, using a special borderless GTK theme for the widget, etc. In GTK2 this is all much easier (just set the widget's style's xthickness/ythickness to 0), but we're not there yet... - borderless frames can not be resized, even though Dillo always shows a thin border (see above). Who cares about resizing borderless frames? Mozilla does it, but I don't think this is an issue. Agree? - iframes always have a border (see above) Keyboard Navigation =================== You can use the keyboard to navigate links and controls in Dillo. In the default configuration, the following keys are used: Alt-Up: link UP Alt-Down: link DOWN Alt-Left: link LEFT Alt-Right: link RIGHT Enter: follow link or activate GTK+ widget Escape: unhighlight link In a non-frames version of Dillo the following keys are also used: Tab: NEXT link Shift-Tab: PREVIOUS link these keys are not bound by default in a frames-capable version of Dillo because they are used to navigate between frames. You are free to bind them (or any other key combination) to these functions though (see Keyboard bindings) Sometimes the result of link UP and link DOWN seems a bit unpredictable. This can happen when the next UP or DOWN link is currently not visible (below the bottom or above the top of the window). The screen coordinates for words are only known when they are in the visible area of the viewport, so off-screen links are accessed sequentially instead. Search and keyboard navigation ------------------------------ Keyboard navigation works with the Search feature: if search hits a link, it will be focused. Press <Enter> in the viewport to follow the link, <Esc> to unhighlight it. When using the status bar for search (an optional feature in the tabbed version of Dillo), press <Esc> to close the search entry followed by <Enter> to follow the link. A second <Esc> will unhighlight the focused link. Pressing <Enter> in the search entry (popup or status bar) repeats the search. History ------- The focus location is saved when navigating to another document in the same window or tab. This makes it possible to go back in history and continue to the next link on the page. Form fields ----------- The same keys used for link navigation work for form field navigation. Do note however that form fields, being embedded GTK+ widgets, can have their own bindings for some functions. As an example, the space bar is bound to the activate function in radio buttons. Keyboard bindings ================= It is possible to change the keyboard bindings used for keyboard navigation, either through editing the dillorc or by adding a section to any of the current GTK+ rc-files. The syntax is the same, the only difference is the addition of the preference keyword "key_bindings" in the dillorc and the fact that the bindings have to be enclosed in double quotes. An example of the configuration syntax can be found in the dillorc and on the mailing list. Tabs, Frames, Keyboard navigation and browser bloat =================================================== version: 0.8.0-pre patch: dillo-20031015-tabs.patch.gz unpatched: 294132 bytes patched, no tabs, no frames: 308404 bytes patched, with tabs, no frames: 315220 bytes patched, no tabs, with frames: 324852 bytes patched, with tabs, with frames: 333108 bytes (gcc 3.2.2, binutils 2.13.90.0.18, CFLAGS "-Os") The increase in size is due to the addition of keyboard navigation. If you want to be able to compile Dillo without this feature (it takes about 10 KB) let me know through the mailing list. Download instructions ===================== The patch is made against 20031014 CVS. Do not forget to run ./autogen.sh after applying the patch. You can find the patch on the usual (ad-happy, use an ad-blocking proxy or sane browser) site: http://www.geocities.com/ikbenfrank/ More specifically: Dillo 0.8.0-pre (CVS) ===================== http://www.geocities.com/ikbenfrank/dillo-20031015-tabs.patch.gz size: 85716 bytes (gzipped, as downloaded) 371416 bytes (uncompressed) md5sum: 358041a00feeef1706b81d24a985613a (gzipped, as downloaded) bf61b1bdb212c69c30ee1fa6fa74f729 (uncompressed) As always, check the site for the most recent version Cheers//Frank -- WWWWW ________________________ ## o o\ / Frank de Lange \ }# \| / +46-734352015 \ \ `--| _/ <Hacker for Hire> \ `---' \ +31-640037120 / \ frank(a)unternet.org / `------------------------' [ "Omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est." ]

Oct. 15, 2003