<table><tr><td style="">mck182 added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D4663" rel="noreferrer">View Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><div class="remarkup-code-block" style="margin: 12px 0;" data-code-lang="text" data-sigil="remarkup-code-block"><pre class="remarkup-code" style="font: 11px/15px "Menlo", "Consolas", "Monaco", monospace; padding: 12px; margin: 0; background: rgba(71, 87, 120, 0.08);">I don't think that KNotification as a framework should hide this feature from the developer.</pre></div></blockquote>
<p>I, on the other hand, don't see why the developer should need<br />
this feature; as I said before - there's no scenario where the<br />
app should want either really short or really long time on the<br />
screen - this should always be fully up to the shell displaying<br />
the notifications. If you do need to have the notification bubble<br />
on the screen for really long time, then imho that's a wrong<br />
solution to the problem it'd be solving.</p>
<p>And that applies to this case as well. KDE's Bluetooth integration<br />
is solving the same problem (pairing devices) and it uses a dialog,<br />
which imho makes sense, because with notification you're supposed<br />
to inform the user that something has happened and he may or may<br />
not react to that something, while what you're doing requires direct<br />
user interaction and what you're trying to solve is the possible lack<br />
of that direct interaction. So I honestly think that a notification is not<br />
even the right approach here altogether.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>they do that using the notifications cross-desktop standard. So I wouldn't criticize Gnome for doing their own thing here.</p></blockquote>
<p>Oh really? :) Ever wondered why the spec you're referring to<br />
is full of only Gnome's extensions and is hosted on Gnome's<br />
servers? It's because Gnome considers the Galago project,<br />
the actual cross-desktop notifications project, dead. They took<br />
over libnotify and they consider that implementation to be the<br />
canonical upstream for the specification. In other words, Gnome<br />
has full control over that spec, can do what they want and can just<br />
as easily block any of our contributions. Sure, it is based and<br />
backwards-compatible with the cross-desktop standard, but it<br />
stopped being actual cross-desktop standard long time ago.<br />
If you feel like changing that, this would be a good start:<br />
<a href="https://bugzilla.gnome.org/show_bug.cgi?id=748145" class="remarkup-link" target="_blank" rel="noreferrer">https://bugzilla.gnome.org/show_bug.cgi?id=748145</a></p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p><a href="https://phabricator.kde.org/p/colomar/" style="
border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;" rel="noreferrer">@colomar</a>: This would be perfect, but it would need a whole lot of work from both the desktop environment and the application side.</p></blockquote>
<p>It's actually not that hard as far as the last three points go. This<br />
can be fully implemented in the notification's server (ie. Plasma)<br />
and the apps changes would be minimal. I even had a branch<br />
doing exactly that, I just never had the time to finish it. But basically<br />
the idea is - every new notification that arrives to the server is<br />
directly mapped to a KSNI - title to title, text to subtitle, actions<br />
to SNI actions. The lifecycle is a bit tricky (eg. when it is not needed<br />
anymore) but still can be done. I meant to mostly mimic what<br />
Android is doing. The only part remaining to solve is the drawer<br />
that has all the SNIs and their action in some sensible way.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R289 KNotifications</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D4663" rel="noreferrer">https://phabricator.kde.org/D4663</a></div></div><br /><div><strong>EMAIL PREFERENCES</strong><div><a href="https://phabricator.kde.org/settings/panel/emailpreferences/" rel="noreferrer">https://phabricator.kde.org/settings/panel/emailpreferences/</a></div></div><br /><div><strong>To: </strong>albertvaka, Frameworks, apol<br /><strong>Cc: </strong>colomar, mck182, Frameworks<br /></div>