Am 05.10.2012 00:21, schrieb Anthony Lieuallen:
On Thu, Oct 4, 2012 at 5:57 PM, Brian Moore <[email protected]> wrote:
I am MAD as hell, WHY did this happen?
Because sometimes human beings are fallible.
How about implementing a warning: generate a hash of the script source
during installation and safe it in the config.xml.
Then, add something like a flag "updateCustomCode" for each script in
the config, which defaults to "false".
Rehash the script file content before an update and require the user to
do anything confirmative if install hash and current hash do not match:
On mismatch and if that uCC flag says "false", display a message box:
-----
Confirm update
-----
A new version of the script "<name>" is available, but it seems you
customized the code.
Updating will overwrite your changes irreversibly! Update the script anyway?
[ Yes, always ] [ Yes, once ] [ Not now ] [ No, never ]
-----
Answer 1: Update, set uCC flag to "true".
Answer 2: Update, set uCC flag to "false".
Answer 3: Don't update, set uCC flag to "false".
Answer 4: Don't update, set uCC flag to "false", disable "autoUpdate".
The flag can be altered from the script's context menu ("Update if
customized") in the script manager.
Chris
--
You received this message because you are subscribed to the Google Groups
"greasemonkey-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/greasemonkey-users?hl=en.
