From kdepim-users Sat Dec 13 11:39:36 2008 From: Ingo =?utf-8?q?Kl=C3=B6cker?= Date: Sat, 13 Dec 2008 11:39:36 +0000 To: kdepim-users Subject: Re: [kdepim-users] Editing a recurring appointment Message-Id: <200812131239.36630 () thufir ! ingo-kloecker ! de> X-MARC-Message: https://marc.info/?l=kdepim-users&m=122916844603988 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1608344170==" --===============1608344170== Content-type: multipart/signed; boundary=nextPart5696023.u79hQxkWZ2; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit --nextPart5696023.u79hQxkWZ2 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 12 December 2008, =C3=81kos Szederjei wrote: > On Friday 12 December 2008 21:29:43 Anne Wilson wrote: > > On Friday 12 December 2008 20:21:06 =C3=81kos 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.=C5=B1 > > > > > > =C3=81kos > > > > =C3=81kos, 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,=20 [1]) that is also used by KOrganizer. This standard is very complex and=20 after a brief glance I think it allows for one event having different=20 recurrences. I haven't seen an indication for allowing different=20 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=20 implementors will only implement it partially. Esoteric features like=20 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 --nextPart5696023.u79hQxkWZ2 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAklDnvgACgkQGnR+RTDgudjfXQCfZI0sRtMJU0FF2Nu3F5gHNrlE jTkAoKkrSQO/Og5zCnISiyJS0h02QV51 =wc2p -----END PGP SIGNATURE----- --nextPart5696023.u79hQxkWZ2-- --===============1608344170== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ KDE PIM users mailing list kdepim-users@kde.org https://mail.kde.org/mailman/listinfo/kdepim-users --===============1608344170==--