I’ve been checking my old backup files on the nowadays old CDROMs from 2008 and I’ve found an scanned Rescapp draft. It’s not handkerchief based 🙂 but paper based. It’s interesting because Rescatux 0.01 came around June 2010, that’s two years later. Sometimes old thought projects come back to life. I wish that the Nowin project was alive again but it seems that the desktop systems are quite dead nowadays with all the cloud stuff. So I will leave it there as a a vaporware.
Rescapp is the main program included in Rescatux. It makes possible that the final user just uses a wizard to perform his rescue tasks. What you are seeing attached to this post is one of the first rescapp drafts. If you see the current Rescapp layout you might be astonished because it’s very different. The first draft, as you see, is very cluttered. I still like the idea of the first draft although I would be probably wrong if I wanted to switch current layout to draft one 🙂 . One thing is what you would like to do, another thing is what you can do, and another thing is what you should do.
The attached draft is written in Spanish but as it has letters in red for each one of the sections it’s going to be very easy for me to explain it. If you see it with a quick glance you will see that it’s quite technical. There are three sections about the source code: [H]: Technical Help (Source Code Explanation), [I]: Source code Edit and [K]: Original source code View. The idea is that if the Rescapp scripts needed to be edited you could do it in the same Rescapp window. You can check original source code to compare it to your edited code. And, if you are not sure about what you have typed you can always click on the [J] Obtain difference button so that you see the diff output.
Another improvement can be found at the bottom. [L] Console Output let’s you see what Rescapp script is doing in the background while performing its rescue tasks. You don’t need to open any log file, it’s all there and you can scroll it too. Currently Rescapp saves all the logs associated with your rescue tasks, in this Rescapp draft you need to save the log specifically thanks to the [M] Save Log button.
Another big difference that you can see is what we could call the status awareness. I mean, you always know what’s the current status of Rescapp. [B] Menu status shows you which option from the [C] MENU you are in. Just above it you can find [A] Steps status which tells you in which one of the [D] Steps from the current option you are. That way you can know if you are about to end your rescue tasks or if you have just begun to use it. I suppose that in the final implementation of this design both [C] MENU and [D] Steps would be hidden when running an option. Alternatively when you are not running an option you wouldn’t see: [A] Steps status or [B] Menu status.
So, what’s left? There’s [F] TIP where you are given tips when selecting an option or when being in an specific step and [G] Classic help which would have something as a manual.
Finally there is the [E] Action widget where the user is being asked some questions and at the same he’s being informed about what is happening.
So that’s it. Some of these ideas might come back to Rescapp in the future? Probably the [C] MENU one if there are so many options in the future. I don’t like tree menues at all because they seem to me as impersonal and complex. We will have to make out a workaround 🙂 .
I’m attaching other Rescapp screenshots so that you can compare how Rescapp has changed in time.