Alternatively, if you don't have a graphics browser or whatever, click here to download it.
Alternatively, if you don't have a graphics browser or whatever, click here to download it.
You may wonder why it hasn't changed much. Well, in fact it has - a lot - the older screenshot used some very spaghetti code and was becoming rapidly unalterable to ensure it'd keep working. The newer screenshot it a complete recode and uses the tornado kernel's memory management routines which the prior screenshot didn't. Superfically it's little change - underneath it's weeks of work).
Oh, just before you all write to me asking for the JPEG of the girl above, don't bother - her name is Patricia Ford and there are LOADS of sites dedicated to her (try my links!). I think she's a total babe, although this photo of her is the best one of her I've ever seen - mind you, I have a few more that are just as good!
One minor problem though is that the latest picture's of her use too much make-up on her face. Damnation!
Here's a few icons that tornado uses:
This is what the mouse pointer changes
to when you are over something tornado wants you to press
This is what the mouse pointer changes to to indicate that clicking on the object under the pointer will cause something to happen as a result
This is an off radio icon on tornado
This is an on radio icon on tornado
This is the icon shown in an information popup window when tornado is informing the user that an application has just caused itself to be shut down
This is the icon shown in an information popup window when tornado is informing the user that an error has occured during the execution of a process which caused the program/tornado to stop whatever that operation was
This is the icon shown in an information popup window when tornado is informing or asking the user about some uncertainty or problem which came up during the execution of a process
This is the icon shown in an information popup window when tornado is informing the user of some information a process wishes to tell them
The graphic above is a piece out of
a tornado title bar illustrating
what this window has in it and
what is happening to the contents
icon represents a convertor of some sort - a black box (in this case a hat) which takes in data in one form and spits it out in another form.
icon represents a textual data stream (a red arrow is text, green graphical, blue audial, multicoloured animated) flowing between the convertor and the view of the file that the open eye represents.
icon represents a view of a file loaded in. Because this is beside the window owner icon, it means that the contents of this window are a view of a (textual) file that is currently being converted from another filetype by a convertor. Note that if the contents of this window were going somewhere else then there would be a data flow arrow after the eye.
icon is the identifier icon which tells who owns the window - in this case, it is a system window (owned by the tornado shell). The identifier is always nearest the right hand side of the title bar, and there always must be one present for all windows. The fact the open eye is beside it indicates that it is a view of a file (since in fact all files are really loaded into tornado, not individual programs). A closed eye would mean the window contains the representation of a physical device eg; hard disc, another computer, printer etc. A question mark would mean that the window is asking you something eg; typically it is a dialogue window.
Data flow arrows can come off objects (converters, file views etc) or off another data flow arrow. If it comes off an object, then the data flow is off that object. If it comes off another arrow, then the data flow coming off is the copy of that flow ie; you can watch what's going down a data flow this way.
You can also twig with the data flow using a drop and drag method. If you wanted to watch a flow, you would drag the flow arrow to the tornado viewer (or much more likely, simply position the pointer over the flow arrow and double click). You can alter flows by creating new ones, inserting new processes (eg; dump all input to disc and pass on), running one flow off another or into another and so on. You can also create pending flows, making one flow wait until another flow is complete. Or you can set a time for a flow to become active, or define a macro to create a whole network of flows from one file etc.
This is the tornado everyone thinks is hyped!