Tickets :: Comment on [#10942] Horde_SyncMl_Device

* Your Email Address
* Spam protection	Enter the letters below: _______ _________ _____ ____ \| __ \ \ / /__ __/ ____/ __ \ \| \|__) \ \_/ / \| \| \| \| \| \| \| \| \| _ / \ / \| \| \| \| \| \| \| \| \| \| \ \ \| \| \| \| \| \|____ \|__\| \| \|_\| \_\ \|_\| \|_\| \_____\____/
Comment	> Horde_SyncMl_Device_Synthesis is a class that provides functionality > that is specific to the Synthesis.ch SyncML clients. The original > class seems to have been writter just to workaround some old > limitations for the windows mobile client: > - the inability to use DateTime in vTodo's DUE attribute, stripping > off the Time part; > - the use of custom values in the PRIORITY attribute (1,2,3 instead of 0-9); > > Using any recent synthesis syncml client (i tested the iphone and the > android ones), these limitations doesn't exists anymore; but since > they are forced anyway, the resulting vTodo gets corrupted: > - every vTodo's due date is changed to time 00:00; > - every vTodo's priority is changed to either 1,2,3; > > I tried to comment out all of the class's methods, and syncs started > working flawless. > Unfortunately i had no WindowsMobile or Palm devices to test this > change with, but is suppose that since all the synthesis's products > are based on the same library, the limitation is gone for all of > these devices. > >
Attachment
Watch this ticket