The Casio Prizm is a powerful calculator, great for both math and playing games. It is particularly great for programming, and for months thoroughly bested the TI-Nspire calculator in offering ASM, BASIC, and C programming. In an attempt to reduce criticism of their apparently anti-student stance, Texas Instruments improved the TI-Nspire to run Lua programs. Lua is a "fast, lightweight, embeddable scripting language," an interpreted procedural language. The language has allowed budding Nspire programmers to quickly write games and programs without needing to use a computer.

I am happy to announce that I am now bringing Lua to the Casio Prizm graphing calculator, in the form of a full-featured Lua interpreter. After days of porting, rewriting parts of libc (including the longjmp/setjmp system), and learning some SH4 assembly, I am proud to present the first screenshot of the interpreter successfully running on a Prizm. Special kudos to Juju for the PrizmIO library, a port of an Nspire I/O library for C programmers. As you can see from the screenshots, this is just the raw interpreter; although it understands Lua syntax and can parse/lex the language, load libraries, and recognize incorrect code, it is almost entirely lacking in functioning libraries. From here, I will be porting over each of the standard libraries, starting with numbers, strings, and I/O. Please feel free to share thoughts and suggestions here or in the original Cemetech thread. Bonus features: Planned transparent support for Nspire and Lua FX programs.

Nice, I will definately be watching this project closely.
This will definately help bring WZGULIB to prizm, at least make it easier.

Hmm, i wonder how hard it would be to port WZGUILIB to LuaFX...

Quote from: jwalker on August 17, 2012, 06:49:07 pm

Nice, I will definately be watching this project closely.
This will definately help bring WZGULIB to prizm, at least make it easier.

Hmm, i wonder how hard it would be to port WZGUILIB to LuaFX...

My estimation... simple. But then again I created it so I know all of the underworkings. Basicly, It would be easiest to 1) implement classes (a must) 2)rewrite the drawing code to work on the specific platform(gc:drawRect() needs to become whatever draws a rectangle) 3) figure out how to make the interpreter use events/callbacks for all of the on. events. and 4) if no mouse, either create one or dont worry about it, I added functionality so you dont nessiceraly have to use a mouse anymore (can also use the enter key to do 'clicks')

I would also be willing to help port it.

EDIT: now that I thought about it... Im going to write a section into the new documentation that I will release with the new version that will talk about the above and how WZ works...

Nice project !
If you need any help with implementing the TI-Nspire API just ask me, I've ported it to various platforms before

@jwalker, if you implement the Nspire API in Lua FX/ZM there is no need to change your code

I think that classes use setmetatable...
I could be wrong though

I think that classes use setmetatable...
I could be wrong though

Yes, I know, that's why I mentioned it. We can't port classes until it is integrated.

Quote from: jwalker on August 18, 2012, 09:40:32 pm

I think that classes use setmetatable...
I could be wrong though

Yes, I know, that's why I mentioned it. We can't port classes until it is integrated.

I wonder how they got away with out having to use metatables, as they are used quit a bit.

Oh, didn't know it didn't have setmetatable ...
Metatables are a very important thing in Lua ... and without it it's much much less powerful.

Anyway, pretty sure LuaZM will have it