2013-03-17, 20:45
I have a small addon (almost) ready that checks the installed version against an included file in JSON format.
If it finds that you are running an older build than is specified in the file it throws a pop-up advising you to upgrade to the next available stable/rc/beta/monthly build that is available.
Of course with some smart checking that it doesn't tell you to upgrade to a beta if you have a stable installed.
Tested from Eden11.0-beta1 and up.
Updating this fairly simple, just update the include file with the new build versions and push update to repo.
If some one has disabled their auto-updating of addons they are of course out of luck but i guess they are missing a lot of other updates as wel like scrapers.
So with this there is no callback to the server needed at all. The file is in JSON format so if decided it should be hosted on our server that's of course possible too with a small script adjustment. I think just pushing an update when needed is less stressing on our servers than the script keeps checking it online.
User can select if it will ignore the next available update so he won't be bothered until there's a succeeding one available. If they won't want to receive notifications at all they can always just disable the addon. It will run as a service at startup or once a week (can be hardcoded configured of course).
Distribution for older builds is as easy as putting it in repo and add this as dependency of our default scraper for example so it will be installed for everyone (in that case we need to detect that it's actually using our versioning so it won't bother people running OE for example).
Thoughts opinions if this is something we want (so i know if need to finishing it)?
If it finds that you are running an older build than is specified in the file it throws a pop-up advising you to upgrade to the next available stable/rc/beta/monthly build that is available.
Of course with some smart checking that it doesn't tell you to upgrade to a beta if you have a stable installed.
Tested from Eden11.0-beta1 and up.
Updating this fairly simple, just update the include file with the new build versions and push update to repo.
If some one has disabled their auto-updating of addons they are of course out of luck but i guess they are missing a lot of other updates as wel like scrapers.
So with this there is no callback to the server needed at all. The file is in JSON format so if decided it should be hosted on our server that's of course possible too with a small script adjustment. I think just pushing an update when needed is less stressing on our servers than the script keeps checking it online.
User can select if it will ignore the next available update so he won't be bothered until there's a succeeding one available. If they won't want to receive notifications at all they can always just disable the addon. It will run as a service at startup or once a week (can be hardcoded configured of course).
Distribution for older builds is as easy as putting it in repo and add this as dependency of our default scraper for example so it will be installed for everyone (in that case we need to detect that it's actually using our versioning so it won't bother people running OE for example).
Thoughts opinions if this is something we want (so i know if need to finishing it)?
