[Dev] implementing recurrence in the repository

[Mike Taylor]

On Mar 28, 2005, at 11:07 AM, Alec Flett wrote:

> These last three points call for a mechanism to get future event 
> information without generating Items in the repository. That also begs 
> the question, why generate any concrete events at all if we're already 
> providing this mechanism for viewing non-concrete events? Something to 
> think about.

While it was rare, I would often go to a future recurring date entry 
and make notes for that specific entry for things like agenda or other 
date specific items.

This will be something you will have to consider - you may have to 
change a virtual future recurring event view and make it explicit but 
yet still tied to the recurring event if a user edits it.

---
Bear
http://code-bear.com

Open Source Applications Foundation (OSAF)
http://www.osafoundation.org

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20050328/5063d319/PGP.bin