Hi nicolai

I'm not yet fully clear about the way we should handle keybinding.
They look to me a bit like settings in the sense that a widget should be able to define its own but that the system
could also "push" into it some predefined one.
We should probably have a way to have local redefinition of binding.

While we were brainstorming with Guille about we were thikning about having a command hierarchy as it was done in OB long
time ago.


Le 3/4/15 13:46, Nicolai Hess a ��crit��:
Shortcuts in text editor are hardcoded

I think it is a good idea to commonly name those short cuts.
But this does not help to make the shortcut handling really configurable.

For example, how would we change the shortcut for "toggle comment" ?
- we need a setting that lists all PharoShortcuts,
- change the keycombination in the setting
- toggleCommentOnSelectionOrLine now would�� return the new shortcut

But�� how do we populate the change to all users of this shortcut?
We would need to rebuild all keymaps.
(And if we want to save and load this shortcuts settings (load settings at startup), we
need to rebuild all keymappings on every image startup).


Instead, we could define commonly named "Actions". A texteditor can register this
action in its keymap and the action has a unique configurable KMKeyCombination

May be :)
I'm dead now.

what do you think?

cheers
nicolai