7:51 p.m.
[Dinesh's email was meant to go to the list, copying the list again]
On Mi, 2011-01-05 at 20:05 +0530, Dinesh wrote:
I have done
grep -rin SPOUSE *
in syncevolution/source/syncevo
and this is what I ve got:
configs/datatypes/00vcard-fieldlist.xml:64: <field name="SPOUSE"
type="string" compare="conflict"/>
configs/datatypes/01vcard-profile.xml:169: <property
name="X-EVOLUTION-SPOUSE" suppressempty="yes"
delayedparsing="1">
configs/datatypes/01vcard-profile.xml:170: <value field="SPOUSE"
show="yes"/>
configs/datatypes/01vcard-profile.xml:172: <property name="X-SPOUSE"
suppressempty="yes" rule="EVOLUTION"/>
configs/datatypes/01vcard-profile.xml:173: <property name="X-SPOUSE"
suppressempty="yes" rule="other">
configs/datatypes/01vcard-profile.xml:174: <value field="SPOUSE"
show="yes"/>
So, (configs/datatypes/00vcard-fieldlist.xml ,
configs/datatypes/01vcard-profile.xml) are these the XML files i have
to be editing for adding KDE specific extensions? (all the additions
should be done the same way right?)
Yes to both. Use rule="KDE". Here's what it should look like:
<!-- item for SyncML server: EVOLUTION rule not active,
both X-EVOLUTION-MANAGER and X-MANAGER are sent.
item from SyncML server: EVOLUTION rule not active,
both X-EVOLUTION-MANAGER and X-MANAGER are checked,
but X-EVOLUTION-MANAGER later so that it overwrites
a value set earlier by X-MANAGER (if any). This is
a more or less arbitrary priority, chosen because
servers that know about SyncEvolution (ScheduleWorld,
Memotoo) use the X-EVOLUTION variant.
item to/from Evolution: EVOLUTION rule is active,
only X-EVOLUTION-MANAGER is used. -->
<property name="X-EVOLUTION-MANAGER" suppressempty="yes"
delayedparsing="1">
<value field="MANAGER" show="yes"/>
</property>
<property name="X-MANAGER" suppressempty="yes"
rule="EVOLUTION"/> <!-- disables the X-MANAGER for EVOLUTION -->
<property name="X-MANAGER" suppressempty="yes"
rule="KDE"/> <!-- disables the X-MANAGER for KDE -->
<property name="X-MANAGER" suppressempty="yes"
rule="other">
<value field="MANAGER" show="yes"/>
</property>
<!-- only enable this when talking to KDE backend -->
<property name"X-KADDRESSBOOK-SPOUSE" rule="KDE">
<value field="MANAGER"/>
</property>
Note that there was some dispute about the name of the X- extensions
used by KDE. I picked something as placeholder above from memory, better
check this with real test data.
Also certain fields ,like SPOUSE, are in both Evolution and
KAddressbook. So should I be using the same field name for both?
Yes, absolutely. The field name must be the same, so that the Synthesis
engine can do the mapping in the different profiles.
I have not forgotten that you also want to handle arbitrary extensions
as defined by users of the KDE suite. Can you give an example how such
extensions look like? Is allowed to have the same X-FOOBAR property
multiple times?
--
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.