Today, I’m happy to announce that Corona Editor is now 1.0!

Since we first announced the beta, you’ve given us fantastic feedback on how we could improve your daily code editing/development experience. We’ve added a ton of improvements including better support for both Sublime Text 2 and Sublime Text 3.

We created a dedicated “Corona Editor” menu to help make it easier for you to access some great new features like a new code snippets feature that helps with syntax and coding conventions.

In addition, we’ve added debugging and breakpoint support. Now you can set breakpoints directly in Sublime Text. Just open the file up, set a breakpoint, and launch the project — all within Sublime! We’ve even added special windows to Sublime so you can look at the callstack and inspect variable values directly.

We’ve updated our video tour to highlight just a few of the great features in Corona Editor:

We think this is a great lightweight IDE for Corona developers and we look forward to your feedback. If you want any specific features, please add/vote for them. And of course, we are open to code contributions.

  1. I’m definitely going to use the plugin, but I have one question, totally not related… what is your accent? I was distracted the entire video trying to listen and figure it out. lol

  2. Whats the big deal?

    Sublime Text is not free, so how can you call this a Corona Editor.

    This is just a plug in for Sublime Text, or am I missing something?

    This is no different than Lua Glider

    • Larry – Corona Editor is indeed a plugin for Sublime. It adds a pretty good amount of functionality on top of it. Of course, you are free to use any other IDE or editor out there. There are several good ones and have different strengths. Glider is great too.

    • I’ve used both, and each have their own strengths and weaknesses. The biggest difference for me is speed.

      Glider is slow and heavy while Sublime is fast and light. I have to occasionally restart Glider during the day when it gets too slow. Granted, the latest update of Glider has reduced the necessity to do that however it still needs to be done sometimes.

      Gilder’s debugger is still better, however improvements have been made to Corona Editor that have made it fully usable, and with further improvements being made I think it will soon be up-to-par with Glider.

      Both Glider and Sublime/Corona Editor are useful tools, and it all comes down to personal preference.
      I have switched to Sublime/Corona Editor for my projects mainly because of its speed, and it has all the functionality I need without any bloat.

  3. Lua Glider has a much better Function Navigator as well. The one built into Corona Editor doesn’t find my functions when they are defined like so:

    local shuffle

    shuffle = function(t)

    I do like the speed of Sublime and Corona Editor. I, like Ingemar, have problems with Lua Glider being slow sometimes.

    I can’t seem to get the debugger to work in a consistent manner in either Lua Glider or Corona Editor.

    In Lua Glider, sometimes when I start my app in debug mode, it just acts as if it’s not in debug mode.

    In Corona Editor, it looks like it’s stepping into one of my .lua files, but the fill will be totally blank, like all the code has been erased. Anyone else seeing that? I’ve tried Sublime Text 2 and 3 to see if it made a difference, and it did not. My breakpoints never seem to be hit either.

    I think adding snippets to Corona Editor is a great idea.

  4. Personally I find it insulting that Corona Labs chose to dedicate this much resource to solve an non-existent problem while there are so many issues and lacking features in widgets. The editor while useful was not on the roadmap nor was it a highly requested feature on the voting list yet it gets all this attention and resource. Can’t figure out why.

    • CL has more than one engineer and I doubt this is a company wide effort. Different engineers will be working on different things, just because one or two are working on the editor doesn’t mean it’s draining resources from other features.

      • Graham,

        Thanks for your comment. I realize my opinion is the odd one out here.

        It has often been said that Corona Labs is a small company with limited resources. It is understandable therefore that the limited resources need to be allocated carefully where the Corona Labs management deems strategic and critical. Roadmap alignment and supporting feature requests voted up by the developer base therefore has to be of utmost importance in this highly volatile business space. To the best of my understanding, this ‘feature’ is neither on the roadmap nor has it been a highly requested feature.

        Given all the critical issues yet to be resolved in a number of areas but most importantly the widget code which is affecting Corona SDKs viability and success in the business apps market, it is hard for me to understand this resource allocation decision. My question is… how many widget bugs could have been fixed by now if only the Corona Editor resource was allocated to work on the widget issues as well?… This is a hypothetical question perhaps since there is a possibility that the skills match may not be there but still it is relevant IMHO…

        I leave you with my unofficial list of widget bugs and promised features.

        https://docs.google.com/spreadsheet/ccc?key=0AsuRVbWElS3YdGpCN0V3emtmWnlwQmRUOVlpb3RkOGc&usp=sharing

        • Sorry, my comment came off harsher than it should have. I was in a rush so had to keep it short, in hindsight I probably should have just waited to respond when I had more time :-)

          I do agree that resources need to be used wisely and having just had a quick glance over the spreadsheet I can see there are quite a number of Widget issues. I was unaware of these simply because we don’t really use them in our stuff.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>