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

[PATCH] Version 4 of kbnav patch is ready

by Frank de Lange

Hi'all, The next version (4) 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. This release does not add many new features. It does however fix most known bugs, which is a good enough reason for applying it I'd say... One new feature is that is is now possible to popup context menus with keyboard navigation. The default key binding is Alt-Enter (and Alt-KP_Enter), this can of course be changed using the appropriate preference incantation. For more info on what this patch does, see the doc/Keyboard_Navigation.txt document (after applying the patch, naturally...) Fixed bugs ---------- - all known segfaults - most 'weird navigation order' problems - related issue (now fixed in CVS): a_Findtext_search returned FALSE (instead of FINDTEXT_NOT_FOUND) when a search was performed on an empty page. Since this function is supposed to return a FindtextResult enum value (and the first value in that enum is FINDTEXT_SUCCESS) this made the focus code try to focus a link in an empty page leading to a segfault in the scrolled_window. TODO ==== - add x scrolling capability to Dillo (change anchors, URL_POS, scrolling functions, iterators, etc...). This is needed for better keyboard navigation on wide pages. Download instructions ===================== There is currently only one version of the patch, made against 2003119@14:09GMT CVS. 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. http://www.geocities.com/ikbenfrank/dillo-200311211558-kbnav.patch.gz size: 30615 bytes (gzipped, as downloaded) 152903 bytes (uncompressed) md5sum: 29aa01c8c5eabe3c7294b975155255ce (gzipped, as downloaded) 5c848e7f0e281e3135392522c8a7f980 (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." ]

Nov. 21, 2003

[PATCH] Version 15 of tab/frame/kbnav/etc patch, now with keywords and more...

by Frank de Lange

