Johannes wrote:
On Wed, Oct 19, 2011 at 11:16:34AM -0400, Benjamin Johnson wrote:
Hi again,
I was just wondering, could we add an option to control the address bar key bindings? I know they're set to behave like a Unix command line, which can be convenient, but it also interferes with some custom key bindings (as one of my users mentioned in bug #1012).
I've also noticed that the address bar bindings confuse a lot of people, since they're not used to the Unix behavior. Conventionally, Ctrl-A is "select all," and other input boxes in Dillo follow that, so they aren't expecting it to go to the beginning of the line instead.
Having it consistent over all text inputs and configurable via keysrc sounds reasonable to me. I don't know the keysrc details though, so I might miss something.
Cheers, Johannes
I was thinking just a simple boolean option in dillorc -- and turn it OFF by default (i.e., no Unix keys), because it's not typical GUI behavior, and anyone who wants it on can quite easily set it in his or her own dillorc. Making it consistent globally would be a bit tricky, since we'd have to replace all Fl_Inputs with our custom widget (including in FLTK's stock dialogs). Besides that, there's the matter of other FLTK applications -- would users expect them to behave our way, too? Personally, I'd just as soon ditch the Unix keys altogether, but if we must keep them, let's let the address bar remain the exception. That way, we're not breaking the behavior either way -- new users aren't surprised, and old users can keep it as it was. Although I will add, the Shift-{Left,Right} bindings in the address bar *have* to go. They're fine elsewhere, if a bit quirky, but in the address bar they interfere with text selection. Ctrl-Tab and Ctrl-Shift-Tab are much more logical and convenient, anyway. ~Benjamin
Benjamin Johnson (2011-10-20 15:56):
Johannes wrote:
On Wed, Oct 19, 2011 at 11:16:34AM -0400, Benjamin Johnson wrote:
Hi again,
I was just wondering, could we add an option to control the address bar key bindings? I know they're set to behave like a Unix command line, which can be convenient, but it also interferes with some custom key bindings (as one of my users mentioned in bug #1012).
I've also noticed that the address bar bindings confuse a lot of people, since they're not used to the Unix behavior. Conventionally, Ctrl-A is "select all," and other input boxes in Dillo follow that, so they aren't expecting it to go to the beginning of the line instead.
How should dillo behave when a user binds Ctrl-A?
Having it consistent over all text inputs and configurable via keysrc sounds reasonable to me. I don't know the keysrc details though, so I might miss something.
Cheers, Johannes
Having input/insert mode and macros in keysrc would be interesting, if not too complex.
I was thinking just a simple boolean option in dillorc -- and turn it OFF by default (i.e., no Unix keys), because it's not typical GUI behavior, and anyone who wants it on can quite easily set it in his or her own dillorc.
Would be a strange dillorc option. A real patch would implement this in keysrc :) Somehow I failed to notice that Ctrl-A for select all is "typical GUI behavior", perhaps I am not using GUIs enough...
Making it consistent globally would be a bit tricky, since we'd have to replace all Fl_Inputs with our custom widget (including in FLTK's stock dialogs). Besides that, there's the matter of other FLTK applications -- would users expect them to behave our way, too?
Personally, I'd just as soon ditch the Unix keys altogether, but if we must keep them, let's let the address bar remain the exception. That way, we're not breaking the behavior either way -- new users aren't surprised, and old users can keep it as it was.
Here, Ctrl-A goes to the beginning of the line in all the input boxes ("find text", "web search", <input> in forms).
Although I will add, the Shift-{Left,Right} bindings in the address bar *have* to go. They're fine elsewhere, if a bit quirky, but in the address bar they interfere with text selection. Ctrl-Tab and Ctrl-Shift-Tab are much more logical and convenient, anyway.
~Benjamin
Are we using different versions of dillo? Shift-{Left,Right} doesn't do anything here. For the arguments sake, how would having to press Ctrl-Shift-Tab be more "logical and convenient" than Shift-Left? It's a matter of taste (habit). In my opinion, both bindings have a disadvantage: Ctrl-Shift-Tab is difficult for the fingers, Shift-Left is unusual to most people. That's why it is configurable, isn't it? -- -- Rogut?s Sparnuotos
participants (2)
-
obeythepenguin@gmail.com
-
rogutes@googlemail.com