Corona Editor is the official Corona SDK plugin for Sublime Text. Designed to make building apps even easier by adding functionality to Sublime Text to improve developer productivity.

1. Install the Sublime Text Package Control plugin if you don't already have it: https://sublime.wbond.net/installation
2. In Sublime Text choose: Tools > Command Palette... > Package Control: Install Package
3. Find Corona Editor by typing in the search field, click on it to install it
4. Restart Sublime Text or reopen any .lua files to see the new features

Alternatively, if you are comfortable doing manual installs of Sublime Text plugins and want to run the latest development version, you can download the plugin from https://github.com/coronalabs/CoronaSDK-SublimeText/archive/master.zip.

After restarting Sublime Text you'll have several new features available in the Corona Editor menu and in the context menu when editing .lua files.

There are several Sublime Text User Preferences that can be set to fine tune the behavior of the plugin. You can find information on setting User Preferences http://www.sublimetext.com/docs/3/settings.html.

The Corona Debugger allows code to be single stepped, variables to be examined and breakpoints to be set. You can run the debugger using the Corona Editor menu from any file in the project and it will automatically find main.lua. Right click on a code line in the editor and choose Toggle Breakpoint to turn breakpoints on and off. Select the name of a variable and choose Inspect Variable from the context menu to see its value.

The following keys also control the Debugger:

A simpler alternative to the Build command in Sublime Text is the Run Project command in the Corona Editor menu (or Super+F10). It doesn't have all the bells and whistles of the build system but it is quick and easy. It is also better at finding your project's main.lua if you aren't using Sublime Text's projects.

• corona_sdk_simulator_path (default: system dependent)

  Set this to the path of your Corona Simulator if it's not installed in the default location for your operating system (remember to double the backslashes in Windows paths). You can also set this in the build.settings file of individual projects to customize the version of the Corona Simulator that is used for each project.

• If you Run the project and it doesn't hit a breakpoint, you'll have to stop and restart to regain control (in particular, setting a breakpoint on a line of code you know is being executed wont stop the program).
• Single stepping through "internal locations" is tedious.
• Using the Run Project command while in the Debugger can result in a confused state.
• There's an implicit breakpoint set on the first line of main.lua so to hit your own first breakpoint you need to run once to start the debugger and stop on the first line then run again to continue until you hit your own breakpoint.

Completion works for all API calls and constants (correctly handling periods in the name). Fuzzy matching is optionally done to increase the chances of finding the item you are looking for. Completion relies on the current Syntax setting so when creating new files you should use View / Syntax / Corona SDK Lua command to set the correct syntax for the new file. You will probably also want to change Sublime Text's default for .lua files by choosing View > Syntax > Open all with current extension as... > Corona SDK Lua when you have a .lua file open in the editor.

• corona_sdk_completion (default: True)

  If you don't like Corona Editor's completion you can turn it off entirely using this preference.

• corona_sdk_use_fuzzy_completion (default: True)

  Turn off "fuzzy completion" and just complete based on the characters typed so far as a prefix.

• corona_sdk_complete_periods (default: True)

  Corona Editor turns off the special meaning of periods as "word separators" in Sublime Text to make Corona completions work better. If you like to use cursor movement keys like "Alt+Arrow" to move to the periods in function calls you might want to turn this off. The most obvious effect of turning it off is that when you type a period all the completions disappear until you type another character.

• corona_sdk_use_docset (default: "public")

  Choose which completion set you want to use. Can be one of "public" (the default), "legacy" or "daily".

• The order of items in the completions popup seems a little odd but is due to Sublime's "fuzzy" matching

Documentation can be called up by placing the cursor on an API call (or selecting it) and either hitting F1 or choosing Corona SDK Docs from the context menu. Lua keywords will be looked up in the Lua documentation. If the context of something isn't recognized, a search of the Corona SDK documentation will be initiated.

• corona_sdk_use_docset (default: "public")

  Choose which documentation set you want to use. Can be one of "public" (the default), "legacy" or "daily".

• Note that right clicking on an item wont move the cursor there so you can't right click on a term that's not at the insertion point and then pick Corona SDK Docs from the context menu as it's the position of the text cursor that determines what's looked up (left click on the item first)
• Some of the completions have minor errors with nested optional parameters.

A selection of commonly used code fragments and templates is available via the Corona Editor > Snippets menu. Selecting an item from a submenu will insert its code at the current insertion point in the file.

A default set of snippets is created in the Sublime Text support folder Packages/User/Corona Editor/Snippets. You can create your own folders and files to add to the default set. Files should either be Sublime Text .sublime-snippet files or plain text files. The contents of plain text files are just inserted when chosen unless they exactly match a completion entry in which case the completion is looked up and they work like a normal completion (you can tab between the arguments) which provides a way to make menus of hard to remember API calls.

The current app can be run in the Simulator by pressing Ctrl+B (Windows) or Cmd+B (MacOSX). Debug output appears in the "build" window in Sublime Text. See also the Run Project command above.

• corona_sdk_auto_build (default: False)

  If you set this to "True" the Sublime Text "build" command will be issued any time you save a .lua file.

Syntax highlighting of Lua with Corona SDK calls is done (choose View > Syntax > Corona SDK Lua to enable this). You will probably also want to change Sublime Text's default for .lua files by choosing View > Syntax > Open all with current extension as... > Corona SDK Lua when you have a .lua file open in the editor.

• A shortcut to the Sublime Text Goto Anything... function list has been added to the context menu as Function Navigator.... This lists the functions defined in the current file and choosing one takes you to that definition.
• The Corona Editor menu has a Show/Hide Build Panel command to toggle the visibility of the Build Results panel (which displays the output of the Simulator). Note that hiding the panel clears its contents.

You can find discussion about Corona Editor on our http://forums.coronalabs.com/forum/630-corona-editor/. Let us know if you'd like to try prerelease versions.

If some aspect of the plugin doesn't behave as expected be sure to include any console output when reporting the problem. You can view the console using View > Show Console and copy and paste the information displayed there.

You may want to set the Use all F1, F2, etc. keys as standard function keys option in System Preferences / Keyboard to make using F10 and F11 easier for the debugger. Alternatively you may want to reassign the keys used to drive the debugger; information on how to this can be found at http://www.sublimetext.com/docs/key-bindings

Many thanks to the Corona users who have provided feedback and suggestions to make Corona Editor even better. Particular thanks to develephant and givemeyourgits for their contributions and help.