[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    [Kde-pim] Re: Toltec connector and exceptions to recurring events
From:       Reinhold Kainhofer <reinhold () kainhofer ! com>
Date:       2005-05-30 23:02:44
Message-ID: 200505310102.46662.reinhold () kainhofer ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Am Dienstag, 31. Mai 2005 00:15 schrieben Sie:
> On 30. Mai 2005, at 01:23 Uhr, Reinhold Kainhofer wrote:
> > However, what kontact doesn't support is to change just one single
> > occurence
> > of a recurring sequence. RFC 2445 says that this is done by having
> > an event
> > with the same UID, but a different RECURRENCE-ID, which specifies the
> > date/time of that one occurence. You can then change any field of
> > the event,
> > but it will still belong to the original event.
>
> OK. But is this relevant for Outlook, that is, does Outlook actually
> support such a setup?

Yes, that's how Outlook handles changing one event of a recurring sequence.

And this was actually the problem that Alan J Collison was experiencing in his 
original post in this thread.

In KOrganizer we have the feature to dissociate an occurence of a recurring 
sequence in the agenda view. What we  do there is simply create new event and 
add the time to the exdates of the original event. 
I looked at Evolution a second ago, and they seem to handle it the same. The 
only difference is that we add a relation to the original event via a 
RELATED-TO;TYPE=SIBLING entry in iCalendar, while evolution looses all 
connection to the recurring sequence..


> PS: IMHO the uid/recurrence-id is quite important in the real world
> (and btw explicitly mentioned/supported in CalDAV). Maybe you can
> somehow workaround using the CalDAV approach (storing multiple
> vevents in memory under a single uid)?

That workaround won't work, since lots of places use a structure like

QString uid=....;
Event *event = calendar->event( uid );
createObject(event->summary(), ....);

You see, lots of places explicitly depend on the assumption that only one 
unique (possibly recurring) event is associated to one UID. I guess it would 
take quite a lot of work to get rid of this in kde-pim.

Cheers,
Reinhold

PS: I'm cross-posting this to kde-pim@kde.org, and kolab-format@kolab.org, 
since this discussion now also affects all of kde-pim...

-- 
------------------------------------------------------------------
Reinhold Kainhofer, Vienna, Austria
email: reinhold@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at
 * K Desktop Environment, http://www.kde.org/, KOrganizer / KPilot maintainer

[Attachment #5 (application/pgp-signature)]

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]