Hi! I've lurked for a couple days, and seeing that this is an active list, thought I'd say "hi." Hi! At the moment, I'm a casual Dillo user, but I definitely like the browser and the idea behind it. I'd love to contribute, and when I've had a chance to sourcedive a bit and check out the bugtracker, you may see a thing or two from me. Things I'm interested in working on at the moment are adding options to configure keybindings (and if that ends up happening, maybe creating CUA (most graphical applications)/Emacs/vi/Conkeror/Firefox (probably not all of the above, but at least a couple) easily-loadable keymaps), and possibly adding surfraw support as an optional module (I haven't thought about how to implement these or anything; just brainstorming), and maybe find-as-you-type searching. (I know that sounds like a list of complaints, but it's not meant that way at all.) I'll likely play around with some of this stuff at some point, but if you have any ideas/tips on where to look for relevant code/how to go about it, sweet! Er. How's that for an introduction? Have a nice ${time_of_day}! -- If I Ever Become An Evil Villainess... 176. I will add indelible dye to the moat. It won't stop anyone from swimming across, but even dim-witted guards should be able to figure out when someone has entered in this fashion.
Hi Ivy, Welcome aboard! On Fri, Oct 24, 2008 at 07:17:03PM -0500, Ivy wrote:
Hi!
I've lurked for a couple days, and seeing that this is an active list, thought I'd say "hi." Hi!
At the moment, I'm a casual Dillo user, but I definitely like the browser and the idea behind it. I'd love to contribute, and when I've had a chance to sourcedive a bit and check out the bugtracker, you may see a thing or two from me. Things I'm interested in working on at the moment are adding options to configure keybindings (and if that ends up happening, maybe creating CUA (most graphical applications)/Emacs/vi/Conkeror/Firefox (probably not all of the above, but at least a couple) easily-loadable keymaps), and possibly adding surfraw support as an optional module (I haven't thought about how to implement these or anything; just brainstorming), and maybe find-as-you-type searching. (I know that sounds like a list of complaints, but it's not meant that way at all.) I'll likely play around with some of this stuff at some point, but if you have any ideas/tips on where to look for relevant code/how to go about it, sweet!
Great. Configurable keybindings is a must. Now, as unfortunately our mailing list search engine is down (now working on it), I'll quote a bit from there on this topic:
[Jorge wrote:] I believe one of the important things that we could support is custom keyboard shortcuts in dillorc. There are different shortcut sets, hardcoded into the user's brain, and they depend on what apps. the person is accustomed to use. For instance, if I've been using an editor where the "find text" function is F3, I'd like to have F3 do the same in dillo.
[Jorge wrote:]
[Justus wrote:] We could pick one / some user interface guideline(s) ([1] lists some) and try to adhere to it / them. Or we could pick one popular browser and copy its 'feel'.
Dillo has come to have it's own "simple" feel, and users have been communicative in making clear they like it.
Now that we changed the UI, we have to define some things though.
The basic model behind dillo is simplicity achieved with:
* right-click context menus. * providing some keyboard shortcuts.
As stated before, we can improve it by allowing custom keybindings.
As you can see this is needed. If you want to get into the code and find out how it looks, peruse the ::handle() functions. E.g.: cd dillo-2.0/src ./srch ::handle That will give you a list of source files defining handle(). Start with ui.cc. Note: FLTK2 has a virtual handle() method, it receives EVENTS from the FLTK2 engine. If a developer wants to customize a widget's behaviour she must do in handle(). One way to do this is to define a table of function/shortcut, and fill it with defaults and override with dillorc settings. ---------------------------------------------------------------------- After configurable shortcuts, there's keyboard navigation... ---------------------------------------------------------------------- Another good task to begin with is the multiple search engines. Currently we have only one hooked, configurable using dillorc. The idea is to extend dillorc with something like: search_url="<title>,<URL>[,LoadPage]" and improve the search dialog: .------------------------------, | Search with <title>: | | [_________________________] | | | | [Cancel] [OK] | '------------------------------' Where <title> is a drop-down menu with a <title> list. For instance: .------------------. | Google | | Wikipedia | | FreeDictionary | | ... | '------------------' ... now some sugar-coat: UpKey focus the menu. Selecting a menu item re-focus input line (History may be added to DownKey). ---------------------------------------------------------------------- BTW, what does CUA mean? ----------------------------------------------------------------------
Er. How's that for an introduction?
Very good. Now I know your interests, but not your skills. I assume you're good with C/C++ and widgets. Once again, welcome aboard! PS: Other developers that have contacted me, may also choose from this task list. Just be sure not to be silent about it and to coordinate. -- Cheers Jorge.-
and maybe find-as-you-type searching.
You can get most of find-as-you-type for (nearly) free by taking the ReturnKey test out of Findbar::search_cb2() and changing the when() in Findbar::Findbar to something like WHEN_CHANGED. I seem to recall that there are times when this alone doesn't do quite what you might want, but I don't remember the details.
participants (3)
-
corvid＠lavabit.com -
jcid＠dillo.org -
joyfulgirl＠archlinux.us