0 Members and 1 Guest are viewing this topic.
We've come a lot farther with the Prizm in six months compared to what was done to the Nspire - it took years before code could be executed on it! Also, some of the activity has been on other forums and IRC, which is why you don't see a lot of topics here. Most of the things that we've been focusing on is opening up the Prizm, not actually creating games and programs for it. The game development is probably going to bet a boost during the summer (at least I hope so...)
Oh, okay, that makes sense. I don't think Casio actually tried to lock anything up or prevent third-party development though, as TI did, so that's probably why the nSpire took so much longer to hack.
(Why would TI want to do this, anyway?)
We've come a lot farther with the Prizm in six months compared to what was done to the Nspire - it took years before code could be executed on it!
Maybe because it was blocked? Maybe because TI, besides blocking it, did not provide any SDK for it like Casio?I think you guys have gone far, but comparing it to the Nspire is unfair.
Quote from: JosJuice on July 10, 2011, 03:50:27 amWe've come a lot farther with the Prizm in six months compared to what was done to the Nspire - it took years before code could be executed on it! Also, some of the activity has been on other forums and IRC, which is why you don't see a lot of topics here. Most of the things that we've been focusing on is opening up the Prizm, not actually creating games and programs for it. The game development is probably going to bet a boost during the summer (at least I hope so...)Oh, okay, that makes sense. I don't think Casio actually tried to lock anything up or prevent third-party development though, as TI did, so that's probably why the nSpire took so much longer to hack.