I'm working on a GUI app which will be using Qt for GSoC 2011 and i'd like
to thank you for these bindings since they probably make my life that much
I was wondering how much of difference do these bindings make? And do they
offer all the functionality the current dbus interface does?
On 2011 5 13 18:45, "Gabriel Schulhof" <nix(a)go-nix.ca> wrote:
> I have just received access to the syncevolution repo on gitorious. I
> pushed a branch called qt-bindings, which should create the bindings
> necessary for talking to the syncevolution D-Bus server from a Qt app.
> The bindings are enabled with --enable-qt-dbus from configure.
> I work for Intel.
> SyncEvolution mailing list
I am currently looking for a Linux replacement for Gigaset QuickSync
. QuickSync is a tool to sync contacts with a cordless phone (not a
cell phone). I thought SyncEvolution might be the obvious candidate for
The cordless phone talks BlueTooth, but not SyncML. I just figured out
that one can feed contacts to it by pushing 2.1 vCards one by one over
BlueTooth. I am currently only interested Desktop → Phone sync. Since
SyncEvolution over Bluetooth won’t work, I thought I could at least use
SyncEvolution to convert my Evolution addressbook to a set of vCard
files in 2.1 format.
As far as I understand, I’d normally need backend-to-backend sync
(Evolution → file). IIRC, that’s not yet implemented. So I thought about
setting up a local SyncEvolution server with the file backend. But it
seems that it isn’t possible to sync syncevolution with
syncevo-http-server on the same machine.
So is there a way to achieve what I try to do using SyncEvolution? Maybe
someone can push me into the right direction.
Once I finally set-up Syncevolution 1.1.1-2 so that I could at least do
a one-way refresh of "Contacts" to my Nokia N86 8MP, I found that
certain contacts would not sync; The resulting comment in the GUI was:
"There were 22 remote rejections". Has anybody else experienced this?
More importantly, has anybody found a solution?