I have two things to inform you of and I need to know if anyone is interested.
First, I've got Civil Defense Commander, which is say 75% complete. I've got all the source and binaries for Borland C++ Builder 4 which I could package up and release as public domain code. It makes me wince to look at because there is little room for expansion and not much attention to some of the final details of the implementation. I left off at this point because I gathered it was not what I wanted. I had to think about it for some time before I got around to the Vault OS concept. Some of you from the first Vault-Co site may remember when I had photos of that posted up. It's no skin off my nose to give it away, it might be useful to some individuals and it even might get polished up if I include all the source code. I can tell you a specific path to follow to complete it, even where you can get a free report design tool to plug in to generate printed reports. I just feel like I have other things that are better directions to go in, for example Vault OS.
Second, I've got CDC.NET, which is an application I've never told anybody about. Basically, it is a .NET/ASP.NET powered shell for a complete client/server shelter management system, running under Windows with a server required (MSSQL/MySQL). It's all powered by Web services over the network and uses stateless sessions for everything. I have not looked at it in 2+ years, but I distinctly remember it being fairly complete and quite usable. This includes inventory, logs, time management and scheduling, personnel and medical records. I could have kept working on this and was pretty close to making a complete product before I abruptly got sick of it, especially when I was thinking it was pretty current tech if it would have to also run on ancient x86 hardware. I didn't want to ever mention it since it would appear to be just something else I got started on and never finished with gusto. * UPDATE * : I just had a look at it. Much more advanced than I remember. Looks like a perfectly usable complete app, in fact. You wouldn't know otherwise unless I told you from looking at the front of it.
So there are two options here. Hendo, a friend of mine for a while, the guy who always promises to run me over with a monster truck, has recommended I do a .NET version of Vault OS first that will run on modern hardware, then do the x86 version later, because modern hardware is much easier to configure and develop for.
1. Release both CD Commander and CDC.NET as public domain or open source. Kiss'em goodbye and never look at 'em again. Stick to working on Vault OS in QNX Neutrino for x86 PCs in DOS.
2. Release CD Commander as Open Source, then do the work needed to package up CDC.NET and release that as a test version of "Vault OS for Windows."
There's one more interesting twist to add to this. You can run a real .NET application on a Windows platform with an embedded HTTP browser as the client. Above this browser window you could put any kind of Winforms/Toolbar/Tabbed/Menu you wanted to launch things like a local monitor for I2C sensors like I was talking about for Vault OS in DOS. There's also the potential there to submit local sensors to the server in the background so they are available to all other machines on the network.
Finally, considering what I already have running, this is much easier to develop than my grand plans for Vault OS in QNX Neutrino. It's coming along well but of course you're still talking about ten hours of coding in QNX to duplicate functionality I can perfect in ten seconds by dragging it from the Visual Studio IDE and dropping it on the design window.
Any feedback much appreciated. If it's not obvious by now, I always have more ideas than time.