Hi'all, The next version (15) of my tab/frame/keyboard navigation patch is ready (see bottom of this message for download instructions). This release incorporates a number of bug fixes to keyboard navigation, in response to feedback on the list. It also fixes several other bugs (see non-exhaustive list further down). And, last but not least, there are several new features: keywords, use of location bar for search, local document handling on location bar, user configurable '_blank' target, repeated search, many more configurable key bindings, etc... /* ATTENTION */ This is the first release *without the conditional compile options* for tabs and frames. Tabs, frames and keyboard navigation are standard now, and there is no provision to compile Dillo without support for these features. This is a BIG patch, with many changes. Please test it, and tell me (through the list) about any problems. New features ------------ - keywords Keywords can be used to access sites and locations with short commands in the location bar (and elsewhere). They are defined in the dillorc as a space-separated list of keyword:url pairs: keywords = "<keyword>:<url> <keyword>:<url> ..." %s is in url is replaced by (escaped) location bar contents Example: (in dillorc) keywords="s:http://www.google.com/search?q=%s" "s dillo patch" in the location bar will execute a search on google for the words 'dillo patch'. There is one default keyword, "search". This corresponds to the search_url preference. The web search feature has been changed to use the new code. Keywords currently work in the location bar, in the "open url" window and *from the command line*. This way you can search the web from the command line: dillo "search whatever you want to search for" (enter) [ programming info ] To add keyword processing to a url, you need to make an explicit call to a_Url_string_process_keywords(gchar *str). I explicitly did NOT add the keyword processing code to the default url code path, so keywords can not be initiated through external links. Better safe than sorry... - local file handling in the location bar: type a valid absolute path in the location bar and it will be transformed into a valid file: url. [ programming info ] To add local path processing to a url, you need to make an explicit call to a_Url_string_process_local(gchar *str, gboolean relative) Set relative to TRUE to include relative path processing (from the current directory) to the code path. - location bar search using keywords and/or with popup_dialogs=NO. If you have popup_dialogs=NO in dillorc, pressing the search button on the toolbar or using the search key combination (ALT-s) will search the web for whatever you typed in the location bar (if you have entered search terms) or focus the location bar with the search keyword set. In the latter case just add search terms and press enter to search. - location bar contents are selected when it is focused, deselected when the content area is focused. - the contents of the findtext and websearch entries are selected when they are re-opened. Type a new search term to replace the old term. Use the cursor keys to deselect the contents when you want to add to the existing search term. - the splash screen no longer lives in the binary (as suggested by Indan Zupancic). It is installed by the makefile and should be distributed with dillo. The default location is in the 'sharedstate' directory (default /usr/share/dillo/dillo.html). There is a preference for those who want to change this: splash = NO | <url> This takes any url. Set it to NO to suppress the splash screen alltogether (you will still be able to get to the splash screen by visiting about:splash). The default value is defined in prefs.h: #define DILLO_SPLASH "file:/usr/share/dillo/dillo.html" - There is a new preference for control of the "_blank" tag and handling of new windows in general (as suggested by Andreas Schweitzer): target_blank = SELF | TAB | [WINDOW] Set this to "self" to disable the "_blank" target (no more new windows popping up all around). The other two settings are self-explanatory I guess... This also works for documents opened using the middle mouse button, and documents opened on the command line. For the latter the "self" setting is ignored (it defaults to new windows in that case). - Repeated search by pressing CTRL-g at any time. Unhiglight search by pressing Escape. If search resulted in a highlighted link, this will be unhighlighted as well (to follow that link, press Enter instead of Escape). - many more configurable key bindings. To avoid overloading the scrolled_frame with content-related signals I added a general 'content_command' signal, which gets passed one parameter of type DilloCommand (defined in commands.h). To adjust a keybinding for a command, set a key for the signal 'content_command' for the widget named 'dillo-content' (or for the class GtkDwScrolledFrame). As an example the following binding sets the 'F3' key for the 'repeat find' command (like it does in Mozilla): key_bindings = "binding 'mozilla-keys' { bind 'F3' { 'content_command' (9) } ... (add more bindings if needed) ... } widget '*dillo-content' binding 'mozilla-keys'" There are currently 30 available commands: DILLO_COMMAND_NAVIGATE_BACK, /* 0 */ DILLO_COMMAND_NAVIGATE_FORWARD, /* 1 */ DILLO_COMMAND_NAVIGATE_RELOAD, /* 2 */ DILLO_COMMAND_NAVIGATE_STOP, /* 3 */ DILLO_COMMAND_NAVIGATE_HOME, /* 4 */ DILLO_COMMAND_DUPLICATE_WINDOW, /* 5 */ DILLO_COMMAND_DUPLICATE_TAB, /* 6 */ DILLO_COMMAND_FINDTEXT, /* 7 */ DILLO_COMMAND_FINDTEXT_INCREMENTAL, /* 8 */ DILLO_COMMAND_FINDTEXT_REPEAT_LAST_SEARCH, /* 9 */ DILLO_COMMAND_FINDTEXT_UNHIGHLIGHT, /* 10 */ DILLO_COMMAND_SAVE, /* 11 */ DILLO_COMMAND_SAVE_LINK, /* 12 */ DILLO_COMMAND_BOOKMARK, /* 13 */ DILLO_COMMAND_NEW_WINDOW, /* 14 */ DILLO_COMMAND_NEW_TAB, /* 15 */ DILLO_COMMAND_OPEN_FILE, /* 16 */ DILLO_COMMAND_OPEN_URL, /* 17 */ DILLO_COMMAND_OPEN_LINK, /* 18 */ DILLO_COMMAND_OPEN_LINK_NEW_WINDOW, /* 19 */ DILLO_COMMAND_OPEN_LINK_NEW_TAB, /* 20 */ DILLO_COMMAND_CLOSE_WINDOW, /* 21 */ DILLO_COMMAND_CLOSE_TAB, /* 22 */ DILLO_COMMAND_EXIT, /* 23 */ DILLO_COMMAND_TAB_PREVIOUS, /* 24 */ DILLO_COMMAND_TAB_NEXT, /* 25 */ DILLO_COMMAND_VIEW_SOURCE, /* 26 */ DILLO_COMMAND_VIEW_BOOKMARKS, /* 27 */ DILLO_COMMAND_FOCUS_LOCATION, /* 28 */ DILLO_COMMAND_WEBSEARCH, /* 29 */ DILLO_COMMAND_TOGGLE_FULLWINDOW /* 30 */ DILLO_COMMAND_FOCUS_ACTIVATE, /* 31 */ DILLO_COMMAND_FOCUS_ACTIVATE_NEW_WINDOW, /* 32 */ DILLO_COMMAND_FOCUS_ACTIVATE_NEW_TAB, /* 33 */ DILLO_COMMAND_FOCUS_POPUP, /* 34 */ DILLO_COMMAND_FOCUS_HIDE, /* 35 */ DILLO_COMMAND_FOCUS_MOVE_UP, /* 36 */ DILLO_COMMAND_FOCUS_MOVE_DOWN, /* 37 */ DILLO_COMMAND_FOCUS_MOVE_LEFT, /* 38 */ DILLO_COMMAND_FOCUS_MOVE_RIGHT, /* 39 */ DILLO_COMMAND_FOCUS_MOVE_TAB_BACK, /* 40 */ DILLO_COMMAND_FOCUS_MOVE_TAB_FORWARD, /* 41 */ DILLO_COMMAND_SCROLL_UP, /* 42 */ DILLO_COMMAND_SCROLL_DOWN, /* 43 */ DILLO_COMMAND_SCROLL_LEFT, /* 44 */ DILLO_COMMAND_SCROLL_RIGHT, /* 45 */ DILLO_COMMAND_SCROLL_PAGE_UP, /* 46 */ DILLO_COMMAND_SCROLL_PAGE_DOWN, /* 47 */ DILLO_COMMAND_SCROLL_PAGE_LEFT, /* 48 */ DILLO_COMMAND_SCROLL_PAGE_RIGHT, /* 49 */ DILLO_COMMAND_SCROLL_EDGE_TOP, /* 50 */ DILLO_COMMAND_SCROLL_EDGE_BOTTOM, /* 51 */ DILLO_COMMAND_SCROLL_EDGE_LEFT, /* 52 */ DILLO_COMMAND_SCROLL_EDGE_RIGHT /* 53 */ If you'd like to see any other commands, tell me or the list! [programming info] To add a new command, simply add the name to the DilloCommand enum, add a handler to a_Commands_handler() and, optionally, add a default key binding to a_Commands_init(). The commands.[ch] files are in a bit of a state of flux, as many commands are currently present in two forms: one with a *dd interface, the other (older) with a *bw interface. Where appropriate the older (*bw) versions can and will be removed - the View Source window can now be closed by pressing Escape. View source is (over)due for an overhaul by the way. I might implement the view-source protocol in one of the next patches. - Tab movement is now cyclic, thanks to a patch by Stephan Goetter - the Frame context menu now has navigation controls (as suggested by Stephan Goetter), so it is possible to go back in the frame history. The main history is not yet synchronised with frame actions. [LIST: Is this necessary? Should the 'back' button and menu remember actions inside nested frames or should it do what it does now, remember actions in the top-level document?] - Keyboard navigation can be used to popup context menus, as suggested by Melvin Hadasht. The default binding for context menu is Alt-Enter (and Alt-KP_Enter). The related DILLO_COMMAND is DILLO_COMMAND_FOCUS_POPUP. Fixed bugs ---------- keyboard navigation - all known segfaults - most 'weird navigation order' problems - related issue (now fixed in CVS): a_Findtext_search returned FALSE (instead of FINDTEXT_NOT_FOUND) when a search was performed on an empty page. Since this function is supposed to return a FindtextResult enum value (and the first value in that enum is FINDTEXT_SUCCESS) this made the focus code try to focus a link in an empty page leading to a segfault in the scrolled_window. document abstraction - a problem with tab/page duplication which had the potential to cause segfaults is fixed - selection copy did not work because I forgot to set the owner for the selection in tab mode. This is fixed. REMOVED PREFERENCES =================== These preferences have been removed from the patch. Update your dillorc if you used them. Complain to me (on the list) if you want them back. * tab_instead_of_window: merged into the new target_blank pref * focus_location_on_new: did anyone use the NO setting? * tab_bar_homogeneous: did anyone use the NO setting? * compress_vowels: can be changed during compile if needed, COMPRESS_VOWELS in src/misc.h CHANGED KEY COMBINATIONS ======================== * Internet search: ALT-s (was CTRL-g, CVS CTRL-s) * Repeat search CTRL-g (was nothing, CVS nothing) * View source: ALT-u (was CTRL-u, CVS nothing) * Open URL: CTRL-l (was SHIFT-CTRL-l, CVS CTRL-l) * focus location bar: CTRL-u (was CTRL-l, CVS CTRL-u) If you want the old keys back, add a binding for the related command (see above) If something doesn't work they way it should (or the way you *think* it should), I want to know! For more info on keyboard navigation, see the doc/Keyboard_Navigation.txt document (after applying the patch, naturally...). More information on tabs can be found in doc/Browser_Tabs.txt, for frames see doc/Browser_Frames.txt. The mailing list archives are also a good place to look for answers to questions relating to this patch. REMOVED COMPILE OPTIONS ======================= * --disable-tabs Tabs are a fixed part of the code now * --enable-xhtml-dtd Full frameset support is a fixed part of the code now TODO ==== - add x scrolling capability to Dillo (change anchors, URL_POS, scrolling functions, iterators, etc...). This is needed for better keyboard navigation on wide pages. Tabs, Frames and browser bloat ============================== version: 0.8.0-pre patch: dillo-20031121-tabs.patch.gz unpatched: 297172 bytes patched: 333364 bytes (gcc 3.2.2, binutils 2.13.90.0.18, CFLAGS "-Os") Download instructions ===================== The patch is made against 20031119@15:09 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-20031121-tabs.patch.gz size: 116678 bytes (gzipped, as downloaded) 529298 bytes (uncompressed) md5sum: 846a6be5100809cd95553e2cae595f3b (gzipped, as downloaded) 7a94882aa87a8787d959105231fcfacf (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." ]

