On 03/08/2016 09:52 PM, deloptes wrote:
Hi
The context to my questions is the project I started about integrating syncevolution in TDE. I finished the basic plugin part and would like to write the platform part, which seems to use dbus from within the plugin to provide password read/write in the tdewallet.
- Question
what would be the best place to start reading about using dbus from within trinity? What is the preferred library to use for the future - it says dbus-1-tqt is qt4 bindings backport? I guess the dbus-tqt should serve my needs as I'm targeting the TDE wallet, but still I would appreciate some advise.
http://git.trinitydesktop.org/cgit/dbus-tqt/ http://git.trinitydesktop.org/cgit/dbus-1-tqt/ http://git.trinitydesktop.org/cgit/kdbusnotification/
- Question
For Calendar/Todo/Memo and Addressbook we hit some issue in syncevolution that child sends via dbus the final sync report message to the parent but the return message does not result in the defined callback and both parent and child are stuck. Patrick Ohly from Syncevolution is looking into it but I think asking here is worth in this case. Are you aware of some side effects in DBus context when used in Trinity? Are there some recommendations - examples, application code?
thanks in advance
Hi Deloptes, sorry for the late reply but I was not on TDE all day and I wanted to check something before replying. TDE is basically DCOP based, being born as a fork of KDE 3.5. Anyhow dbus-tqt and dbus-1-tqt add support for dbus application. To be honest I never delved into it at all, since they were already there when I discovered/joined TDE. dbus-tqt provides dbus support, dbus-1-tqt provides binding for TQT (whatever that means, I am just referring to the package description in Debian) and kdbusnotification is a small tray app that displays dbus notifications. In addition to the git URLs you mentioned, you can probably read on line about dbus, such as: https://dbus.freedesktop.org/ https://dbus.freedesktop.org/doc/dbus-tutorial.html https://dbus.freedesktop.org/doc/dbus-specification.html
Regarding question 2, I have no idea. From the description it looks like some gets stuck, perhaps some locking problem (I am assuming there is some sort of synchronization mechanism in dbus :-) ). Could be in syncevolution or in the dbus implementation provided in Trinity. Sorry for not being of more help here.
Cheers Michele