Le 16/6/16 à 22:45, Tudor Girba a écrit :
Hi,
I think we are mixing the topics a bit. The #meta discussion is not specific to
Spotter actions.
The idea was to offer a uniform support of keybindings in Pharo, in general.
Then Guille etal added #meta to have a predictable mapping. All #cmd places
were changed to #meta, and since then we should not use explicitly #cmd
anymore, except when we know we are on Mac. For a portable modifier, we should
only use #meta.
At this point, both Rubric and Spotter use #meta. #meta maps on:
- Mac: Command
- Win: Control
- Linus: Control
This means that #alt is now a portable modifier that will not conflict with
#meta, so we can now think of using that one in combination with #meta.
For text navigation, the situation is a bit complicated. On Win/Linux,
Ctrl+Right/Left moves the cursor between words. On Mac, Cmd+Right/Left moves
the cursor at the end/beginning of line. So, using #meta for text navigation
between words is not entirely accurate. We should use #ctrl instead.
This would anyway mean that it would be an option to use #alt for Spotter now.
But, if we are at it, would anyone be interested in working on revisiting the
overall keybindings in Pharo?
It would be good.
I would really like to have an agreement on nautilus and non nautilus
- implementors
- senders
- references
Now this is not easy.
In addition, having on implementors falling back on class browse and the
inverse too
is really nice to have like that we do not have to think "ok this piece
of text represent a class so that I should browse)" or "this piece of
text is a method so I have to ask implementor (browse should bring
implementor)
we could also get back on binding. We could do the same for
senders/references (that are the same concept). I already fixed that and
it was lost two times.
Stef
