I’m building a group calendar application that needs to support recurring events, but all the solutions I’ve come up with to handle these events seem like a hack. I can limit how far ahead one can look, and then generate all the events at once. Or I can store the events as repeating and dynamically display them when one looks ahead on the calendar, but I’ll have to convert them to a normal event if someone wants to change the details on a particular instance of the event.
I’m sure there’s a better way to do this, but I haven’t found it yet. What’s the best way to model recurring events, where you can change details of or delete particular event instances?
(I’m using Ruby, but please don’t let that constrain your answer. If there’s a Ruby-specific library or something, though, that’s good to know.)
