GitLab

We need that in multiple places.

Also, consider realtime status information for coloring those.

This is barely good enough as a proof of concept, there is still quite
some work needed to properly merge the various elevator elements and
to more reliably match OSM data and realtime equipment information.

The Location::Equipment case will be handled in a dedicated class.

This allows us to provide them directly from QML as well, as will be needed
by the upcoming realtime elevator status one.

Prepares this for usage with an upcoming equipment model that needs a more
fine-grained control over level filtering.

Fixes compilation with upcoming KPublicTransport changes.

For just showing the text this might be overkill, but when showing a more
elaborate evaluation of this, the extra separation makes things easier to
read.

Clipping to future events needs to happen above this, otherwise this
messes with change tracking.

Needed in KDE Itinerary.

Also, show icons for closed entities in a different color.

Will make maintaining the different color scheme style sheets easier.

This should complete the API needed to integrate opening hours into map
styling.

This matters when opening hours are considered for styling.

Lacking a coordinate-based lookup for those here, we still need a way to
provide them externally though.

This works and performs well already, but we are still missing proper
ways to configure the relevant time span as well as the holiday region.
Also, this has yet to be used in any of the style sheets.

The pointer use here pre-dates the value type changes to MapData.

We can do that now that the new data on maps.kde.org is deployed, with
previous precision loss issues fixed that we had to work around here.

The enum with Http2 spelling is 5.15+ only, the one with HTTP2 spelling
is 5.14 only (and deprecated afterwards).

Requested by distributors.

This works perfectly fine with the more specific type on Linux, but breaks
on Android for unknown reasons, making the application fail to start there.

This also completes the API needed to properly integrate this in an
application.

This makes it easier and safer to pass this through QML, and it will make
it possible to expose API to QML (which we cannot do on the previous raw
pointer, nor a shared pointer directly).

Prepares this for becoming a shared value type for easier and safer use
via QML.

This allows us to use it in the C++ example app as well, and avoids using
some implementation details of MapData there, preparing that for some
needed refactoring.