9:36 a.m.
Aahaaa,
Thanks for the extensive reply.
Op zondag 02 januari 2011 22:29:41 schreef u:
On So, 2011-01-02 at 20:30 +0000, Hans de Jonge wrote:
> Hi,
>
> I want to synchronise a local agenda of KDE's Korganizer-kontact with my Nokia
N900
> native calendar: using the file-backend.
[...]
> Besides VEVENT-s, the kontact calendar.ics file also contains VTODO
> and VJOURNAL items. These seem to be the problem: When I remove these
> with a plain text-editor, all 707 calendar-events are transferred
> properly to the N900 and subsequent synchronisation tests are
> succesfull enough.
You are accessing a single .ics file via the Evolution Data Server,
right? That only works for .ics files which contain one of VEVENT,
VTODO, or VJOURNAL, but not a mixture of them.
After using a small ics file for setting up and testing, I copied a standard ics file from
korganizer in the directory ${HOME}/.SyncEvolutionData/:
[hansdej@debian]>cp ${HOME}/.kde/share/apps/korganizer/std0.ics
${HOME}/.SyncEvolutionData/calendar.ics
and the working calendat source configuration with the test calendar.ics file:
********calendar config**********
[calendar]
sync = two-way
type = file:text/calendar
evolutionsource = file:///home/hansdej/.SyncEvolutionData/
uri = Calendar
****************************
But enter the VEVENTS and/or VJOURNAL, things stopped working. (for the reason you explain
below)
The SyncEvolution file backend as it exists at the moment also
doesn't
help, because a) it expects each item to be a separate file and b) also
is limited to one kind of items per directory.
[...]
>
> Any Solutions?
Sorry, none at the moment.
Your extensive answer has been pretty helpfull already; thanks!
Guess I 'll have to work around it for now then: tell Korganizer to refrain from
mixing the different items in one file; that will not be difficult (just something to
keep in mind all the time)
It wouldn't be too hard to write a SyncEvolution backend which
accesses
a single .ics file. If some developer is interested, then I can provide
further instructions. Might be useful by itself, independent of KDE.
There's also an on-going effort to enable an Akonadi backend, but it is
still work in progress. Dinesh (on CC) is driving that.
Okay, that sounds nice. I am just a mere mortal, non-software developer, trying not to
sound too pushy; But any idea of its maturity or estimation when we, simple mortals, can
get our hands on this?
(Or a place where we can sneak on the progress?)
$ syncevolution --template '?Nokia N900'
Available configuration templates:
template name = template description matching score in percent (100% = exact
match)
Nokia N900 = Template for all Nokia phones which support contacts, notes and combined
tasks+events 100%
Nokia N910 = Template for a fictious Nokia N910 80%
Sony Ericsson K750i = Template for old Sony Ericsson phones, with separate databases
for contacts/events/tasks/memos and SyncML 1.1 40%
Sony Ericsson W595 = Template for all current Sony Ericsson phones, with separate
databases for contacts/events/tasks/memos and SyncML 1.2 40%
SyncEvolution Client = SyncEvolution server side template 40%
:-) Thanks again: I had tried to get the the N900 template printed, but despite the
respectable amount of documentation present on the syncevolution.org site, I had not
realized the usage of the single quotes around '?Nokia N900'. Thanks for also
showing the applied example.
Hans de Jonge