[SyncEvolution] Calendar+Todo and Memo

[Patrick Ohly]

On Sat, 2016-04-02 at 23:04 +0200, deloptes wrote:
> Hi all,
> 
> I apologize for disturbing you once again, however I found out that the
> older Nokia 5530 has Calendar+Todo and Memo in one.
> So when I use following configuration I get everything to the TDE Calendar
> when just syncing the calendar part. This is great, however I can not push
> back Todo or Memo items for obvious reasons.
> 
> How can I modify the configuration such that I am able to use all of it. I
> read about the virtual, but could not come up with a decision what I should
> put where in the config.

The easiest approach would be to do something as in
https://syncevolution.org/wiki/kde-akonadi: first configure your local
databases, then add peers as described elsewhere.

That means:
syncevolution --configure \
              addressbook/backend=tdepim-contacts \
              addressbook/database="kxXrRFzP9c" \
              addressbook/databaseFormat="text/vcard" \
              calendar/uri="Calendar" \
              calendar/backend=tdepim-calendar \
              calendar/database="ZsPZokpoTg" \
              calendar/databaseFormat="text/calendar" \
              todo/backend=tdepim-tasks \
              todo/database="ZsPZokpoTg" \
              todo/databaseFormat="text/calendar" \
              memo/backend=tdepim-memos \
              memo/database="ZsPZokpoTg" \
              memo/databaseFormat="text/calendar" \
              @default addressbook calendar todo memo

And then add the phone
(https://syncevolution.org/wiki/sync-your-phone-bluetooth):

syncevolution --configure \
              --template nokia \
              --sync-property syncURL=obex-bt://${deviceAddress} \
              nokia_5530

Because "nokia_5530" = "nokia_5530 at default", it will use the
addressbook/calendar/todo/memo databases defined in that context
earlier.

The template has a calendar+todo entry that matches the data on the
phone and splits it locally into calendar and todo.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.