On Friday, 2013-06-14, Jan Kundrát wrote: > into Kontact" is a good first step, but I was hoping for something more > integrated, i.e. using Kontact's facilities for notiffying about new > mails, etc (assuming there is something like that in Kontact).
Notifications are independent of the Kontact shell, each component is using KDE's notification API as it sees fit, which in turn uses a D-Bus API to talk to a notification provider. So ultimately notification support is not related to KDE at all, but more an item for general FOSS/Linux desktop integration. > > * create new kpart plugin for kdepim which render trojita GUI into > > Kontact > > Notifications? Providing some kind of a persistent identifier so that > Kontact can "attach" mails to e.g. events in a calendar? Perhaps that's > impossible without pretending to be an akonadi backend, in which case it's > out of a table, but still worth a discusssion. I don't think there is anything like attaching an email to an event in a linked kind of fashion. The only mail -> calendar integration use case I am aware of is adding a calendar entry from a respective invitation email and sending out the accept/decline/.. response. A calendar -> mail integration point is sending out invitation emails, but I think that KOrganizer does that through KDE's mail transport library. That could be investigate more closely though. > I agree with Kevin's mail later in this thread where he is strongly in > favor of async interfaces -- these are harder to write, but provide huge > benefits. Especially when creating plugins for APIs that are asynchronous themselves, e.g. any network protocol based addressbook like LDAP, CardDav, etc. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
