[11:37] system/kubuntu-notification-helper (master) e159e07 * Harald Sitter: src/daemon (13 files in 7 dirs) [11:37] don't put event names in the module [11:37] instead init it in the actual event class. that takes useless responsibility away [11:37] from the module [11:37] https://invent.kde.org/system/kubuntu-notification-helper/commit/e159e072d09f35112c2a7fee12b5e1cea3a350d8 [11:37] system/kubuntu-notification-helper (master) d3d7cdb * Harald Sitter: src (7 files in 2 dirs) [11:37] port to kconfigwatcher [11:37] replaces bespoke watcher tech [11:37] https://invent.kde.org/system/kubuntu-notification-helper/commit/d3d7cdb2da6ad9dee9c99e98a1f3abcac7b3535d [11:37] system/kubuntu-notification-helper (master) fbf67c3 * Harald Sitter: src/daemon (9 files in 7 dirs) [11:37] refactor event init and management [11:37] this moves all event setup and handling logic into the events themselves [11:37] making the module itself entirely unconcerned with the specifics of the [11:37] events. [11:37] https://invent.kde.org/system/kubuntu-notification-helper/commit/fbf67c3dbb521a89c91324af78ff5c52f19dedaf [11:41] RikMills: I'm not convinced this is a force for good in the world. l10n support is entirely bust. reboot notification is likely clashing with discover. codec notification I'm also sure is some degree of broken. driver notification I suppose is worthwhile but the way this is implemented is daft plus I'm not sure why that isn't in the driver kcm repo [11:41] the only things that look semi sane are apport and hooks support *shrug* [11:46] sitter: *shrug* has been my response each time I pondered it. I certainly can't fix it [11:52] sudo rm -rf /* [13:01] 'morning folks