Your browser does not support javascript (or it is disabled.) Please use a browser with javascript or enable it.We need javascript to function properly otherwise some things won't work.
Just a quick note on the warning. You don't really need the first sentence - the second sentence says the same thing. In warnings, less is more. The longer it is, the more people tend to ignore it, strangely. It might also be cool to include a list of plugins that are installed but do not support the update check, maybe with a link back to the plugin page as a "manual check" or to contact the developer. That way, the end user knows "Yes, the update checker plug-in sees that these unsupported plugins exist and the update checker is functioning properly, the reason there is no update listed for these is that they are not supported." I don't know if that's possible or not, but it would be more user-friendly. Great stuff, there. Nice.
mb doesn't support any compatibility check for skins/theater modes. it would be just the info that mb is needed to be upgraded also.
Ok i have a very basic working demo ready. https://mega.nz/#!CFwDQRgB!jVglRERRL-8GkS6GGOKW6Wv4mp-rhF8zQxhDkg8UBOgThis is the updater file. You can try it out.You can try it on your own addon. Here is the XML file structure. Code<?xml version="1.0" encoding="UTF-8"?><addon-data> <name>Addon Name</name> <id>put your addon id</id> <version>put your addon version</version></addon-data>you can get the addon ID by going to your addon page and check the URL. you should see a number there. That is the IDThe XML file extension should be .meta, you can name it whatever you like. No need for prefix or suffix.it should look something like:Right now you can access the updater from the menu:you can check if an update is available or not. and the download button will open the addon page:This is a very basic implementation.
<?xml version="1.0" encoding="UTF-8"?><addon-data> <name>Addon Name</name> <id>put your addon id</id> <version>put your addon version</version></addon-data>
mb must hide folders which are marked hidden in file system in 'skins' folder. also it would great to have 3 tabs: available updates, ignored updates and add-ons, which don't support update notifications.
<?xml version="1.0" encoding="UTF-8"?><addon-data> <name>Taskbar Progress</name> <id>97</id> <version>1.0</version> <ignore-update>false</ignore-update></addon-data>
AvikB, i think that i meant by 'unsupported' the add-ons without metadata.
just list all skins/plugins which don't have associated .meta files on 3d tab. maybe its wont be very quickly, but its local operation, so the speed must not be the problem.
Code<?xml version="1.0" encoding="UTF-8"?><addon-data> <name>Taskbar Progress</name> <id>97</id> <version>1.0</version> <ignore-update>false</ignore-update></addon-data>the "ignore-update" tag should decide if notification will show or not. (ofc notification is not added yet) Right now you can manually set if it will notify you or not.
I don't think it's a good idea to store this in the xml because it will get overwritten every time the plugin is updated (because the .meta would be in the same zip as the new plugin). The xml should only contain values that are not changing at "runtime" of the plugin or user settings, it should be deployable as part of a plugin update.
Maybe you could support it yourself without add-on devs' help by adding a button to each add-on page that auto-generates the manifest file. Then users who want to use the "updater" plugin could download the file using the button and put it in the folder and add-on devs won't have to include it to their add-ons.
