Posts made by ivo

Dear Windy.com plugin developer

We are refactoring Windy.com client codes to Typescript, which is superset of Javascript. This will enable us to develop features faster, with less errors.

During this process, it is possible that, that some part of Windy Plugin API will be changed.

In order to enable smooth transition to this new version of API we need some cooperation from you:

1) Please publish your plugin source codes to GitHub (the address of github repo is part of package.json). We would like to see how you use Windy.com plugin API, or help you later on to make transition. It could also help us to design new Windy.com plugin API.

2) If you actively maintain your Windy.com plugin, just drop the line below in this thread, so we could see, that we can count on you.

Remember, that you do not need to know or learn typescript. We plan to change just plugin API.

@idefix37 Arctic forecast is technically quite difficult to realize.

So for now, we have launched it w/o it, and we will see later.

M A G N I F I C E N T 👏

@ting1990 Yes I am working on this

@Korina Can you put this to our issue tracker

@cphoenix This is basically strategy of payment gates, we use. Apple, Google, Fastspring.

We just set the price, and they do some magic calculation, that is beyond our reach.

Windy.com has already more than 8 developers and I, personally, should be just doing CEO job. But I could not resist the temptation. Few month ago, I have learned SwiftUI, and personally programmed Windy.com app for Apple Watch (not bad for being 47y old Internet veteran).

I have put there goodies, that should be on your wrist:

• Compass with forecast wind rose
• METARs, with super handy "notify me on update" button

As soon as we will see some first user feedback @SimonUrbanek (who overtook my iOS programming job) is willing put more functionality to it.

So enjoy Windy.com on Apple Watch and let us know how do you like it.

A note for Android users:
As much as I try hard, I do not know, or see, anyone wearing Android watch. A lot of my friends have some kind of sport tracking (Gramin, Coros etc) smart watch. But not a single Android watch out there.

@Korina Let's add this buf to Bug Tracker with medium priority and assign it to @SimonUrbanek

@manninwind Version of Watch OS, and your Watch?

Although we have have not encountered problems with Windy Widget on any of our testing devices, we consider your Widget complains very seriously.

In Windy Widget we have discontinued old technology, that was used by our widget (Apple prohibits new apps to use its old technology UIkit) and replaced it with new technology Swift UI as was requested by Apple.

It seems to us, that this is quite novelty and a lot of thing still does not work. Some issue can be our own BUGs, some issues are part of iOS BUGs. iOS API is also changing rapidly from version to version, which makes things more complicated.

If we are unable to replicate the bug we have a very hard task to fix these widget issues. But anyway @SimonUrbanek our iOS guru is working hard to make the widget great again :-)

Please be patient

We take this issue seriously. The fix is already in pipeline to be approved by AppStore. BUT we are not sure it will work since we are unable to replicate the BUG on any of our testing devices.

@jakubvrana Super. Dame pristi tyden videocall a domluvime se?

@graziano_vannini WOW

MAYBE, I say MAYBE these long decimal numbers make problems.

We are unable to replicate the bug so we just guess.

Anyway fix is on its way, I hope it will work.

Any chance to send us screenshot of this variables?

Go to Menu -> Error console (at the bottom of menu) -> Native Aps

We will look at this

Unfortunately we do not use data from PWS and we are considering discontinuing this feature.

@lsisca Will look at it

@ting1990 great tips thx

@jakubvrana Vypada to dobre. Nechtel byste to "publikovat" nikoliv jako plugin, ale jako oficialni soucast Windy. Tj jako interni plugin. Nahradili bychom timto nasi POI vrstvu paragliding spotu.

Nicmene asi by to chtelo udelat celosvetove.

@davink Publish it on npm and do not announce it. Authorize usage on the backend that will be avbl only to you customers.