Now this is interesting. This will surely help me with development. I've always found it a bit of a hassle Downloading now!

He's also porting Starcraft 1 to the Nspire?? (see window title bar)

Kidding aside, this is cool. I'm glad new tools are coming out to make Ndless development more user-friendly.

Is it portable?

In the sense of being zero-install, or in the sense of being usable on Windows, MacOS X and Linux ?

Very Nice, trying it out right now

Replace nioconsole with nio_console in line 5

I'm wondering if there's a tutorial for nspire c programming?

All resources made for nspire C programming are on hackspire.
There is also a tutorial for non-Windows users in order to setup the environnement and make a hello world program, but I guess it is getting a bit old now (it still work tho)
http://hackspire.unsads.com/wiki/index.php/Main_Page

edit : wait, Extended has updated the page for Linux-users (since they can't use the sdk)
http://hackspire.unsads.com/wiki/index.php/C_and_assembly_development_introduction_on_Linux

Quote from: alberthrocks on August 26, 2012, 01:33:38 pm

Good stuff! I do hope though that ExtendeD fixes the trunk to make the old ndless building work...
(If you don't know, r632 ish is the only revision that does not have the SDK, and still has the nspire-gcc and friends work.)

Hm, what's wrong with it exactly?

Basically, the bin/ directory disappeared, so I tried to find and use another copy of nspire-gcc within another directory. I only found tools/build/nspire-gcc, so I set my PATH to that, and it failed (for obvious reasons). Building ndless itself failed too!

Interesting enough, I downloaded the latest revision, and got Ndless-SDK/ndless/bin/nspire-gcc, which works! Whatever you did, something must've worked! (Though oddly enough, I *don't* see the bin directory on the web repo: https://www.unsads.com/scm/svn/nsptools/Ndless/trunk/Ndless-SDK/ndless/)

Re: the web repo, could you fix the problems with it? It would be great to see the history of a folder/file with a single click instead of going through SVN commands. (For instance, https://www.unsads.com/repos-web/open/log/?base=nsptools&target=/Ndless/trunk/Ndless-SDK/ndless/3rd/nSDL/)

As for the repo separation... I'm foreseeing some difficulty now that I've seen the current structure of the repo. Maybe you could move the Windows only stuff to a branch or different repo, and have linked folder(s) to the ndless one? (Like this: https://github.com/Chronic-Dev/greenpois0n - though now looking at it, that's a Git repo, so I don't know if SVN has such a thing.) That way, you won't have to go through the hassle of maintaining two separate repos.

Again, great work! An IDE for Ndless development will definitely bring in some activity to the C development community here! I do have a few minor suggestions though:

• A pretty, yet thorough wizard for getting an emulator set up and ready to go. This would include having the IDE show the user the available emulators, downloading the user's emulator, dumping the needed files, and setting it up. (And in the future, if a community boot1 is created, simply extracting OS files downloaded from TI.)
• Tutorials using the 3rd party libraries. Those are rather powerful libraries, and most people getting into Nspire development are unlikely to know how to manipulate the screen buffer! They abstract away some of the not-so-nice internal stuff, so it's more dev-friendly. SDL might just be an import from the other tutorials online, with some Nspire-y modifications. SDL might be a bit too much for simple stuff, so...
• Add nRGBLib to the 3rd party libraries. It's a much simpler library, and would certainly help newcomers get into developing Nspire programs!
• Clarify that the printf() statement does NOT print to screen, and that something like NspireIO should be used. In fact, maybe it would be best to replace that printf() tutorial with a NspireIO one (using the NspireIO printf() statement)! I know that the wiki does say RS232 is needed, but I feel that not many new devs would know what it is, or even if they did, not realize that the printf() won't show up! If you don't want to take such an extreme change, you could writeup (or I could, if I have time) a NspireIO tutorial (on the wiki), and then link to it saying that this is the way to put text on the screen.
• Better API documentation + tutorials. Each function could have their own page, with a description, usage, breakdown of usage, and maybe a very well documented example (with a picture, if applicable!).
• Pictures on the wiki! I'd feel better than looking at code

(I apologize in advance if you've already implemented any of these - I haven't tested the SDK on my Windows computer yet! )

I know this is a lot to ask for, so I'm certainly willing to help do any of these suggestions when I have time. (Just tell me which ones you are too lazy to do )