Re: [Multisync-devel] sync_vtype_convert

2005-01-04 Thread Stewart Heitmann
On Wed, 5 Jan 2005 12:23 am, Armin Bauer wrote: > On Tue, 2005-01-04 at 14:14, Stewart Heitmann wrote: > > On Tue, 4 Jan 2005 11:44 pm, Armin Bauer wrote: > > > i will give you an example sync: > > > > > > two devices: A and B > > > > > > user adds this vcards to device A: > > > > > > NAME:blubb

Re: [Multisync-devel] sync_vtype_convert

2005-01-04 Thread Armin Bauer
On Tue, 2005-01-04 at 14:14, Stewart Heitmann wrote: > On Tue, 4 Jan 2005 11:44 pm, Armin Bauer wrote: > > i will give you an example sync: > > > > two devices: A and B > > > > user adds this vcards to device A: > > > > NAME:blubb > > A-ONLY-FIELD:test > > > > and syncs with B. Now the archive

Re: [Multisync-devel] sync_vtype_convert

2005-01-04 Thread Stewart Heitmann
On Tue, 4 Jan 2005 11:44 pm, Armin Bauer wrote: > i will give you an example sync: > > two devices: A and B > > user adds this vcards to device A: > > NAME:blubb > A-ONLY-FIELD:test > > and syncs with B. Now the archive will contain both fields (the > converter has to map the A-ONLY-FIELD of co

Re: [Multisync-devel] sync_vtype_convert

2005-01-04 Thread Armin Bauer
On Tue, 2005-01-04 at 10:57, Stewart Heitmann wrote: > > - Use device capabilities to tell the syncengine which fields one device > > does support and use this information to merge the data. This approach > > can be complicated and afaik one of the members of the OMA has a patent > > on this approa

Re: [Multisync-devel] multisync-gnokii-plugin hangs/crashes while syncing against evolution

2005-01-04 Thread Christian Hilgers
Jonas Birmé wrote: please see: http://www.multisync.org/wiki/index.php?PluginsNotFound Cool, did not find that before. If it still does not work with autoreconf, add the -f flag to the command as well. That is: autoreconf -s -f -i && ./configure Information that perhaps can be added to the wiki. Wi

Re: [Multisync-devel] sync_vtype_convert

2005-01-04 Thread Stewart Heitmann
> - Use device capabilities to tell the syncengine which fields one device > does support and use this information to merge the data. This approach > can be complicated and afaik one of the members of the OMA has a patent > on this approach. I think that's pretty much what I suggested but in diffe

Re: [Multisync-devel] sync_vtype_convert

2005-01-04 Thread Armin Bauer
On Tue, 2005-01-04 at 03:41, Stewart Heitmann wrote: > > > I find that if one plugin ignores a cvard entry because it does not > > > recognise it, then the multisync engine thinks the plugin device has > > > device > > > deleted that entry and promptly deletes the same entry from the other > > >