Would be nice if we could have syntax coloring, code completion, project/build support and debugging capabilities for Lua.
More ideas?
Would be nice if we could have syntax coloring, code completion, project/build support and debugging capabilities for Lua.
More ideas?
Hi,
+1 for this question. Maybe there is a way to add Lua code completion support to Mosync IDE, especially for MoSync framework classes and functions?
Thanks.
Cheers!
Anyone out there tried the Eclipse plugin for Lua with the MoSync IDE?
Best, Micke
Yup, seems to work ok.
Choose Help | Install New Software, then point to this site for your platform:
http://luaeclipse.luaforge.net/preview/update-site/
Havent had a huge play yet - but the syntax highlighting seems to work ok...
Thanks for the info!
Best, Mikael
Hi Mattias, Mikael, and others,
I've been working on a Lua IDE for the last couple of months and what we have now includes syntax coloring, code completion, project filetree support, local/remote shell, debugging capabilities for Lua, as well as some other interesting features. My main audience is the educational market, with a focus on middle and high school students; as the result, I wanted the product to be simple and straightforward to use and still be able to show all the power of Lua. After I struggled with getting Lua for Eclipse to work, I also wanted it to be a small and lightweight package without any external dependencies. The IDE is written in Lua itself and can be easily improved and extended (it is based on Estrela editor, which is based on wxLua).
The IDE includes initial support for debugging mobile lua applications using Mikael's code. The MobDebug remote debugger that the IDE ships with allows to load and debug mobile lua apps. The sample application I provide (LuaRemote: https://github.com/pkulchenko/LuaRemote) connects to the IDE, establishes the debugging session and then loads whatever Lua application is in the current editor window. You can then use all the regular debugging functions to step through the application, set breakpoints, run code in the interactive shell (will be executed on the phone or in the simulator), and look at variables. There are still some limitations because of the event-driven model and the lack of socket select()-like call in MoSync (http://www.mosync.com/content/there-analog-select-mosync-sockets), which need to be worked on.
I also wrote a simple script that can be used for rudimentary automated testing (https://github.com/pkulchenko/MobDebug/blob/master/examples/autotest.lua). It allows to load an application and execute it with debugger commands scripted (including ways to run tests on those commands). You can use LuaRemote to connect to that test server, which will run the commands and provide a report as the result of the tests.
The ide is available here: https://github.com/pkulchenko/ZeroBraneStudio (zip and exe here: https://github.com/pkulchenko/ZeroBraneStudio/downloads); MobDebug is available here: https://github.com/pkulchenko/MobDebug.
Give it a try and let me know how it works for you.
Paul.
Hi Paul,
Thank you very much for sharing this! It sounds very exciting.
Regarding the camera, there was a bug in the camera API that is fixed, so I will give the Lua Camera example app a try again.
Best regards, Mikael
Hi there,
Just thought that you might want to give Lua Development Tools a try. It is installable into the mosync IDE by referencing the following update site: http://download.eclipse.org/koneki/updates-nightly
You can get more information about the features provided by LDT at: http://www.eclipse.org/koneki/ldt
Cheers!
Hi Benjamin,
Many thanks for this info! Looks very interesting.
Once MoSync 3.0 is out, I will give more attention to the MobileLua project.
Ver best regards, Mikael