Nov. 21, 2003

Re: [Dillo-dev] FLTK

by Frank de Lange

Melvin Hadasht wrote: >Another advantage is that when used with Gnome, GTK2 gains accessibility >functionality for handicapped persons. I like to think that the kbnav is >already one big step toward offering such functionality (perhaps it lacks >a way to open context menus), thanks to Frank. After reading this message I implemented this in the coming version of the patch (available today if I find the time to release it). The default key binding is ALT-Enter (or Alt-KP_Enter). It can be bound to any other key using the appropriate preference setting (see the README documents for more info on this). The menu pops up under the link for keyboard navigation, under the pointer for mouse actions. Any other suggestions to make Dillo more accessible for both non-handicapped and handicapped users? 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." ]

Nov. 21, 2003

Re: [Dillo-dev] Emacs

by Frank de Lange

Sebastian Geerken wrote: >>>(Emacs' use of tabs >>>messes up things sometimes, and the 2-space indent it uses are not >>>consistent with Dillo's conventions). >>> >>> > >Emacs users, put the following code into ~/.emacs: > >---------------------------------------------------------------------- >(defun array-find (a1 a2 &optional index-or-nil) > (let ((index (if index-or-nil index-or-nil 0)) > (l1 (length a1)) > (l2 (length a2))) > (if (> (+ index l2) l1) > nil > (let ((i 0)) > (while (and (< i l2) > (= (aref a1 (+ index i)) (aref a2 i))) > (setq i (+ i 1))) > (if (= i l2) > index > (array-find a1 a2 (+ index 1))))))) > >(defun my-c-hook () > (if (array-find (buffer-file-name) "/dillo") > (progn > ;; dillo conventions > (set-variable 'indent-tabs-mode nil) > (set-variable 'c-basic-offset 3)) > ;; conventions for other code > (set-variable 'indent-tabs-mode t) > (set-variable 'c-basic-offset 2))) > >(add-hook 'c-mode-hook 'my-c-hook) > > Thanks... Makes it a bit easier to be Dillo-compliant... 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." ]

