[sync] Synching Birthday-entries?

[Jan Schneider]

Zitat von Lukas Gradl <horde at ssn.at>:

>
>
> Jan Schneider schrieb:
>> Zitat von Lukas Gradl <lazarus at ssn.at>:
>>
>>>
>>>
>>> Jan Schneider schrieb:
>>>> Zitat von Lukas Gradl <horde at ssn.at>:
>>>>
>>>>>
>>>>> Jan Schneider schrieb:
>>>>>> Zitat von Lukas Gradl <horde at ssn.at>:
>>>>>>
>>>>>>>
>>>>>>> Jan Schneider schrieb:
>>>>>>>> At the moment you can't even sync anything but your default   
>>>>>>>> calendar.  When we add preferences to choose the resources to  
>>>>>>>>  sync with, we might  add time objects (like birthdays) too.  
>>>>>>>> This  might collide with clients  that already show birthdays  
>>>>>>>> in the  calendar, like Outlook, though you  could always turn  
>>>>>>>> it off, of  course.
>>>>>>> Thanks for your explantations.
>>>>>>>
>>>>>>> Are there any near future plans to create a possibility for   
>>>>>>> user-settings in SyncML?
>>>>>> Plans? Yes. In the works? No. Though I'll try to implement this  
>>>>>> for  address books this week so that I can easily take all my  
>>>>>> address  books on the road while on vacation. :)
>>>>> What I was thinking about is quite near your plans:
>>>>> - Choosing which addressbook(s) to sync
>>>>> - and making a few tests if it might be possible, that the user  
>>>>> can  select his type of mobile device and the sync-process will  
>>>>> change  field-mappings according to that setting (and perhaps  
>>>>> this "select  mobile device" might be a good place to check the  
>>>>> synched fields for  deleting attributes as Gunnar suggested...)
>>>>
>>>> No, this is not necessary and doesn't make much sense. There are  
>>>> only  so many properties possible for vCard or SIF-C data.
>>>
>>> Don't understand your answer....
>>> - I know this is not possible at the moment - that's why I wanted  
>>> to make some tests if it might be possible to implement...
>>>
>>> - why does that not make sense? Nearly every mobile device has  
>>> different Field-Maps (eg. the telephone-numbers!) So why not make  
>>> a possibility to change the mappings on a per user base? IMHO that  
>>> makes sense!
>>
>> It doesn't matter what these devices do internally. In the end they  
>> have to synchronize their data with a set standard. And these  
>> standards (see above) only provide a fixed set of possible  
>> properties. We already support those (to some extend).
>
> A fixed set of possible properties? Where in which standard is a  
> definition of possible properties (and let alone which  
> "human-readable-fieldname" they get!)? There are only rule for HOW  
> to encode things, but not WHAT.

Eh? vCard and SIF-C *do* specify available contact properties.

> Outlook has 19 possible Telephone-numbers, Nokia/S60 has 20, but  
> only half of them match. So the only place to get them together and  
> to decide which number goes where is on a central server - which  
> turba wants to be.
>
> To do that by device-recognition is nearly impossible - as  
> recognition depends on the SyncML-Plugin used.

Sorry, I lost you, no idea what you are talking about here.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/