On Feb 10, 4:42 pm, ArmEagle <[email protected]> wrote: > But that wouldn't be enough for the people that want to update the > script and keep their custom rules (regardless of whether that ever > worked or not).
Very true, but even in older version of GM, updating a script would remove all of your custom rules anyway. > The XML file is probably going to stay anyway, because it is easier to > parse just that file than to parse all scripts. No I really don't think it will or should. Right now it is basically a cache of what is in the script, with the addition of storing whether the script is enabled/disabled. > So the custom rules could still be stored in the XML file. Make it so that > isn't > overwritten on a reinstall/update of the script, but it is by manually > editing the script (or so). And possibly some button to export the > custom rules into the scripts (though whether that will have to > replace all rules in the script or just add to them is another issue). Sounds really overcomplicated. I also don't like the idea of keep two sets of rules in two different places. I'd rather keep them in the file and just mirror them in the XML file. > A custom rule edit UI could be opened through the context-menu of a > script entry. Yeah, that's what I was thinking. -- 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.
