aspotashev added a comment.
In D22544#505476 <https://phabricator.kde.org/D22544#505476>, @ngraham wrote: > In D22544#497637 <https://phabricator.kde.org/D22544#497637>, @aspotashev wrote: > > > > The case where no notification daemon is running is IMHO an edge case that we don't need to support. > > > > Disagree here. I believe a lot of people don't use a notification system on Linux. If we remove KPassivePopup, some apps with stop working properly for them. > > > This seems unlikely to me simply given that all the major DEs have notification systems installed by default, so the pool of people you're talking about would be limited to people using purely DIY systems or bare-bones tiling WMs. In such a case, by deliberately not installing notification stuff, those users are signaling that they don't want notifications, in which case, they should be //happy// to not see KPassivePopups, no? :) Of course not. If an application is designed to tell something to its user by means of a notification, then we can judge the application stops working corrently as soon as notifications are blocked. IOW, if KNotifications drops KPassivePopup support, then every application using KNotifications now requires a notification system. This is not fatal, but it limits the range of systems where a application can be used. >> Also, even if you use Plasma, sometimes it crashes, and then you don't have a notification daemon to connect to. > > Then we should make it more reliable. :) Impossible. In the current design, you can always make Plasma crash with a broken custom widget. REPOSITORY R289 KNotifications REVISION DETAIL https://phabricator.kde.org/D22544 To: nicolasfella, #frameworks, broulik Cc: ngraham, davidedmundson, aspotashev, kde-frameworks-devel, LeGast00n, sbergeron, michaelh, bruns
