[Kde-pim] Running KMail and calling via D-Bus

Kevin Krammer kevin.krammer at gmx.at
Tue Aug 4 19:05:22 BST 2009


On Tuesday, 2009-08-04, Thomas McGuire wrote:

> I had the same problem with the Kolab resource, which needs a special
> interface to show up to work.
> What I did to solve that was a introducing a nasty hack: After I created
> that interface in KMail, I added a dummy D-Bus service
> "org.kde.kmail.groupware". This way, I then use Qt to see if the
> org.kde.kmail.groupware service is up, which in turn also means my
> groupware interface/object is ready.
> Not a nice solution though. The code is in
> KMailConnection::waitForGroupwareObject() in
> kdepim/kresources/kolab/shared/kmailconnection.cpp.

Wouldn't it be easier if an always existing object would emit a D-Bus signal 
when it has successfully created sub objects?

Sure, it is a pity that QDBusInterface seems to test validity at creation time 
[1] thus not allowing the interface itself to emit that signal, but it still 
sounds less messy than to register another name.

Cheers,
Kevin

[1] maybe there is a way in the Qt4 bindings to allow a proxy object to be 
instantiated without introspecting the target

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20090804/b8684c57/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list