Thoughts
in
4 posts,
3 voices
jamisonf
Scriptwright
|
I noticed the script only looks for changes however some userscripts have you change something in the code yourself but this script would repeatidly say a new version is available, is there a way to exclude certain scripts? Right now i have it disabled and just run it every once in awhile, also it'd be nice if the title of the userscript linked to the userscript details page. Awesome job though, i had about 15 scripts that actually needed updating. |
Eyal Soha
Script's Author
|
The title of the user script now links to the userscripts.org page. I will work on a disable/enable checkbox for you. |
|
Eyal Soha
Script's Author
|
Okay, there's a checkbox now. Go to about:cache#scriptupdater Also, next time that you are asked about updating, if you select cancel then it'll ask you if you want to ignore this script in the future. That will turn off updates for the script. To turn them back on again go to the link above. Let me know how that works for you. |
IzzySoft
Scriptwright
|
To decrease "false alerts" on "available updates" which are not really available (due to changes the user made, as jamisonf described in the initial post), here's a suggestion: On a check, first grep the metadata. Check whether they contain the @version tag. If so, only compare the version (and not the script content). Not that much logic required (we don't need to know which one is the higher version - if it differs, there's an update. The only few exceptions, like the script developer is just developing, we can ignore here - it's still an improvement). Compare the entire script only if the @version tag is missing. Of course: If the @version tag is missing locally XOR remotely, we assume there's an update available - it's quite unlikely the author removed it rather than (s)he added it. |
