From kde-pim Sun May 18 13:34:41 2008 From: Kevin Krammer Date: Sun, 18 May 2008 13:34:41 +0000 To: kde-pim Subject: Re: [Kde-pim] Akonadi D-Bus interface renaming: remaining issues Message-Id: <200805181534.45990.kevin.krammer () gmx ! at> X-MARC-Message: https://marc.info/?l=kde-pim&m=121111773514457 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1269315226==" --===============1269315226== Content-Type: multipart/signed; boundary="nextPart1248167.LiB6Gb9PgM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1248167.LiB6Gb9PgM Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 13 May 2008, Kevin Krammer wrote: > On Tuesday 13 May 2008, Till Adam wrote: > > On Saturday 10 May 2008 17:09:25 Kevin Krammer wrote: > > > Therefore I'd like to ask for suggestions, probably something like > > > org.freedesktop.Akonadi.UserInterface > > > or > > > org.freedesktop.Akonadi.WindowPeer > > > > WindowContext? > > I like this. > > In a comment to my blog about this topic, Aaron suggested to use > org.freedesktop.Akonadi.VisualNotifications since there are people working > on a fdo spec using a similar name and we could probably switch to this > once there are implementations available. > > So maybe we should split the two problem domains, i.e. one interface for > the window context and one for the notifications and let the tray app > implement both. Since Tom needs to tag tomorrow, we should probably do this renaming today = or=20 tomorrow morning. Do we go for just a single interface, e.g. org.freedesktop.Akonadi.WindowContext on object /WindowContext on service=20 org.freedesktop.Akonadi.WindowContext or do we split the notification stuff into its own triple, assuming that=20 VisualNotification spec the KNotify guys are working on will become widely= =20 used or do we keep our own notification interface anyway and just add support fo= r=20 the other one Cheers, Kevin =2D-=20 Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring --nextPart1248167.LiB6Gb9PgM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBIMDB1nKMhG6pzZJIRAkIVAJ94Stz11aoq1ZE52UDzbPY2o0v8+ACfSQRg bwK3GAAlFqHYuROlIyMDpkI= =FNdU -----END PGP SIGNATURE----- --nextPart1248167.LiB6Gb9PgM-- --===============1269315226== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ KDE PIM mailing list kde-pim@kde.org https://mail.kde.org/mailman/listinfo/kde-pim KDE PIM home page at http://pim.kde.org/ --===============1269315226==--