In D29416#665213, @winterz wrote:

I understand the motivation for this change. However, it is pretty ugly and verbose.

maybe we can do something in KHolidays API itself to provide a prettier string.

Ideally "German (German) - Feiertage fur Deutschland (Bayern)" would become tr("Germany/Berlin (German)")?
I don't think we need to see "Feiertage fur Deutschland"

Technically this looks fine from the Prison POV. Whether the barcode type selection makes sense beyond "because we can" I'm not sure about though (in particular the 1D codes seem to be of questionable use here), but then again that's not something introduced by this patch anyway.

In T11875#229181, @nicolasfella wrote:

D29405 shows that a notifyrc-less KNotifications is possible in principle.

On Android we still have the problem that notifyrc supplies the needed channel name/descriptions.

Possible solution could be the aforementioned "Have app define actions in code somewhere", e.g. KNotification::addChannel("some_id", "Name", "Description"). Could fall back to a default channel if none is set

Replace the simple ref count with a full child id tracking.

Still not good enough, updating existing notfication messes up the refcounter, resulting still in leftover group elements.

Example:

Explicitly track if notification groups are still in use.

This isn't good to go yet, there are corner cases where the group summary item stays around after closing the last notification, working on fixing this.

Collapsed:

Oh, regarding borrowing for KTrip, you might want to check the one in Itinerary, that does some better train length scaling IIRC.

Don't remember why I ended up doing it like this back then...

There might be ways around the native function registration issue from the QML thread, e.g. by using the alternative approach of exported (mangled) symbols instead: https://docs.oracle.com/javase/1.5.0/docs/guide/jni/spec/design.html -> "Loading and Linking Native Methods".

Regarding data sources, there is also https://api.met.no/, no API keys required, world-wide coverage and CC-licensed data. KDE Itinerary has some code for dealing with their forecast data.