@rittels You are right. I didn't want some of my plugins to be listed in the gallery as they are not very useful for others. However, I just learned that it's possible to have an approved but unlisted plugin which is fine with me.
Would also love to open a plugin from the URL. See discussion here: https://community.windy.com/topic/8925/how-to-document-a-plugin
It is considered a potential security threat. I though it was only possible to inject JS if the author of the plugin actively allows it, by appending a script element. I may be wrong?
This is how the query string works: https://community.windy.com/topic/13421/updated-plugins-system
The author of the plugin has to handle to query string within the plugin. There is no standard, but ..../windy-plugin-name?lat=xxx&lng=xxx to set the map center and open the picker seems logical.
@rittels said in Windy Plugins - Add to Favourites?:
You can rearrange the plugins, so that the ones you like most are at the top.
To be honest I never noticed that - embarrassing :)
It takes a few minutes for npm to update. At the moment version 1.0.2 loads, though if you click debug, it still shows 1.0.1. This happens if you update the version number in package.json, after compiling it plugin.js. The original version number is then still included in plugin.js. It does not matter at all, just looks confusing.
Amazing feedback, thanks everyone!
@rittels, the skewT is overlapping the spot forecast? I'll look into that. Man I hate cross-browser incompatibility! The error you see isn't anything to worry about, been meaning to find a way to suppress it. It's just the data points in the ascent that I didn't want shown.
Thanks for the info on the temperature discrepancy too @Gkikas-LGPZ and @Yves70, I'll have a look into that for the next version.