| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Order the properties to be copied onto the new object in an order that
wouldn't throw warnings, eg. the "enabled-providers" property doesn't
like to be set if the "application-id" and "contact-info" properties
aren't set.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Similarly to the application ID, contact information must be provided to
use the online weather providers.
|
| |
|
|
|
|
| |
As uncommon as that might be...
|
| |
|
|
|
|
| |
And mention that in the gweather_info_set_application_id() API doc.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We will use this to supplement the user-agent so that individual
applications using libgweather are, well, identifiable.
|
| |
|
|
|
|
|
| |
1+1«2+1«3+1«4+1«5 = 61
Not 31...
|
| |
|
|
|
|
|
|
|
|
| |
According to the HTML5 spec ";" is no longer allowed. This was
automatically rewritten in Varnish, but was temporary measure
and was likely to disappear if on cache/load balancer change.
Closes: #72
|
|
|
|
| |
This allows the API provider to track libgweather usage.
|
|
|
|
|
|
|
|
|
| |
libgweather/gweather-location.c: In function ‘gweather_location_common_deserialize’:
libgweather/gweather-location.c:1591:5: warning: passing argument 1 of ‘glib_autoptr_cleanup_GWeatherLocation’ from incompatible pointer type [-Wincompatible-pointer-types]
1591 | g_autoptr(GWeatherLocation) *by_station_code = NULL;
| ^~~~~~~~~
| |
| GWeatherLocation *** {aka struct _GWeatherLocation ***}
|
|
|
|
| |
It's very much the old legacy API now.
|
|
|
|
|
| |
They were never master/slave elements, but parent/child, as is common in
XML.
|
|
|
|
|
| |
Was "info", "other" and "master_info" depending on the caller. Call
them all "original" or "original_info".
|
|
|
|
|
| |
Make sure to also copy the "enabled-providers" property when cloning the
info object.
|
|
|
|
|
| |
The old code used to start doing network I/O when we didn't even have
the enabled-providers set.
|
|
|
|
| |
It was outdated, and duplicates the content of the DOAP file.
|
| |
|
|
|
|
|
| |
We don't use autotools anymore, and it was what required this link, so
remove it.
|
| |
|
| |
|
| |
|
|
|
|
| |
Rather than relying on GWEATHER_EXTERN.
|
|
|
|
|
|
|
| |
Version 1.9, which we were using, was deprecated and will be removed soon,
so migrate to the compat XML output of the v2.0 API.
Closes: #65
|
| |
|
|
|
|
|
|
|
| |
Can be useful if libsoup and dependencies aren't installed properly and,
say, SSL/TLS support is broken.
GWeather:ERROR:test_libgweather.c:427:test_metar_weather_stations: assertion failed (msg->status_code >= 200): (6 >= 200)
|
|
|
|
|
|
|
|
|
|
| |
1/1000th of a degree of longitude or latitude corresponds to around
100 meters. There's no reason for the weather to be any more precise
than this.
See https://www.thoughtco.com/degree-of-latitude-and-longitude-distance-4070616
Closes: #69
|
|
|
|
| |
We will be adding code here.
|
| |
|
|
|
|
|
|
|
| |
"The Yr API is now officially discontinued, and the Yr is now
trademarked for the website and mobile apps only."
Closes: #64
|
|
|
|
| |
Add pylint to the CI environment so that we check the Python script.
|
|
|
|
| |
When available, run pylint over the DB generator to ensure a good style.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The order of locations as returned by GWeatherLocation used to be sorted
by the localised name. However, that requires quite a lot of resources
and is not needed in many usecases.
As such, sort the resulting tree model by location name. Note that this
actually changes the behaviour slightly as Countries were grouped by
region before and are now all sorted by name.
To do so, add a new column that allows direct comparison for sorting
purposes. Note that this cannot be the same as the compare name, because
order needs to be reversed for sorting but must remain the same for
matching.
|
|
|
|
|
|
| |
It looks like at one point the idea was to use a hierarchical structure
for the entries. However, it really is a flat list, so there is no need
to use a tree store for it.
|
|
|
|
| |
So that it doesn't cause the whole world to be kept in memory forever.
|
| |
|
|
|
|
|
|
|
| |
This makes GWeather use a memory mapped GVariant as an in-memory
database. Doing this allows much faster access and decreases memory
consumption considerably as items can be fetched from the database
on-demand.
|
| |
|