So Doors CS 7 is underway at last.  Development is slowly accelerating, as I still have a few more things to finish up for the semester, most prominently the defense of my Master's thesis on realtime face detection and recognition in wearable computing and augmented reality.  I also have two finals and a project, but then I'll have a nice chunk of the summer for development.  Unfortunately the 11-hour-from-now deadline in my signature is unrealistic (and will be corrected soon), but I have indeed been doing some fairly intense ASM coding.  I freed up about 2KB by consolidating routines and moving more of the internal stuff over to the DCS GUI subsystem, I've been doing general stability fixes and optimizations, and yesterday evening I more or less finished porting the popular TabFunc shell expansion (which makes the mouse irrelevant for those who dislike a mouse-based interface) into the shell proper.  I'll stop by here occasionally, but if you want more timely updates on development (and want to nag me with feature suggestions and bug reports, which I would very much appreciate), come say hi at Cemetech or #cemetech on efnet.  The topic to post suggestions and bug reports in is currently this one, and you can see some more dev screenshots in this topic.  Cheers.

Here's some eyecandy of DCS6 vs DCS7 to date for your pleasure:


PS - oh, and folder backup is indeed a priority for DCS7. Thanks for all the feedback on that particular issue.

So Doors CS 7 is underway at last.  Development is slowly accelerating, as I still have a few more things to finish up for the semester, most prominently the defense of my Master's thesis on realtime face detection and recognition in wearable computing and augmented reality.  I also have two finals and a project, but then I'll have a nice chunk of the summer for development.  Unfortunately the 11-hour-from-now deadline in my signature is unrealistic (and will be corrected soon), but I have indeed been doing some fairly intense ASM coding.  I freed up about 2KB by consolidating routines and moving more of the internal stuff over to the DCS GUI subsystem, I've been doing general stability fixes and optimizations, and yesterday evening I more or less finished porting the popular TabFunc shell expansion (which makes the mouse irrelevant for those who dislike a mouse-based interface) into the shell proper.  I'll stop by here occasionally, but if you want more timely updates on development (and want to nag me with feature suggestions and bug reports, which I would very much appreciate), come say hi at Cemetech or #cemetech on efnet.  The topic to post suggestions and bug reports in is currently this one, and you can see some more dev screenshots in this topic.  Cheers.

Here's some eyecandy of DCS6 vs DCS7 to date for your pleasure:


PS - oh, and folder backup is indeed a priority for DCS7. Thanks for all the feedback on that particular issue.

I'm glad you got back into the groove . Altough I'm a die hard MirageOs user (being the fact it's the shell I used since early 2002), I liked DoorCS style. Providing it works on the TI-Nspire and that DCS7 saves my settings after a RAM clear, it's pretty much guaranteed a place on my TI-Nspire 84+SE mode.

I also think Door CS deserves a feature on ticalc.org. It became a pretty popular shell with the time and I often hear people over here who says who use it. Heck, Quigibo even added DCS support in Axe Parser compile option

Yay, DCS7 will be coming out! I second the notion for a feature when it is released. If only we can convince the ticalc.org staff...
What all new is being added this version?

TabFuncs built-in! Folder Restore feature fully working! Masters thesis defense in fourish hours! Progress rolls on.

http://www.cemetech.net/news.php?id=383

Nice! I can't wait to use it on my calc :p
what's the new estimate on the completion date?

Password protection is a plugin that you can already download on Cemetech or on ticalc.org in the new 2.0 version.

What I was asking was if it you need the seperate program, or will it be built in, like TabFunctions is now? Cuz, if there's extra space on the third app page when Kerm is done, it would be nice to have it built in, if he didn't intend to originally.

Or, what would actually be cooler, but maybe harder to do, is to have the password program work as a sort of installer script that adds the password to the DoorsCS program, in much the same way that you run installers on a computer, and once the program is installed, you never need the installer again (unless you crash).

I kinda agree with Kerm on that last point, especially if password protection is disabled on a reset.