From kde-core-devel Fri Aug 28 18:52:47 2009 From: "Aaron J. Seigo" Date: Fri, 28 Aug 2009 18:52:47 +0000 To: kde-core-devel Subject: Re: [PATCH] Detecting notification popup server capabilities Message-Id: <200908281252.47533.aseigo () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=125148565613704 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2099273.ak6HTGtNBA" --nextPart2099273.ak6HTGtNBA Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On August 28, 2009, Aur=C3=A9lien G=C3=A2teau wrote: > Sebastian Tr=C3=BCg a =C3=A9crit : > > sounds like a weird solution to me. What are apps supposed to do in such > > a case? Just not add actions? That can be handled on another level I > > suppose. > > I was indeed thinking about this: just letting knotify discard the > action if the notification server does not support them. I can easily > provide a patch to do this. why? the server can discard them just as easily without us adding to our AP= I,=20 no? to me this really sounds like the thin edge of a wedge that will encourage= =20 people to not trust in actions and stop using them. which is why some peopl= e=20 want, i know, but not what we want. i'm not cool with that kind of erosion. > Still, I think it's useful to let applications know whether actions are > supported or not. This way they can switch to other means of > interactions (the other means in Ubuntu being message indicators, which > I am working on as well, see [1]) exactly what i feared above. put simply: that's fixing it in the wrong plac= e. if actions aren't supported in Ubuntu's interpretation of How The World Wor= ks=20 then Ubuntu needs to figure out how to rectify that. KDE should not, and AF= AIC=20 will not, do that for Ubuntu (or any other single distro) at the cost of ou= r=20 API and our application's consistency. this is 100% solvable on the Ubuntu side, e.g. by turning actions into mess= age=20 indicators. this is really rather easy with the approach Plasma takes to=20 notifications, actually. in any case, this is a problem Ubuntu has created for itself, one the=20 upstreams are not in agreement with Ubuntu on (_none_ of the upstreams, afa= ik)=20 and so it's a problem Ubuntu can fix downstream. if it didn't put our application consistency at risk or muddy our APIs i=20 wouldn't care. but it does. so -1 from me. =2D-=20 Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software --nextPart2099273.ak6HTGtNBA Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkqYJ38ACgkQ1rcusafx20NeigCePTRJL64oK8lyi1uofrct5FKc eVQAoIzVEaSiNjY2wsPIJF5Txn8w5tEU =BSYT -----END PGP SIGNATURE----- --nextPart2099273.ak6HTGtNBA--