Changing playground and monticello shortcuts
Hi, currently to open a Playground via shortcut one has to type <cmd>+o+w, that's because it used to open Workspace. However since it now opens Playground the shortcut is no longer appropriate. So can we change it to <cmd>+o+p? (This shortcut is currently occupied by Monticello Browser, but that can be movd to <cmd>+o+m which is free.) You could argue that people are used to this shortcut, however that will not be true for newcommers, who will just see it as random naming (which it currently is). Peter
2015-11-11 10:45 GMT+01:00 Peter Uhnák <i.uhnak@gmail.com>:
Hi,
currently to open a Playground via shortcut one has to type <cmd>+o+w, that's because it used to open Workspace. However since it now opens Playground the shortcut is no longer appropriate.
So can we change it to <cmd>+o+p? (This shortcut is currently occupied by Monticello Browser, but that can be movd to <cmd>+o+m which is free.)
cmd+o+m would be ctrl+o ctrl+m on windows, but ctrl+m does not work yet on windows.
You could argue that people are used to this shortcut, however that will not be true for newcommers, who will just see it as random naming (which it currently is).
Peter
I actually think we should disable those shortcuts. The reason is that they âpollute" the global shortcut space: for example, you can now not use Cmd+o for any custom action in your own window, and that is less than ideal. The alternative is to use Spotter to spawn windows. The interesting thing there is that you do not need shortcuts for every specific windows because you can use regular search. For example, opening Playground is: Shift+Enter, p, Enter Cheers, Doru
On Nov 11, 2015, at 10:49 AM, Nicolai Hess <nicolaihess@gmail.com> wrote:
2015-11-11 10:45 GMT+01:00 Peter Uhnák <i.uhnak@gmail.com>: Hi,
currently to open a Playground via shortcut one has to type <cmd>+o+w, that's because it used to open Workspace. However since it now opens Playground the shortcut is no longer appropriate.
So can we change it to <cmd>+o+p? (This shortcut is currently occupied by Monticello Browser, but that can be movd to <cmd>+o+m which is free.)
cmd+o+m would be ctrl+o ctrl+m on windows, but ctrl+m does not work yet on windows.
You could argue that people are used to this shortcut, however that will not be true for newcommers, who will just see it as random naming (which it currently is).
Peter
-- www.tudorgirba.com "We cannot reach the flow of things unless we let go."
Ehm, or maybe fix event dispatch so it works properly? It should always end up testing for event handling By the leaf morph at the given event position and work its way up if unhandled, not check top-down like the change to dispatchEvent:with: has ended up doing... Cheers, Henry
On 11 Nov 2015, at 11:46 , Tudor Girba <tudor@tudorgirba.com> wrote:
I actually think we should disable those shortcuts.
The reason is that they âpollute" the global shortcut space: for example, you can now not use Cmd+o for any custom action in your own window, and that is less than ideal.
The alternative is to use Spotter to spawn windows. The interesting thing there is that you do not need shortcuts for every specific windows because you can use regular search. For example, opening Playground is: Shift+Enter, p, Enter
Cheers, Doru
On Nov 11, 2015, at 10:49 AM, Nicolai Hess <nicolaihess@gmail.com> wrote:
2015-11-11 10:45 GMT+01:00 Peter Uhnák <i.uhnak@gmail.com>: Hi,
currently to open a Playground via shortcut one has to type <cmd>+o+w, that's because it used to open Workspace. However since it now opens Playground the shortcut is no longer appropriate.
So can we change it to <cmd>+o+p? (This shortcut is currently occupied by Monticello Browser, but that can be movd to <cmd>+o+m which is free.)
cmd+o+m would be ctrl+o ctrl+m on windows, but ctrl+m does not work yet on windows.
You could argue that people are used to this shortcut, however that will not be true for newcommers, who will just see it as random naming (which it currently is).
Peter
-- www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
Hi, It was chosen a while ago that the Global shortcuts are checked first, before the local ones. The local ones propagate from bottom to top. The idea here was to guarantee global behavior, such as Shift+Enter for popping out things like Spotter. I was not happy about that, but that was the choice. Now, I think that the global keymap mechanism should be used sparingly, and I think that using it for Cmd+o is a bit too much. Cheers, Doru
On Nov 11, 2015, at 12:22 PM, Henrik Johansen <henrik.s.johansen@veloxit.no> wrote:
Ehm, or maybe fix event dispatch so it works properly? It should always end up testing for event handling By the leaf morph at the given event position and work its way up if unhandled, not check top-down like the change to dispatchEvent:with: has ended up doing...
Cheers, Henry
On 11 Nov 2015, at 11:46 , Tudor Girba <tudor@tudorgirba.com> wrote:
I actually think we should disable those shortcuts.
The reason is that they âpollute" the global shortcut space: for example, you can now not use Cmd+o for any custom action in your own window, and that is less than ideal.
The alternative is to use Spotter to spawn windows. The interesting thing there is that you do not need shortcuts for every specific windows because you can use regular search. For example, opening Playground is: Shift+Enter, p, Enter
Cheers, Doru
On Nov 11, 2015, at 10:49 AM, Nicolai Hess <nicolaihess@gmail.com> wrote:
2015-11-11 10:45 GMT+01:00 Peter Uhnák <i.uhnak@gmail.com>: Hi,
currently to open a Playground via shortcut one has to type <cmd>+o+w, that's because it used to open Workspace. However since it now opens Playground the shortcut is no longer appropriate.
So can we change it to <cmd>+o+p? (This shortcut is currently occupied by Monticello Browser, but that can be movd to <cmd>+o+m which is free.)
cmd+o+m would be ctrl+o ctrl+m on windows, but ctrl+m does not work yet on windows.
You could argue that people are used to this shortcut, however that will not be true for newcommers, who will just see it as random naming (which it currently is).
Peter
-- www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
-- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."
On Wed, Nov 11, 2015 at 11:46 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
I actually think we should disable those shortcuts.
The reason is that they âpollute" the global shortcut space:
Well they are global shortcuts, so that's to be expected.
for example, you can now not use Cmd+o for any custom action in your own window, and that is less than ideal.
as far as I know events bubble up, so morphs can intercept them (which will break the global shortcut, but if the programmer sees it as appropriate...)
The alternative is to use Spotter to spawn windows. The interesting thing there is that you do not need shortcuts for every specific windows because you can use regular search. For example, opening Playground is: Shift+Enter, p, Enter
This takes significantly more time, and on top of that doesn't actually work, because the first group is History and not Menu... so this would open PetitParser browser for me. I don't see a problem in having global shortcuts for the most important tools, if the current key combinations are problem, then we should come up with different combinations. Peter
participants (4)
-
Henrik Johansen -
Nicolai Hess -
Peter Uhnák -
Tudor Girba