Nov. 21, 2003

Re: [Dillo-dev] Proposal: United Dillo

by Indan Zupancic

> I mean, removing the possibility of having another Dillo instance is > equivalent restricting its usage. That's why I suggested the other solution. True, that's why I will probably make it a cmd option too, seeing that running only one Dillo is not what people seem to want, and difficult in other cases. > Your patch was also meant to get rid of dpid, if I understood correctly. No, my patch made it only easier to get rid of it in the future. > My point was that I don't think dpid is so expensive apart maybe for > https: The structure of dpid is not optimal for https: the dpidservice > gets data from internet and the it passes it to dillo. It adds a proxy, > and that may reduce throughput. But this should be quantified and proved. That's what you get if you treat https as a protocol instead of just http over ssl/tls, if you ask me. ;) > This is in fact a X feature. It just happens that gtk-1.2 did not support > it. Of course it is a X feature, but one that is impossible to use when the widget doesn't support it. Seems like it's not needed though. Greetings, Indan

Nov. 20, 2003

Re: [Dillo-dev] Re: kbnav3 patch test

by Frank de Lange

Jorge Arellano Cid wrote: >>I have taken a look at your patch-to-my-patch, but did not apply it to >>the version I will publish later today. >> >> OK, later tomorrow, did not have time today... Both patches. Anyway, the reason I did not apply the patch was because it was incomplete, and I had changed my version in the meantime (as you'll notice when it finally is available to the masses, tomorrow...). > Thanks, we strive to be style consistent. > BTW, I didn't try to fix indentation in the patch, it >was just to do a test run. > > I'd like to teach my Emacsen to 'do the right thing', but they all have a will of their own when it comes to indentation. And the use of tabs instead of spaces. But as Emacs' indentation (GNU-style) is what I generally use that's no problem for me. Except in the case of Dillo... >focus.c: In function `Focus_state_find_list': >focus.c:268: warning: `list' might be used uninitialized in this >function >focus.c: In function `Focus_state_find_link': >focus.c:465: warning: `list' might be used uninitialized in this >function > >gcc version 3.2.3 > > Hmmmm... Nothing here with 3.2.2, weird. I'll have a look at this... >>(including the one causing the Tarot page to crash by the way - see my >>message dated Wed, 12 Nov 2003 11:00:58 +0100). >> >> > > Oh, I didn't find anything about it at GMANE !? > > http://article.gmane.org/gmane.comp.web.dillo.devel/1458 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." ]

Nov. 20, 2003

Re: [Dillo-dev] Proposal: United Dillo

by Melvin Hadasht

> Always having one Dillo even when you exec dillo is practically the same > as always having one Dillo. And as a sort of server mode, in the sense > that you just send a message and exit instead of running and doing the > stuff. I took a look at your patch, you mainly do the same as I did, but > you added much code to handle all the extra commands. I would handle the > "server" commands the same as the cmd commands, they are mostly the same > anyway. Simpler, more code reuse, smaller and less code. My patch doesn't > do that yet, but that's because dillo.c needs to be rearranged a bit to > make it possible, wanted a working patch first, and see what people think > about it before wasting time finishing it. I mean, removing the possibility of having another Dillo instance is equivalent restricting its usage. That's why I suggested the other solution. > > Concerning the second advantage (not using dpid): performance reasons > > would be of concern especially when large amount of data need to > > be passed from and to dillo (https), but maybe we need to quantify this > > before. > > I don't understand your point, performance reasons are of concern only > when using dpid, because dpid copies data, so what exactly has this to do > with my patch? Your patch was also meant to get rid of dpid, if I understood correctly. My point was that I don't think dpid is so expensive apart maybe for https: The structure of dpid is not optimal for https: the dpidservice gets data from internet and the it passes it to dillo. It adds a proxy, and that may reduce throughput. But this should be quantified and proved. > Good to know it's possible, and that it depends only on the widget toolset > if it's supported or not. This is in fact a X feature. It just happens that gtk-1.2 did not support it. -- Melvin Hadasht

Nov. 20, 2003

Re: [Dillo-dev] Proposal: United Dillo

by Indan Zupancic

Hello, Accidentally activated some hidden command to search (damn firebird, should have used Dillo :), so lost the email I waswriting... Summary below: > I think that the advantage of always having one Dillo is not an argument, > because even now you can run only one instance. If you want that every > "dillo" command uses the first instance, then another approach would be > to use a "remote" or "server" mode, like mozilla, nedit, xemacs and vim > have. > I once made a patch for Dillo to support this. The patch is not uptodate, > but I can update it on request. Always having one Dillo even when you exec dillo is practically the same as always having one Dillo. And as a sort of server mode, in the sense that you just send a message and exit instead of running and doing the stuff. I took a look at your patch, you mainly do the same as I did, but you added much code to handle all the extra commands. I would handle the "server" commands the same as the cmd commands, they are mostly the same anyway. Simpler, more code reuse, smaller and less code. My patch doesn't do that yet, but that's because dillo.c needs to be rearranged a bit to make it possible, wanted a working patch first, and see what people think about it before wasting time finishing it. > Concerning the second advantage (not using dpid): performance reasons > would be of concern especially when large amount of data need to > be passed from and to dillo (https), but maybe we need to quantify this > before. I don't understand your point, performance reasons are of concern only when using dpid, because dpid copies data, so what exactly has this to do with my patch? > gtk1.2 cannot do this, but gtk2.0 can migrate a window from display to > display. It can also open a new window in another display (display being > another X server, like a remote host). Good to know it's possible, and that it depends only on the widget toolset if it's supported or not. In reply to Jyri Jokinen: > I said "browser tabs". Window manager level window grouping is ok, > and renders browser tabs useless. That was/is the point. Think about all those poor souls using some window manager which has no grouping/tabs or something similar. Also, tabs in a browser means only extra subgroups, very useful when you have a lot browsers open. Greetings, Indan

Nov. 20, 2003

Re: [Dillo-dev] Proposal: United Dillo

by Jyri Jokinen

On Thu, Nov 20, 2003 at 08:48:56PM +0100, Indan Zupancic wrote: > 1369 k/Dillo versus 795 k/window. That's not really an issue. I gladly accept the larger memory consumption when it gives me better reliability and still is, in comparision with the rest of the web browsers, minimal. > > I think it's the stupidest idea since browser tabs. (*) > Thanks for your (honest and to the point) oppinion, but really, 50 windows > open, and you hate tabs? I said "browser tabs". Window manager level window grouping is ok, and renders browser tabs useless. That was/is the point. I don't like seeing code duplication, and certainly not somewhere it doesn't belong. Web browsers should help the user with web browsing, window managers with window managing. Somehow I feel I have said this before. :) -- shared, pekwm people

Nov. 20, 2003

Re: [Dillo-dev] Proposal: United Dillo

by Melvin Hadasht

Hi, Paul Pelzl wrote: > If this were the only concern, then maybe the solution is to > implement some sort of commandline option (e.g. --unified) that will > > 1) launch a new dillo if none are already running > 2) open a new window (or tab?) if there is already a dillo running > > Interested users could then "alias dillo='dillo --unified'" to get the > behavior you want. Of course, this does not have the benefit of > simplifying the code, but it would be a nice feature. I have a patch against old CVS at: http://melvin.hadasht.free.fr/home/dillo/server/index.html -- Melvin Hadasht

Nov. 20, 2003