Omnimaga
Omnimaga => News => Topic started by: DJ Omnimaga on June 03, 2011, 05:11:56 pm
-
On the Lua page (http://education.ti.com/educationportal/sites/US/nonProductSingle/nspire-scripting.html) from TI website that was mentionned yesterday, it mentions that a SDK is planned for 2012:
When will a SDK (software development kit) / authoring kit be available for Lua?
A. We have a conversion utility tool and documentation available today from this page. TI expects to have an SDK available in 2012. If you are interested in providing input for this kit please use the feedback link ([email protected]).
Let's hope it will be free or at least contain a not-to-limited free version. I guess it might help, when providing input to Texas Instruments, to suggest a free version. :P
-
2012 till a SDK is available :O. I wish we didn't have to wait that long but the only reason they released it I bet was to make themselves look better and because we hacked into it in 3.0.1. I bet it was very unplanned
-
Yeah I am certain it was not planned for a long while as they claim on the page. It was probably also to save their reputation.
I hope it won't be as buggy as the 83+ one, too. Several programs wouldn't even work in the emulator.
-
I hope it won't be as buggy as the 83+ one, too. Several programs wouldn't even work in the emulator.
The 83+ SDK attempted to emulate the whole CPU (because asm could be used). This one only needs to be able to run an interpreted language - no CPU emulation required (because asm can't be used)... It should be much simpler to make, but TI will probably just screw up like they always do.
-
2012? That's a long time, is there a chance we can make our own earlier? I'm pretty sure that's possible :)
-
It's possible, if the right persons (I'm not one of them) spend enough time tackling that task :)
-
It all depends on what an "SDK" means.
And we already have official and unoffical emulators.
-
It all depend on what an "SDK" means.
And we already have official and unoffical emulators.
We have Lua>Tns Converters, Emulators. All we need is to package them together and *voilá* your SDK is finished.
-
It all depend on what an "SDK" means.
And we already have official and unoffical emulators.
We have Lua>Tns Converters, Emulators. All we need is to package them together and *voilá* your SDK is finished.
Is the documentation finished?
-
It all depend on what an "SDK" means.
And we already have official and unoffical emulators.
We have Lua>Tns Converters, Emulators. All we need is to package them together and *voilá* your SDK is finished.
Is the documentation finished?
Sorry, I just noticed I confused SDK with IDE :P
-
IDE is not all that different from SDK its just lacking the documentation which we seem to have been doing pretty well with
-
Well, they have released the api documentation, and thats pretty complete :)
-
And the vast majority of said API documentation had already been reverse-engineered before they released the documentation :)
-
Wow, so TI is admitting Lua is on their calculators and *gasp* they put up a tool for changing Lua into TNS! Yay I hope it works with the CX!
-
Yay I hope it works with the CX!
Why it can't work ? (Because actually, it works)
-
I hope it works with the CX!
It does. All calculators (and also the computer software) are (unless TI screwed something up, but I don't think they did... yet) supported as long as they run 3.0 (or newer).
-
This tool had been involuntarily leaked by a third-party before TI released it ;)
Perhaps it should be made clearer in the first post that the Lua page recently created on TI's site brings nothing new ? :)
-
Well at least TI (could be) doing something good
-
Yes, that is indeed a welcome change in behaviour :)
But they probably didn't have much of a choice, even before the involuntarily leak occurred: reverse-engineering would eventually have 1) found the minority part which was not documented yet, and 2) made the 0D encryption fully understood, and independently reimplemented.
-
Yes, that is indeed a welcome change in behaviour :)
But they probably didn't have much of a choice, even before the involuntarily leak occurred: reverse-engineering would eventually have 1) found the minority part which was not documented yet, and 2) made the 0D encryption fully understood, and independently reimplemented.
I stll think we should at least do 2).
-
Unfortunately, I don't think SDK is referring to C..... :(
I'm willing to bet they didn't write much for the Lua port. They probably used someone else's Nucleus RTOS code, and just threw in a few specific commands. That means that maybe there will be an exploitable vulnerability....
Of course, I might be wrong, and they might include Asm support, which would mean we wouldn't need such things :P
-
Maybe they stole Casio PRIZM OS code? O.O
jk