Improving Sailfish-Weather

As Sailfish-Weather is now open-source, let’s take the opportunity to create a wiki to share our thoughts and elaborate some new features.

Share the code with another project

Not sure how feasible this idea is, but as we have few resources we could share some code with apps from another platform (like Ubuntu Touch or KDE Weather).

Allow multiple provider

Pro

Contra

No resource to maintain various provider

Requires:

  1. Either migration from existing (Foreca) internal API/schema (Weather and Location Models) to a generic/neutral one,
  2. OR any implementations for other providers to re-use the existing models and schemas (modelled on what the Foreca API provides). This may mean missing features (but the model can be expanded later).

For reference, here’s what Foreca returns when asking for the weather at the current location (source:

{
  "current": {
    "time": "2021-12-20T09:28+02:00",
    "symbol": "n000",
    "symbolPhrase": "clear",
    "temperature": -11.76,
    "feelsLikeTemp": -18.97,
    "relHumidity": 69,
    "dewPoint": -15.81,
    "windSpeed": 4.25,
    "windDir": 16,
    "windDirString": "N",
    "windGust": 11.66,
    "precipProb": 1,
    "precipRate": 0,
    "cloudiness": 3,
    "thunderProb": 0,
    "uvIndex": 0,
    "pressure": 1020.95,
    "visibility": 19934
  }
}
8 Likes

Can someone with some rights convert this post to a wiki, please?

2 Likes

How is it not more sensible to just file issues on GitHub?

1 Like

Indeed Github may be a better place, but you need an account to take part to the decision.

2 Likes

Agree, as someone who don’t even know how to navigate in GitHub properly, I can take part and follow discussion here much easier. Of course someone probably need to take the suggested features to GitHub.

3 Likes

Please share a link to the Issues in Github when created.

I would like to vote on Allow multiple providers and add Yr.no to the list.

2 Likes

Unfortunately, keeping various lists in sync across platforms is thankless busywork that nearly noone wants to do. Resource is scarce as-is, and the end result will always be sync targets being out of date all the time.

I highly recommend channeling all enthusiasm into onboarding as many as possible on GH: YouTube has plenty of good Getting Started tutorials etc. Issue management is just a comment box at the end of the day, there, too.

1 Like

With a system allowing to easily add a new provider, it’s perhaps easier to fix once a provider is broken? But I agree with you that maintaining various provider is not the best idea.

Where are the instructions? There isn’t even a readme file there. It should be easy and not for developers only.

1 Like

When Jolla originally wrote the software in 2013, I’m sure they didn’t have the ease of modification by the general public in mind, so they didn’t bother with writing “how to edit this” or designing it with this kind of modularity from ground up.

1 Like

Check your expectations. Barely any projects have that.

It is perfectly normal that software development is for developers only.

7 Likes