GitLab

This should fix another high frequency polling loop, and fix the visual
update glitches when new data arrives.

Most batch-based logic doesn't actually care if we add or remove elements
from the batch, but only cares for the actual content changing.

This has currently been implemented in the timeline model, the trip
grouping and the live data handling, duplicating this rather complex
logic multiple times. The goal is to replace all that with the new code.

Compared to the existing implementations, this has more fine-grained
change notifications for the various corner cases, and it persists the
batching, so we don't have to compute that on every startup again.

This also makes further optimizations possible, like persisting the sort
order of the batches, so we only need to load the reservation elements
actually on the screen.

This fixes unneccessary high frequency polling during a longer trip.

Most importantly, we now propagate the geo coordinates from that to
the reservations, which makes all location-based features work.

This now leaves us with exactly one path for adding or changing
reservations.

Only needed when using widgets or QQC1 (which we don't).

Summary: Importing a reservation from an intent only worked when that intent started the app. When the app is already running onNewIntent is called, but since we didn't override it nothing was imported.

Test Plan: Open app. Send reservation via KDE Connect. Previously nothing happend. Now the reservation is added to the list

Reviewers: vkrause

Reviewed By: vkrause

Subscribers: kde-pim

Tags: #kde_pim

Differential Revision: https://phabricator.kde.org/D17993

Test Plan: Double-tap barcode : Screen gets brighter

Reviewers: vkrause

Reviewed By: vkrause

Subscribers: kde-pim

Tags: #kde_pim, #kde_itinerary

Differential Revision: https://phabricator.kde.org/D17827

Necessary for a more clever auto-polling.

Could still be nicer by using color highlighting for changes.

Summary:
_ZN22SolidBrightnessBackendC1EP7QObject symbol not found.

Commit 1466a25c removed compilation of solidbrightnessbackend.cpp on
Android, so this code now uses a class that's not part of the build.

Test Plan: Running on Android now works

Reviewers: vkrause, nicolasfella

Reviewed By: vkrause

Differential Revision: https://phabricator.kde.org/D17763

Also, make it less departure-centric, now that arrivals are handled here
too.