Parsable output for Thandy
In order to make it easier for an external application to know what Thandy is saying, there should be a switch in the Thandy client to make the output uniform.
I have in mind something along the lines of: One message per line with the following format:
::
Where: is arbitrary number id to easily recognize the message we are dealing with. For example: 1: error, 2: updates available, 3: updates downloaded, 4: download progress, 5: start download, 6: available packages for update, etc
is a verbose message, or the bytes downloaded if it's a message with id=4.
If this sounds like a good idea I'd draft a more formal spec for it.