Quote from: DJ_O on August 21, 2012, 11:55:17 pm

On MP OSes on the 84+, such menus also exist now.

Though the layout is slightly different; you also use Up/Down to navigate submenus.
Even if he's switching from an Nspire of 68k, the 80-86/Casio interface is pretty quick to learn.

Personally, even after learning the Casio UI, I still find the TI way of doing things much, much better. Casio tends to (ab)use the F1-F6 keys a lot, which IMO is somewhat a clunky way of navigating. Even bringing up that F1-F6 menu can sometimes be non-trivial.

As for development, things *might* get better for the Casio Prizm. With the upcoming LuaZM (Prizm Lua port) there's also a port of the libc, something that has been a big roadblock for much Prizm dev. (The only activity from before was from people using the raw API, and those who knew how to write directly to the screen.)

For the Nspire, development has never been looking much sunnier There are very nice graphic libraries, like nSDL and nRGBLib, that can be used, as well as NspireIO for console dev. (Not to mention that Nspire already has a working C library!) And of course, Nspire Lua has been very popular too

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 )

This is pretty amazing! I would be one very serious user** if you added TCP networking support!
The Nspire (and friends) would appreciate some Internet connectivity.

(For the Nspire, USB communication needs to be implemented Ndless side beforehand)

** By user, I don't mean just accessing the Internet, I also mean using it as a component for a major project!

Now that school's starting, I'm going to be programming on calc more. So could somebody who already has the Ndless SDK set up just recompile this program for the CX? Thanks a billion to the person who does. 

Done! Recompiled with ndless r632, and added this snipplet somewhere inside main():
if(has_colors)
                lcd_ingray();
Enjoy! Please let me know if the build fails/does not work.
EDIT: This uses his latest SVN trunk source code, so it may be less stable. Also, you still need his other resource/conf files, if you don't already have them.

Like I've said before, Eeems is the guy who manages the server, and he's usually quite busy, and....

To make things a bit better, I took matters in my own hands to get things working! I installed Minecraft Server Manager (MSM) for automated saving and updates**, and then copied Eeem's world data into MSM, and with some effort, the server is now updated to 1.3.1! Also, online-mode is disabled, so you can freely log in! (This will probably be re-enabled later on with some patch/mod to still let everyone in.)

** Except plugins, which are manual.

It's not very well known, but I've been hosting a Minecraft server for quite a while! It started when Cooliojazz started a MC server, and needed some hosting (and paid me for it). Since then, he has moved on to his own server, and this server became a community server (which still appreciates donations). As of right now, it seems to have a title of Omnimaga MMO MC server... maybe this should become an official Omni MC server?

Anyway, the details!

Specs:
IP/Domain: mc.withg.org
Server: Minecraft 1.25 (CraftBukkit)
Hardware: OpenVZ VPS 2GB RAM, 99% dedi to MC
Admin: Eeems
Non-premium: Yes (will be fixed, if there's demand - but it's better to support the dev and buy it!)
Mods: Tons (Minequery, Towny, iConomy, Register, Vault, PermissionsEx, LWC-Economy, Questioner, LWC, mcMMO, SimpleSpawn, MoneyDrop, TownyChat, ...)

Access (I think) is somewhat limited, but if there's demand it can be fixed.

Great stuff! I think the emphasis of "non-opinionated" downvoting is important. I know it's tempting to use the downvote for certain posts (like this one), but the downvote/upvote is designed to promote quality of posts and content, and discourage spam. More amazing projects can grow this way!

(Note to admins/mods: I haven't ever really used the downvote button much, just the upvote button - if I'm wrong about the downvote rule, let me know!)