> cmd+h, then search for what you want (jump panels, execute commands, everything you can do in calypso you can find it there).
Thanks. But Spotter can hardly be a replacement for the keyboard. Spotter is a marvel by itself, however please try to survive developing in Pharo for a minute without a mouse - or just jumping to different panes in Calypso, debugger and inspector. For instace, I checked all the shortcuts under ctrl-o-s. The shortcut ClySwitchFocusToPreviousBrowserPaneCommand>>fullBrowserShortcutActivation should take you to the previous panel. It works for the top four panels, but not for the coding panel - or am I too clumsy? Furthermore, if you edit the code in Calypso, there are hidden shortcuts ctrl-1, ctrl-2, ctrl-3 etc. which take you to different tabs of the coding (bottom) panel. While editing the code, press ctrl-1 (this takes you to the Comment tab) and then go back to your code by using the keyboard. You can type in the code editor, however the panel is not selected (the blue frame is missing in the dark theme), and there is no cursor, so you are typing in the dark. And so forth. The problem is not people trying to edit the code in emacs, the problem is how to give them the experience which was already invented and works well. There's no danger that Pharo will not be Pharo anymore, if we do that. Visual programming is not the mouse to click on the editor panels. And, in my opinion, a lot has already been done in this direction. I really don't understand all the fuss in this thread. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
