Moreover, it seems that TI secures more and more their OSes, so I think that ndless 3.2 won't be here before a while, despite your amazing work.

I don't think they'll ever make a secure OS, as long as ExtendeD is motivated and has time there will be Ndless

Anyway, I thought a lot about this last night, and it would be stupid to stop calculator programming.
I might not stop this project, but it is paused for sure (for at least one week).
I still feel discouraged, but I do want to help the community, and it seems that giving up isn't the right thing to do.

I like your project, and if programming isn't fun for you at the moment, just make a pause and program again when it's fun again

Indeed, TILP doesn't have that kind of egregious misfeature.


FWIW, there's a bit of potential in making new GPL'ed Nspire linking code, this time in C++ (using std:: facilities to replace Glib where applicable, and be neutral to whatever UI tookits people would want to use on top of the library), borrowing information from the libti* + tilp code base (which is the best available source of information). Without support for TI-Z80 and TI-68k (for which any evolution from TI's side is now over), and the associated cables, file types, character conversions, etc., the code base would be massively streamlined.
But I think that for instance, the pattern of using structs containing function pointers should be kept.


EDIT nearly two weeks later: last week-end, I spent several hours experimenting with stripping TI-Z80 and TI-68k support out of TILP. As I had predicted, the libti* + tilp code base was massively shrunk, even without spending time thoroughly purging the code base (lots of low-hanging fruit remain: dozens of references to various TI-Z80 and TI-68k models remain, as do hundreds of lines in the error handling code, and other code which does no longer matter in a code base which doesn't support the older models anymore): from ~78K lines in .c and .h files (libti* + tilp CLI/GUI, I merged everything together in a single folder), the code base shrank to ~35K lines.
Of course, the binary resulting from the build of the stripped code base can communicate with my Nspire CX CAS

I just decided to resume this project.
(BTW, I also resumed GravityGuy development and nSpaint)

I don't think that it will be really fun to use, but it's a nice challenge for me. I hope that it will be playable...
Anyway, I kinda optimized the display.
I can now draw a lot of cubes with a decent speed. (~1000 cubes in 0.2 sec)

But I really need to use the timers to slow down sometimes... When there's almost nothing to draw, the camera moves incredibly fast.
Does anyone know where I could find some documentation ?

Test ALL the addresses
http://hackspire.unsads.com/wiki/index.php/Memory-mapped_I/O_ports

Timer 1, Timer 2, and RTC.
The choice is up to you.
Beware on the emulator, it seems that the RTC can't be modified since it is based on the system (windows) time.

What is RTC ? If that means Real Time Clock does that mean there is a clock on the Nspires that I never noticed ?

I just decided to resume this project.
(BTW, I also resumed GravityGuy development and nSpaint)

I don't think that it will be really fun to use, but it's a nice challenge for me. I hope that it will be playable...
Anyway, I kinda optimized the display.
I can now draw a lot of cubes with a decent speed. (~1000 cubes in 0.2 sec)

But I really need to use the timers to slow down sometimes... When there's almost nothing to draw, the camera moves incredibly fast.
Does anyone know where I could find some documentation ?

Glad to see you didn't quit everything because of TI
(Also, 1000 cubes in 0.2 sec is incredibly fast )

Test ALL the addresses
http://hackspire.unsads.com/wiki/index.php/Memory-mapped_I/O_ports

Timer 1, Timer 2, and RTC.
The choice is up to you.
Beware on the emulator, it seems that the RTC can't be modified since it is based on the system (windows) time.

Thanks !

What is RTC ? If that means Real Time Clock does that mean there is a clock on the Nspires that I never noticed ?

Yes...
A while ago, with ndless 2, I made a little program to use it, but I never finished it.

If you get minecraft to work on the CX, you win.

I hope I will
But don't think it will really look like the PC game : much slower, no textures, no nice physics...

wow, nice ö i tried it on my cx Cas and saw on the upper 1/4th of the screen that house, with the front wall green, the left wall blue and the floor pastel green

i couldn't move, but as you said it wasn't supported yet i had to try it out xp

but seeing the screenshot it really shows a lot of its potential, since you can create a complete 3D world..

I tested it on my non-cx cas, and movement and camera rotation worked and it didn't crash
But it was a bit confusing that the screen was empty until I pressed a key.
Keep up the good work