On Wed, 17 Mar 2004, Duncan Sargeant wrote:

> Hubert Figuiere wrote on Tue March 16, at 12:26 +0100:
> > > .  all day events:  syncing between Evo and s55 of all-day events
> > >   results in midnight-midnight events in the s55.  a) this is done in
> > >   GMT, so its 8am -> 8am for me, and b) midnight-midnight localtime
> > >   spills over into the next day (looks bad on s55 calendar, I saw
> > >   someone else asking about that too).
> > 
> > "All day events" are a big issues as each device seems to handle it its
> > own way.
> 
> Doh!  Is that just v1 devices, or do v2 devices have the same problem?

Lots of "devices" don't speak vCal/iCal at all, and we have to transalte 
into that format. It is a problem in general.

> 
> > >   I patched the code to equate vCal v2 all day events to vCal v1
> > >   zero-minute events at midnight on the day.  Which is great for the
> > >   s55 (but probably not so good for other v1 vCal devices;
> > 
> > Perhaps should these hooks be implemented on a device by device basis ?
> > This would solve lot of side effects. This is IMHO the best solutions.
> 
> Like a sub-plugin architecture?  It sounds like a good solution to me
> too, if the device formats are really so different.  Not that I've
> looked at it thoroughly at all, but my gut feeling is that it would
> also require a rewrite of the sync-vtype code.  At the moment it
> parses vCal line-by-line, which could result in some bad spaghetti
> code if it was trying to deal with many different formats.

The idea in the future (0.90+) is to get the type massaging out of the 
sync engine and in to type plugins. I'd imagine that this would include 
data types like this.

Tom




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Multisync-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/multisync-devel

Reply via email to