Comment #4 on issue 4532 by
[hidden email]: inconsistent text
selection in workspaces
http://code.google.com/p/pharo/issues/detail?id=4532Mmm... more or less.
At least it was less inconsistent in:
Pharo1.2.1
Latest update: #12345
it had almost the behavior of text editors in OSX.
To work as people expects, it should: (as it can be tested in any text
editor, like Pages, TextEdit, smultron, etc)
1. left or right +cmd go from beginning of line to end of line
2. up+cmd go to the beginning of document
3. down+cmd go to end of document
4. left +option or +control jump word by word, when reached first word go
to last of previous line
5. right +option or +control jump word by word, when reached last word of
the line go to first of next line
6. up +option go to beginning of line then go up line by line
7. down +option go to end of line then jump down, line by line, staying at
the end of those lines
8. up +control make a page up without changing cursor position
9. down+control make a page down without changing cursor position
10. left +fn go to beginning of document without changing cursor position
11. right +fn go to end of document without changing cursor position
Knowing that having two monitors have dramatic effects in developers (see
here:
http://www.codinghorror.com/blog/2004/06/multiple-monitors-and-productivity.html)
we
can infer that the sum of the "little times" consumed by "the feature"
of not having the right keystrokes is eating precious time from everybody
without any reasonable payoff. So it would be pretty nutty to leave it like
that (hence my WFT comment).
What's important here, I think, is that, having this behavior plus some
keyboard commands for the debugging process we can make all Pharo users
dramatically more productive and improve the Pharo UX a lot with modest
effort.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Locked
