Closed NoXPhasma closed 1 year ago
According to documentation, if the @updateURL
key is omitted then the original installation path will be used to download file to check @version
key for update.
https://sourceforge.net/p/greasemonkey/wiki/Metadata_Block/#updateurl
It is intended to use in pair with .meta.js
file, which should contain script info and more importantly - @version
key. That allow updating procedure not to download a whole script file just to check a one string.
But I strongly beleive in nowadays developers should use streams in such cases and stopping the downloading when whole string with @version
key is received.
Also, forcing @updateURL
key to github means forcing people from other install sources to switch. Im trying to maintain a mirror at https://openuserjs.org/scripts/thomas-ashcraft/Alienware_Arena_helper Though they didn't make it easier by rejecting auto-updates because icon from our current meta info (original AWA site icon actually) isn't up to some imaginery standarts which they didn't even bothered to document.
You know... maybe we really should to force people to switch to github source. Should sleep with this thought and decide at fresh head. Maybe even someone will comment on this.
I've added a meta.js file and changed the update url to it.
That's exactly what I don't want to do - maintain another file every release.
This adds the
@updateURL
to the script with the URL to the raw js file. This enables automatic updates through the Browser addon.