@AnToX98: Wow, thanks and congrats to you! My french is very poor but I undestood the most, really nice review! Maybe I'll add french translations for the great french community!

PS: Just noticed that "Skript" is actually german... I meant "Script"...  Now I can replace that dang letter everywhere! 

Oh right at first I thought it might have been a mistake, but then I thought it was intentional, for a unique name to your program!
Great news on v0.3! I have never needed to use [[string]] before. I'm not sure what it does.

@jwalker: I think this is not possible as long as TI blocked all functions to use the file system. Also user-defined libraries are not supported.

It is, you place a document with public variables in the library portion of the Nspire and then call using the Lua var functions. You would just have to write a standard for how code can be imported, and boom you have library like functionality.

@jwalker: Wow, didn't know that! I'll do some research about that. Is that function available in apilevel 1 and 2? That would be a nice option to kinda use the file system!

Here is an example : http://ourl.ca/10565/242834

@jwalker: I like your idea of importing code from a library and I'll start working on it tomorrow.
@Levak & adriweb: Thank you both for the links, now I understood the concept.
Question:
- To make a library with sourcecode entirely loadable the whole code has to be saved as a string and saved in a variable? And then use var.recall("file\\var") to get the code as string?
- What happenes if the string is too large to load?

Ah, ok, thank you very much! That feature is very easy to implement then! I'll just make a dialogue to set file and variable to load and then I'll use the paste mechanics to insert it

Congrats, quite awesome


Feedback :
- There are a few useless bits like "if xxxx == nil" and "if xxxx == true" etc. (can be replaced respectively bu "if not xxxx" and "if xxxx")
- The .tns file contains a large amount of debug/useless variables in Basic, you should clean that up
- What about making the selection mouse-based too ? (it'd feed more natural on all platforms, then, in addition to what's available now)
- Awwww you put all the sizes/coordinates in absolute values So, in Computer View on the software, it's still calculator-sized When you have some time, don't hesitate to convert all that to relative values (fractions of pww and pwh (platform.window:width()/height())
- I haven't yet looked very well at how you handle the font but could you think about making all the letters even-spaced (still monospaced, sure, however a bit less space in general between the letters ?). Also : you should add "S" to the list of letters to add an offset.
- For compatibility reasons, you should try to avoid gc=platform.gc() and look at this replacement for 3.2 (in conjunction to this for 3.1)
- Some autocompletion would be very nice too, maybe with a "popup" list as you type, that completes when you [tab] ?

- How to check and delete those variables?

Usually, in a math page, to see them : press the var button, or Ctrl-L. To delete them : just do a bunch of "Delvar xxxx". But seeing the amount of variables you have here, you should just create a new .tns and copy/paste the lua page onto the new one, so there won't be a single basic variable anymore (until your scripts makes some)

- Yeah, I thought about mouse-based selection but then I thought: "Why would anyone use the ported Script Editor when he could just use the original one on the PC?!"
- Same as above

Well, then it'd work on the iPad too, for example

- The problem here is that when I reduce the space between the letters even one pixel, Upper-case characters like "W" or "G" or "M" would overlap each other and the code wouldn't be readable anymore...
   About the "S": I just forgot to call __mG.initialChrOff() after changing the font, I'll fix that

Ok

- I've set apilevel='1.0' for compatibility reasons, the new withGC doesn't work here (?)... But maybe I'll make a 3.2 Version of the Editor some day...

If you "compile" your lua code with Luna and don't set an apilevel, then the script will work under all 3.x OSes. Then it's yoru job to detect what features are available. For example, detecting if we are on 3.2 (apilevel "2.0") is easy : if platform.withGC then .... end    or :   if platform.registerErrorHandler ....   
So that way you can have things that work on all platforms and newer versions can have more features if available

- I like the Idea an autocompletion, but that is huge function and I think I actually used EVERY user-caused event

Well, still, it'd be uber cool (and it's not even done correctly (pretty much the same as if there were none) in the computer software !)

PS: I know the code is far from perfect, I am still new to lua (and even to programming in general) and I'm still far from knowing all opportunities of lua. You may like posting some improvement proposal on the code. Thanks for the feedback!

It's pretty good core already, especially if you're new to Lua