This isn't really a discussion related to CakePHP as it's more of an
application concept or database scheme query.  Dealing with repeat
events is normally the difference between a basic calendar and an
advanced calendar and I did some research into this some time back
with various google searches and there was no definitive answer.

I would say you need to create multiple event records all linked to
the original event created.  This way you can add add different
comments to each event or move one instance of a repeating event by a
couple of hours or a day without it affecting past/future events.

The next question is how many instances of the event do you create?
Whilst I do not yet have a definitive answer to this it doesn't take a
rocket scientist to know that automatically creating an infinite
number of events is not a clever idea.  I would probably provide start
and end date fields when adding editing a repeat event so the user
specifies how many instances are created and once the end date has
been reached an alert is triggered to review the repeat event
settings.

This leaves you with the challenge of dealing with the frequency
variable.  Daily/Every Saturday/Bi-weekly on a Saturday are easy
options, but what about First Thursday or Last Thursday as events are
not likely to occur on specific dates such as the 23rd of every month.

Would love to hear how you approach this issue ... I will be working
on this soon as I'm currently developing a Contact Relationship
Management app so we may be able to help one another.  I have been
modelling my calendar application on Mozilla ThunderBird (Lightning
Extension).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to