I wouldn't put the end/then tokens invisible...........and i like the small font A LOT more. but yeah, great job!

They are in the Omnicalc readme: https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CC8QFjAA&url=http%3A%2F%2Fwww.omnimaga.org%2Findex.php%3Faction%3Ddlattach%3Btopic%3D11145.0%3Battach%3D10138&ei=MFPDUd_BKOqF4gTE-IDgDw&usg=AFQjCNH_0vCkoKVimvM5L2Cw-KCTTJaplQ&sig2=1OGpbjk2CJs6IGq1yST50w&bvm=bv.48175248,d.bGE
And looking nice

Have you considered adding code folding to the editor?

The editor already takes over 7000 bytes of memory. I also need to get the editor working for Grammer 3 programs before I can really progress with making the interpreter. If I can, I will include the editor with Grammer 3 (if they fit). They do share a bunch of the same code, so that should make it easier.

EDIT: @ben_g: What do you mean by code folding? Do you mean like hiding blocks of code unless the user clicks on it to expand it? If so, then yes, but it won't be easy to implement for the BASIC editor.

Yes, hiding blocks of code like the inside of functions or loop, so you will for example only see:
[+]function doSomething(argument) {...}
And if the user presses the

• icon, it should show everything inside the function. It can be really usefull if you only use a single source file, because with code folding, you have to scroll trough huge portions of code less often.

@DJ_O: That is the main reason for why I want to keep it separate. For people that only want to use Grammer 3 programs, the extra flash page for the editor is kind of a waste. Whereas for developers, it is useful. Plus, the editor app should be functional on its own.

That said, I only have 5800 bytes of code space left and I haven't even started the editing part of the editor I will probably remove the variable width font and if users really want to use such a font, they can load their own. Also, for the indenting, I have come into a problem that I am trying to fix. Trying to scroll backwards isn't working very nicely at the moment for the indents, but I am hoping that I will have a fix. However, the perfect solution might cause a hit to speed for the editor (scanning all of the code before it to figure out the indent). For now, here is a screenshot of viewing the code

I personally hope that the fonts are monospace, since otherwise it can be annoying to edit in-game text (aligning it properly, I mean), or in the case where someone decided to use the editor for BASIC, editing string-based maps (like in Illusiat 13)

Good luck