On Feb 5, 9:41 am, SpaceMonkey <[email protected]> wrote: > Previously i simply right-click on greasemonkey, manage user script > and then i could add or remove pages from my chosen script... > > Now it seems... that i have to start > physically typing things/changing things??
It's telling that out of about 3 million active users of Greasemonkey, we've only seen a dozen or so users complaining about this change. That tells us that very few users (less than 0.001%) have a need to edit the list of sites and/or pages a script runs on. So let's look at this another way. *Why* do these users need to change the @includes? Reading between the lines of some of the complaints, my guess is that these users are using some website where they want a script to only run on certain pages, which the script author cannot pre-define. I'll make a bunch of assumptions here: 1. The website is a game. 2. The game has multiple pages, perhaps for towns or armies or some other entity. 3. These entities have arbitrary names that are part of the URL. 4. A user wants a script to only run on their own entity, and not on opposing player's entities. 5. Because of the arbitrary names, there is no way for the script author to define which pages to run on. 6. So the user must change the meta-data to tell the script which entities to run on. Now here's the rub: 7. The user previously used a feature of Greasemonkey (the scripts dialog) to edit the list of pages the script runs on. 8. That feature of Greasemonkey changed in a way that it is now undesirable for non-technical users to use. 9. In addition, any changes the user now makes will be lost next time the script author pushes out an update. Is there a better way? YES! The script author could add a mechanism in the script, where it could ask the user what entities to run on, and save that list via GM_setValue. The script would be have an @include to run on the entire website in question, but then one of the first lines of code would be a conditional that exits immediately if the document.location is not on the previously saved list. The point is, instead of looking at the changes in Greasemonkey, maybe there are changes that can be made to the script(s) that would eliminate the problem. Lil Devil -- 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.
