trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: December 2015

Re: Re: Re: TDEPIM status and possibility to extend it to support syncevolution

From: deloptes <deloptes@...>
Date: Sat, 05 Dec 2015 17:28:41 +0100
Slávek Banko wrote:

> Nowadays I find it more convenient to deal with synchronization to the
> server instead of a "local synchronization with computer."

Slavek I got your point, I hope you get mine as well. Just as you prefer
sync up with a server, I prefer sync up with the PC.

Your point is valid one and I do not think that our views contradict in some
way.

And yes it states it supports CalDAV/CardDAV, but I almost never use the
wireless or data access on my phone. I would prefer old fashion USB cable
or bluetooth also for the security reasons the gents mentioned above.

AFAIR syncevolution supports  CalDAV/CardDAV as well, so wouldn't it be
better to just connect TDEPIM with syncevolution and let all the rest to
their support team?

I'm not advocating for syncevolution, but I'm not aware of any other engine
supporting SyncML with USB/Bluetooth.

I'm not sure, but I think we could extend kitchensync and let it use
whatever we offer in TDEPIM to use syncevo engine and this might be the
less effort path - but honestly I'm too far from being sure as I barely
know the status of TDEPIM and syncevolution ATM.
Where is the CalDEV/CardDEV part Timothy and you mentioned? What is the git
location?

regards