Hello, i’m new with corona and lua. I started to code with sublimetext + corona editor, but i’m searching something more like a real IDE.
I found this one:
I try to compile and runa corona sample with success, but i still missing:
autocompletition
debugging
Anyone can help me?
Thanks
I tried this one also, but autocompletition seems to be not so useful, and debugging is a little “hacking”: add some file to the project and a line of code, plus inspect variables only via command in console.
That’s what i figured out by myself, not spending too much time finding if there are alternatives ways to resolve these “issues”.
i tried also OutLaw (http://outlawgametools.com/outlaw-code-editor-and-project-manager/). Seems work very well. Autocompletition works better than zerobrane, but unfortunately there is no dubug. It’s a shame.
Lua Glider 2 (http://www.mydevelopersgames.com/Glider/) it’s only a payment tool. I try the trial. It’s very very “heavy” respect the others ; even LDT seems responsive like rocket in compared to that 
> autocompletition seems to be not so useful
@salvionidan, thank you for sharing your feedback on ZeroBrane Studio; do you have any more details on what didn’t work for you with auto-complete? I generally try to keep the included auto-complete descriptions up-to-date with Corona releases. In fact, the new version of ZBS (1.30, planned for next week) will include the API updated for v2015.2731 along with added handling of type inheritance for Corona types.
> debugging is a little “hacking”: add some file to the project and a line of code
I actually see it as advantage as ZBS will not modify your files, so there are no “surprises” when some auto-generated code is added and not removed. You only need to add a file to the project if you do on-device debugging; for local debugging you only need to add the line to start the debugger.
> inspect variables only via command in console.
There are several ways to inspect variables; in addition to running command in console, you can also use the stack window as it shows all local variables and upvalues for all stack frames or the watch window that takes any variable or expression and updates its values when the debugger is stopped. There is also a plugin that allows you to update watch values in real-time while your application is running.
Speaking about plugins; there are also 50 or so plugins that extend core functionality in various ways; for example, there is DocumentMap, HighlightSelected, AutoIndent, or even ShowReference that can be configured to show Corona reference for selected text.
I’m open to ideas how to make all this information more easily available to the users.
I tried this one also, but autocompletition seems to be not so useful, and debugging is a little “hacking”: add some file to the project and a line of code, plus inspect variables only via command in console.
That’s what i figured out by myself, not spending too much time finding if there are alternatives ways to resolve these “issues”.
i tried also OutLaw (http://outlawgametools.com/outlaw-code-editor-and-project-manager/). Seems work very well. Autocompletition works better than zerobrane, but unfortunately there is no dubug. It’s a shame.
Lua Glider 2 (http://www.mydevelopersgames.com/Glider/) it’s only a payment tool. I try the trial. It’s very very “heavy” respect the others ; even LDT seems responsive like rocket in compared to that
> autocompletition seems to be not so useful
@salvionidan, thank you for sharing your feedback on ZeroBrane Studio; do you have any more details on what didn’t work for you with auto-complete? I generally try to keep the included auto-complete descriptions up-to-date with Corona releases. In fact, the new version of ZBS (1.30, planned for next week) will include the API updated for v2015.2731 along with added handling of type inheritance for Corona types.
> debugging is a little “hacking”: add some file to the project and a line of code
I actually see it as advantage as ZBS will not modify your files, so there are no “surprises” when some auto-generated code is added and not removed. You only need to add a file to the project if you do on-device debugging; for local debugging you only need to add the line to start the debugger.
> inspect variables only via command in console.
There are several ways to inspect variables; in addition to running command in console, you can also use the stack window as it shows all local variables and upvalues for all stack frames or the watch window that takes any variable or expression and updates its values when the debugger is stopped. There is also a plugin that allows you to update watch values in real-time while your application is running.
Speaking about plugins; there are also 50 or so plugins that extend core functionality in various ways; for example, there is DocumentMap, HighlightSelected, AutoIndent, or even ShowReference that can be configured to show Corona reference for selected text.
I’m open to ideas how to make all this information more easily available to the users.