[Opensync-devel] evolution capabilities

[Mark E. <ma...@mp...>]

Hiya

I've attached a patch, would appreciate anybody present glancing over it
as a quick sanity check, as I'm still not completely sure about
capabilities.

We've discussed evo sync and capabilities before. Since then I
encountered a more specific problem. Create a sync group between file
and evo, create a new calendar object (event, task, or journal) on one
side or the other, and sync, it works ok. Create a new object on both
sides, file sync gets the object from evolution, but evolution gets a
new empty object, wierd !

So eventually I disabled all the capability code in evo sync, and it
"fixed" the problem. Evo sync currently builds capabilities for
contacts, but not any other objtype, so apparently opensync reads this
as the other objtypes having no capabilities at all.

So, attached patch adds capabilities for calendar objtypes. This info
can't be gained from evolution like contact capabilities can, so I've
put it together the best I can through experimentation. I don't want it
committed yet, but would appreciate someone else eyeballing it briefly
before I get it tested by the guy that brought this to my attention
using synce and evo.

As an addendum, this would suggest to me that capabilities in opensync
are a bit off, since they obviously aren't applied when syncing the
single object one way in the example given above. I'm a long way off
working out why, or even where, that is going wrong, so if anyone else
wants to look ....

Ta
Mark