I'M not sure. It seemed like it was them that wanted info on how we did our stuff.

Also while they may be more open to third-party development (not sure yet), they should really spend more effort at optimizing their BASIC interpreters. Heck, maybe someone could write a new one and send it to them?

That needs to be done for the nspire too.

I don't think there's room for complaint on the basic front, compared to the nspire At least it has Pt-On

Actually the Prizm doesn't have a Pt-On command. Just Pxl-On. I'm hoping though that basic gets faster in the future as only OS 1.00.100 is out right now. Later versions might even overclock the proc. but then again, TI didn't do to well with making newer, faster OS's. eg. OS 2.53

Quote from: willrandship on January 11, 2011, 05:35:12 pm

I don't think there's room for complaint on the basic front, compared to the nspire At least it has Pt-On

Actually the Prizm doesn't have a Pt-On command. Just Pxl-On. I'm hoping though that basic gets faster in the future as only OS 1.00.100 is out right now. Later versions might even overclock the proc. but then again, TI didn't do to well with making newer, faster OS's. eg. OS 2.53

Someone could maybe write a new interpreter or a parser hook that installs sprite commands to the Casio BASIC, like Doors CS, xLIB and Celtic did for the z80 calcs. Heck, maybe an entire interpreter could be done, although that could be complicated. A new language would be welcome as well, but not only C. We need something like C, ASM and Axe or BASIC, because some people can't stand ASM and C and will be singled out. However, that stuff would probably be for later, I guess.

Quote from: DJ Omnimaga on January 11, 2011, 09:35:01 pm

Why did you just quote me without saying anything?
Whoops! I must've wrote what I was saying inside the quotes.

Lol I see now. And yeah I agree. The Nspire is really in need of new commands like getkey, Output and pxl-On. I think for Nspire BASIC the real issue is not its speed, but rather its lack of decent display/output or key input commands.

darn this sucks. What about an home screen snake? Also, is text drawing on the graph screen very slow too? You should check if pictures are supported and how they behave. I am curious if text sprites could be used on the Prizm. On the 83+ people used them to draw graphics faster.

On the 83+, for example:

ClrDraw
For(Z,0,7
Text(-1,8Z,0,"LLLLLLLLLLLLLLLL
End
Storepic 0
For(Z,0,7
Text(-1,8Z,0,"SSSSSSSSSSSSSSSS
End
Recallpic 0

Gave some interesting results sometimes. On the 83+, pic recalling uses the OR logic, though. If Casio Prizm pic recalling uses Overwrite logic, then we can forget about that type of text sprites. Let me make a screenshot.

EDIT: Screenshot: