RE: [ANN] ZeroBrane Studio 0.32; now with unicode support, moai integration, and wxlua 2.8.12 upgrade

Hi

my vote would be to just have a simple text file that you manually keep up to date with what you want. This is Scite's simple way of doing this, the code completion info and the intellisense type help is in this one file

acme.os.sleep(t)   sleeps the CPU for t milliseconds
acme.os.createTimer(f, t) Creates a new timer. f = Lua Callback function, t = time period in milliseconds
etc etc

Also it would be nice to have a snippets file in the future with user defined common code blocks, that could also be a simple text file too.

ife=if | then\n\
    \n\
else\n\
    \n\
end

A few weeks back I had a look at how the love2d api and help stuff worked so I could copy, but had to give up as I couldnt figure it out :(

From: thijs@thijsschreijer.nl
Date: Fri, 7 Sep 2012 16:43:39 +0200
To: lua-l@lists.lua.org
Subject: Re: [ANN] ZeroBrane Studio 0.32; now with unicode support, moai integration, and wxlua 2.8.12 upgrade

Javier Guerra Giraldez <javier@guerrag.com> schreef:

On Thu, Sep 6, 2012 at 7:21 PM, Paul K <paulclinger@yahoo.com> wrote:
I've been thinking about using metalua to parse the source and/or to
use LuaDoc format to get parameter/return values and descriptions, but
I'm open to suggestions.

my vote is for using LuaDoc hints.  metalua is impressive, but i think
most of my code wouldn't be analyzable without actually running it.

a nice side effect is that it would encourage us to keep doc comments
up to date :-)