Labs/Bespin/Tips: Difference between revisions

Labs/Bespin/Tips (view source)

Revision as of 16:50, 27 July 2009

437 bytes added , 27 July 2009

no edit summary

Dalmaer

355

edits

@@ Line 1: / Line 1: @@
 We want to make Bespin as discoverable as possible, but there are already lots of little tips and tricks, so we wanted a place to hold them:
-==== Ctrl-J: Jumping from Editor to Command Line ====
+== Important Shortcut Keys ==
-We love using the keyboard to navigate and often find ourselves jumping from the editor to the command line and back. To do this easily, simple use Control-J.
+NOTE: Cmd == the Apple key on a Mac, and the Ctrl key on Windows / Linux.
+==== Cmd-J: Jump to the Command Line ====
+To get to the command line, simply type Cmd-J. To get back to the editor, use Escape.
+==== Cmd-O: Open File Browser ====
+The file browser is a good way to look at the files and folders that you have in the cloud. Cmd-O will give you access to the file system and you can go from there.
+==== Cmd-I: Quick Open ====
+Cmd-I will open a quick way to jump to any file in a given project. The quick open window will jump up and you can start searching. It will remember your recent files for quick access.
+==== Cmd-L: Goto Line ====
+Opens the command line with the "goto " command seeded. Simply type the line that you wish to jump to and you will be sent there.
 ==== Ctrl-L: Center selected line ====
@@ Line 21: / Line 37: @@
 * renameproject currentName newName
 * mkdir path projectname
-==== Open in a new tab ====
-If you are in the dashboard and want to open a file from the Open Sessions, or from the file chooser, just SHIFT+DOUBLE+CLICK.
 ==== How can I tie my own code into the editor? How can I extend it? ====
-One way yo inject your own code to change the experience is via the special BespinSettings/config.js file.
+One way yo inject your own code to change the experience is via the special BespinSettings/config file.
 You can read more at the [[Labs/Bespin/Roadmap/ConfigIntegration|config integration area]].