[kdepim-users] Editing a recurring appointment

[Ingo Klöcker]

On Friday 12 December 2008, Ákos Szederjei wrote:
> On Friday 12 December 2008 21:29:43 Anne Wilson wrote:
> > On Friday 12 December 2008 20:21:06 Ákos Szederjei wrote:
> > > On Friday 12 December 2008 19:54:42 Art Alexion wrote:
> > > > On Friday 12 December 2008 10:07:06 am Anne Wilson wrote:
> > > > > I have a weekly appointment, for which the time will change
> > > > > in the New Year. I can't find any way to change forward times
> > > > > only, leaving previous ones unchanged.  If this is true I
> > > > > would call it a bug, and report it. Am I missing something?
> > > >
> > > > I am going to make a guess here, based solely on my experience
> > > > with Palm Pilots and how they handle that.  If you make a
> > > > change to a recurring appointment in the Palm, it asks you
> > > > whether you want to change (1) all, (2) that instance, or (3)
> > > > this and all future occurrences.  If you use (3) it actually
> > > > terminates the original recurrence and creates a new recurring
> > > > appointment with the change.  If you choose (2) it creates 3
> > > > appointments, the original terminated just before the changed
> > > > one, the changed one, and a new recurring one starting with the
> > > > next one after the changed one.
> > > >
> > > > To the extent this is not implemented in kontact, you can do it
> > > > manually. Duplicate the appointment.  Edit one copy and
> > > > terminate it at the end of the year.  Edit the other one with a
> > > > new time and to begin at the first of the year.
> > > >
> > > > Hope this helps.
> > >
> > > Kontact does something similar.
> > > In the case of 2 it creates an excetpion (no appointment at that
> > > date) and allows the user to modify that single appointment.
> > > We do not have a case for 3, except to do the same thing
> > > manually.ű
> > >
> > > Ákos
> >
> > Ákos, thank you for discussing this with us.  It does help in the
> > understanding of the 'nuts and bolts' of the application :-)
> >
> > Anne
>
> A pleasure...
>
> Actually it is a conceptual question. There is no right answer,
> because both approaches has advantages and drawbacks.
>
> I played around with Kontact's calendar and it seems to me that the
> appointments use the time range as basic reference, while in Lotus I
> assume it is the name.
>
> For example: Dancing lesson - 17:00-18:30 - every Monday.
>
> In Kontact you can change everything and the reoccuring appointments
> remain together (as repeating occurrence), EXCEPT the time
> 17:00-18:30. As long the time 17:00-18:30 there is no problem. Change
> the time (except having exception, which we can set) and the "chain
> of appointments" break as discussed above. This solution is logical,
> easy to grasp, but cumbersome in some cases.
>
> Now in Lotus they may have set the name of the appointment as a
> common value. We can change everything in any of the reoccuring
> appointments, BUT the name. So as long we the name Dancig lesson it
> remains  chained together. This is logical and flexible, but very
> difficult to visualise in an easy to use way. Imagine having  Dancing
> lesson as a repeating event for 3 years while the regular time
> changed three times, had 7 exceptions, etc. How do you handle them?
> Have them listed under the appointment if it opens up? Where and how
> to indicate that that (or the other) appointments are exceptions?
>
> Coming back to the question, yes I can imagine a situation where the
> "Lotus- like" version is convenient. Actually I just have such a
> case... But on the long run it will become too detailed and difficult
> to overview.

Together with others Lotus authored the iCalendar standard (RFC 2445, 
[1]) that is also used by KOrganizer. This standard is very complex and 
after a brief glance I think it allows for one event having different 
recurrences. I haven't seen an indication for allowing different 
titles, but I haven't read the complete 150 pages document.

Given that this standard is so complex it's safe to assume that most 
implementors will only implement it partially. Esoteric features like 
several different recurrences will probably be dropped first.

I have no idea what part of the standard KOrganizer supports.


Regards,
Ingo

[1] http://www.ietf.org/rfc/rfc2445.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdepim-users/attachments/20081213/86c07715/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM users mailing list
kdepim-users at kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users