Corona Editor Update

Solar2D Corona Editor
#1

Everyone’s like, finally, man!

I’ve pushed a good set of fixes and changes to Github so if you’re a bleeding edge type and don’t mind the occasional pebble in your shoe, you can test along with me.  Hopefully there will be few surprises and an official release will go out next week (which is what you should wait for if you aren’t comfortable opening up Sublime Text and changing the plugs and oil).

Completion Improvements

  • Now only files which have their syntax set to Corona SDK Lua  are considered to be Corona Lua files
  • Add support for corona_completions_strip_white_space preference to strip whitespace from completions
  • Fix doubling of prefixes when doing completion under certain circumstances
  • Add appropriate symbols to the word terminators list
  • Change the way periods are handled so that the ST word_separators  preference is not changed (logic is now based on the more appropriate  auto_complete_triggers  preference). Changes are reverted when the buffer is closed
  • Fixed an annoying regex error that would happen occasionally

Syntax Improvements

  • Fixed the way functions are parsed so that all 3 kinds are recognized correctly (this affects not only the coloring of the code but also the Function Navigator )
  • Added highlighting for composer

Build Panel Fix

  • Previously the Build Panel would be cleared if you so much as glanced at it, now it retains its content for much longer.  It might even retain its content between sessions if there’s any demand for that

Let me know about any rough edges or outright bugs you find.

Many thanks to  personalnadir who contributed lots of code and ideas to this release.

#2

Do you recommend version 2 or 3 of Sublime Text?

#3

I liked that the build panel cleared. wish had a setting to clear on every run

#4

or at lease some type of visual seperation between runs

#5
  • Fix doubling of prefixes when doing completion under certain circumstances

This is not as fixed as I’d hoped.  I think I’ve zeroed in on the real issue so I’m testing a new fix now.

#6

I use Sublime Text 3 except when I have to test Corona Editor with the older version.

I find it’s faster and actually has fewer issues than the older version because there are things they have fixed in 3 that they aren’t going to address in 2 (though they are mostly very obscure things relating to packages rather than mainline features).

#7

I’m reminded of this  :slight_smile:

The big change was that using the menu to Show or Hide the Build Panel no longer clears it.  For me, each time I do a Cmd+F10 or a Build, the panel is cleared so only one session’s output is ever in it.

Which version of Sublime are you running and on what OS?

#8

sublime 3 Mac os10.9

#9

 I might be wrong - but I suspect jstrahan means when he Reloads simulator (from within simulator) he would like the console to reload as well. Would you agree jstrahan?

I have sublime 3 & Mac os10.9 - console clears as soon as I click Corona Editor in sublime.

If that is not what you meant - then I will step in and say it would be very neat if console cleared every time simulator reloaded! :slight_smile:

Thanks,

Kreso

#10

yes that’s what I mean, kreso

#11

I agree with kreso and jsrahan, please can we keep the contents of the console UNLESS the simulator is restarted.

Since discovering Corona editor & Sublime I haven’t used anything else - it’s fast and it does what I want and need - great work Perry! It was only the clearing of the console that was a problem :) 

#12

Everyone’s like, finally, man!

I’ve pushed a good set of fixes and changes to Github so if you’re a bleeding edge type and don’t mind the occasional pebble in your shoe, you can test along with me.  Hopefully there will be few surprises and an official release will go out next week (which is what you should wait for if you aren’t comfortable opening up Sublime Text and changing the plugs and oil).

Is official release available through package control, or should we get it some other way?

Thanks,

Kreso

#13

When it’s ready, the official release will happen via Package Control.

I’ve been busy with some other things but I really hope to get the release out soon (I have a couple of debugger issues to address first).  If you are comfortable with setting up Package Control to access Github directly, you can get the latest from there but I’m being deliberately vague about how to do that as we don’t want to actively support that mode of access.

#14

Do you recommend version 2 or 3 of Sublime Text?

#15

I liked that the build panel cleared. wish had a setting to clear on every run

#16

or at lease some type of visual seperation between runs

#17
  • Fix doubling of prefixes when doing completion under certain circumstances

This is not as fixed as I’d hoped.  I think I’ve zeroed in on the real issue so I’m testing a new fix now.

#18

I use Sublime Text 3 except when I have to test Corona Editor with the older version.

I find it’s faster and actually has fewer issues than the older version because there are things they have fixed in 3 that they aren’t going to address in 2 (though they are mostly very obscure things relating to packages rather than mainline features).

#19

I’m reminded of this  :slight_smile:

The big change was that using the menu to Show or Hide the Build Panel no longer clears it.  For me, each time I do a Cmd+F10 or a Build, the panel is cleared so only one session’s output is ever in it.

Which version of Sublime are you running and on what OS?

#20

sublime 3 Mac os10.9