Changes
-------------------

[2002.Aug.10]
 1.1.2: Very minor changes: new pop-up text when restoring message and 
        fix such that quicksave doesn't try to restore messages that
        had no content (if user accidentally presses "Compose" twice).

[2002.May.10]
 1.1.1: Added a ton more javascript fixes, focused around the problems we
        had when the Compose page was in its own window. So, to put it best,
        Quicksave should now be fully compliant with both the New Window
        and Compose In New Window plugins. Also added a fix for folks like
        myself who use the pagination feature (thanks to Cor Bosman for
        that). Finally, the Cancel button now pseudo-intelligently returns
        you to the message list if you'd clicked 'Compose', or back to
        your message if you'd clicked Forward or Reply (or Reply All).

[2002.Mar.06]
 1.1.0: Javascript bug fixes for our IE friends, plus fixes for all those
        wierd folks out there not using short tags and asp-style prints.
        (thanks to Seth Randall for making this update really easy)

[2001.Apr.30]
 1.0.0: Minor bug fixes to the old, form-based storage system. That's not
        the big thing, though. We now use cookies as the primary storage
        system. If cookies are being refused (then Squirrel shouldn't
        work, but I digress), then we still have all the old functionality
        of the 0.x releases.

 0.6: IE over-save bug FINALLY fixed (thanks DJ!), cancel button added
        to Compose's button row, plus cleaned up recovery process.

 0.4, 0.5: not officially released. Attempted fixed for IE's annoying
        over-save bug (didn't fix it). With 0.5, canceling works better.

 0.3: only fields which have values will be saved and/or restored.

 0.2: bug fixes, requirements updated.

 0.1: initial release (duh).



1.0.1 - To Do
-------------------

 - Add the option to store in cookies OR using a form. If you get messages
        whenever a cookie is stored, then you're going to be pummelled by
        this plugin. I got locked out of SM when I had notification turned
        on and I told the browser to stop taking cookies from this host
        because it was SOOO intrusive. Whoops!

 - Compress the code into something a little more managable. Right now it's
        something like 8k that's being sent to the client with the compose
        page, and that's a lot of overhead to deal with over a modem.

 - It could use some security stuff, like encrypting the cookie values, or
        making sure that we've got the same user logged in when we restore
        as we had when we saved... stuff like that. Most of this only comes
        into play if in an environment where multiple people use the same
        computer to access SM one after the other. Closing the browser
        would fix all of these, btw :)

