Very cool

I believe I don't have many things to say about the code layout, at least from what I quickly saw it looks well indented and pretty clear to read (classes and good (enough) seperation from code and paint )
What editor did you use, btw ?

And I like the intro

(I may have a few optimizations, for example, you already make good things, like localizing things etc., but here is a mistake :
function Player:tick(del)
    local floor,abs=math.floor,math.abs
...The point of localizing the math functions is to not having Lua access the math table. Here it's still being accessed at each tick You could simply put the local out of the function
Sure, what you do is already better than nothing since the local version will be used for the loops calculations, but anyway, let's go all the way
(and localize every math functions you use, btw, it can't be bad.)
Also, I see you declare functions within the paint function... why ? I suppose you can just put them somewhere else (and add parameters if needed), so they just get defined once, that'll speed things up.

One more thing (but you already know about that ) : Computerview/iPad support

If you want/need a string.ulen function, here you go :
 
function string.ulen(s) return select(2, s:gsub('[^\128-\193]', '')) end
(from https://github.com/Pogs/lua-utf8-simple/blob/master/utf8_simple.lua )

Sure, but for those who have it installed, the features is available and for those who don't, it's just "hidden" (or does nothing).
Detecting if ndless is installed is just doing : "if ndless then ... end", I believe. (that's because Ndless adds a global table called 'ndless' to Lua)


But that's not the "hard" part. The actual ndless hook (lua extension rather) that makes a proper .tns from a script is doable, I assume, but it would take a bit of work...


(@mdr1 : comments*)

Quote

Although a screenshot feature within the game would be cool (if it's not there already, I don't know )

I had implemented it once but lost the code somehow (it was before v0.7.2, when I moved to git). But it's on my todo list again!

Maybe a part of that could help (instead of recoding this feature from scratch) : http://tiplanet.org/forum/archives_voir.php?id=12264
(also, I like the Ctrl-capture shortcut ... )

Quote from: LDStudios on July 08, 2014, 09:06:38 pm

-Ability to save custom themes

Indeed, it works fine on the emulator but doesn't on the handheld. The problem seems to be that var.recall apparently doesn't work in the first call of on.activate. I hate that TI doesn't mention such things in their guide and have such differences between emulator and handheld...    I'll try to find an other suitable event for initialization that fits all needs then... 

TI does warn about this kind of stuff for other functions... but apparently they forgot this one ?
Anyway, on.resize makes a good init functions.


But all that's obsolete with 3.9 where you can call any Nspire API function without having to worry if it's going to work (it will, as they kind of fake a first initial lua script setup, then launch the user code, so that the API is indeed ready.) So, basically, you're able to make an init() function and call it right after and whenever you need it.

can't get tired of this 5-hour long mix :

I included the Windows Visual Studio solution this time because its where I do development so it kind of belongs in the package.

Ha, pretty cool ! And nice job again in general

Just for fun, I ran PVS-Studio (static analyzer) on it :
33 level 1 warnings, 16 level 2, 379 level 3... Quake 1 source is fun ....

Examples:

DJ : what you don't understand is that the program is already 6 times faster (according to latest aeTIos's tests) on GS calcs than on color calcs at merely the same frequency (120 MHz for GS vs 132 MHz for color).

In case you didn't see :

I decided to un-overclock my calc and re-run copyscreen1000times.12:53 seconds.

(Or well, I'm not sure where you see this '6x' faster )

GL&HF anyway ^^