On Mon, Nov 21, 2016 at 19:04:02 +0100, deloptes wrote:
> Hi,
> yes I would prefer bluetooth as I do not use wireless, or at least avoid
> using it.
I must have missed something, as I never saw a Bluetooth cable yet. :-)
> + I don't have Cal/CardDav server setup. Can SyncEvolution offer
Tino Mettler wrote:
> On Mon, Nov 21, 2016 at 08:00:33 +0100, deloptes wrote:
>
>
>> devices for me and the question is can be done something for SailFish and
>> what, so that I can use SyncEvolution with it via bluetooth. If you know
>
> Hi,
>
> is Bluetooth the only option for you? It looks
On Mon, Nov 21, 2016 at 08:00:33 +0100, deloptes wrote:
> devices for me and the question is can be done something for SailFish and
> what, so that I can use SyncEvolution with it via bluetooth. If you know
Hi,
is Bluetooth the only option for you? It looks like Sailfish can sync via
Hi Patrick, Graham, all,
Patrick Ohly wrote:
> On Tue, 2016-11-15 at 23:04 +0100, deloptes wrote:
>> Patrick Ohly wrote:
>> > During all that time, SyncEvolution has had a functional SyncML
>> > implementation and backends for the PIM storage in MeeGo...
>>
>> Here is what they said:
>>
>>
On Fri, 2016-11-18 at 16:35 +, Graham Cobb wrote:
> On 18/11/16 15:06, Patrick Ohly wrote:
> > SyncEvolution can be used in such a mode - one just needs a central hub
> > which supports the full semantic and attributes of everything that one
> > wants to sync, and the description of what each
On 18/11/16 15:06, Patrick Ohly wrote:
> SyncEvolution can be used in such a mode - one just needs a central hub
> which supports the full semantic and attributes of everything that one
> wants to sync, and the description of what each peer supports has to be
> accurate. Unfortunately, in practice
On Fri, 2016-11-18 at 14:08 +, Graham Cobb wrote:
> On 18/11/16 13:03, Patrick Ohly wrote:
> > With multi-way you mean a sync topology that has cycles? Yes, that's
> > indeed not possible with SyncEvolution. I also don't see a way to do it
> > as long as one is stuck with existing data
On 18/11/16 13:03, Patrick Ohly wrote:
> With multi-way you mean a sync topology that has cycles? Yes, that's
> indeed not possible with SyncEvolution. I also don't see a way to do it
> as long as one is stuck with existing data formats.
Actually, I meant even without cycles. It seems to me from
On Wed, 2016-11-16 at 09:48 +, Graham Cobb wrote:
> On 16/11/16 08:43, Tino Mettler wrote:
> > On Wed, Nov 16, 2016 at 08:16:29 +0100, Patrick Ohly wrote:
> >
> > [...]
> >
> >> while Buteo was a "cleanly designed" framework which avoided doing
> >> any of the hard work and delegated that to
On Wed, Nov 16, 2016 at 22:57:41 +0100, deloptes wrote:
> doesn't syncevolution support a cal/carddav server ... or just a client?
Hi,
it is just the client side. For the server side, you can try DAViCal if
you don't want to run a full blown ownCloud service just for PIM sync.
Regards,
Tino
Graham Cobb wrote:
> On 16/11/16 07:16, Patrick Ohly wrote:
>> Reminds me of the discussions we had about comparing Bueto with
>> SyncEvolution. SyncEvolution always had a strong focus on actually
>> making syncing work (and yes, that gets ugly sometimes), while Buteo was
>> a "cleanly designed"
Graham Cobb wrote:
> I am sure I used to have a version of SyncEvo on my Jolla, due to the
> kindness of someone on the list who built it. I seem to remember it
> worked sort of -- was it for calendar or contacts? Anyway it stopped
> working (did Jolla change the underlying data store or
On 16/11/16 20:10, deloptes wrote:
> Hi Graham,
> they confirmed it is not working on SailFish - who knows when they will
> implement it and how it will be implemented ... given the comments
> above ...
> Perhaps we have to work closer with the Jolla team on it. Or ... get proper
> SyncEvolution
Graham Cobb wrote:
> Oooh, a bit of a low blow :-)
>
> I certainly learnt a lot from spending quite a lot of effort trying to
> make OpenSync work! The main one (and the main reason I am here) is
> that sync is **really** hard to do in the general case.
>
> Syncevolution does a great job on
On 16/11/16 08:43, Tino Mettler wrote:
> On Wed, Nov 16, 2016 at 08:16:29 +0100, Patrick Ohly wrote:
>
> [...]
>
>> while Buteo was a "cleanly designed" framework which avoided doing
>> any of the hard work and delegated that to "plugins". In other
>> words, it didn't actually solve the
On Tue, 2016-11-15 at 23:04 +0100, deloptes wrote:
> Patrick Ohly wrote:
> > During all that time, SyncEvolution has had a functional SyncML
> > implementation and backends for the PIM storage in MeeGo...
>
> Here is what they said:
>
> Sync via Bluetooth isn't well supported at the moment. We
Patrick Ohly wrote:
> Huh? Then how did you sync between your N9 and the Sail Fish OS phone?
> Why does it advertise SyncML support via Bluetooth?
>
> I thought Sail Fish OS had continued to use Buteo as its sync solution
> because that's what they got from MeeGo, and there was a SyncML
>
On Tue, 2016-11-15 at 21:57 +0100, deloptes wrote:
> deloptes wrote:
>
> > I'll try to find information how this version is supposed to work. Perhaps
> > it is missing a service in the background.
>
> Jolla/Sailfish OS does not have syncml implemented (yet). Work is in
> progress, was the
deloptes wrote:
> I'll try to find information how this version is supposed to work. Perhaps
> it is missing a service in the background.
Jolla/Sailfish OS does not have syncml implemented (yet). Work is in
progress, was the answer.
thanks and regards
Patrick Ohly wrote:
>> This is what I did - it loops in ObexTransportAgent::wait(): iteration
>> for quite some time, but I guess I have to remove PC suite parameter and
>> who knows what I also have to modify.
>
> That doesn't look good :-(
>
> Is the phone still supported? Is it possible to
On Mon, 2016-11-14 at 20:27 +0100, deloptes wrote:
> Patrick Ohly wrote:
>
> >> How can I get a working template/config for the device
> >
> > I would start with the Nokia template.
> >
>
> This is what I did - it loops in ObexTransportAgent::wait(): iteration for
> quite some time, but I
Patrick Ohly wrote:
>> How can I get a working template/config for the device
>
> I would start with the Nokia template.
>
This is what I did - it loops in ObexTransportAgent::wait(): iteration for
quite some time, but I guess I have to remove PC suite parameter and who
knows what I also have
On Sat, 2016-11-12 at 10:17 +0100, deloptes wrote:
> Hi,
> I am wondering if it is possible to sync Intex Aqua Fish with SailFish OS
> via SyncEvolution.
>
>
> sdp browse
>
> Service Name: SyncML Client
> Service RecHandle: 0x10008
> Service Class ID List:
> UUID 128:
23 matches
Mail list logo
