[Design] [Proposal] Recurring events in Cosmo

[Bobby Rullo]

Priscilla,

This is not exactly what I thought we were talking about in IRC,  
which was a much simpler solution that would fix things in the short  
term:

	* In Chandler and/or Scooby, just make the "recurrence end date" UI  
element default to one year in the future. If the user wants to  
change it, they can.

No hidden anything, no changes to Cosmo, just a temporary workaround  
until the Cosmo issue is sorted, which it might be soon anyway.

Bobby


On Apr 18, 2006, at 12:16 PM, Priscilla Chung wrote:

> Currently Cosmo hangs when you create/edit a recurring event with  
> no end date. The reason Cosmo hangs is because it creates an new  
> event for each recurrence until 2059. For example a weekly meeting  
> involves creating something on the order of 2500 events, which  
> makes Cosmo slow.
> I think the Cosmo team is looking to reduce this to 2008.
>
> This is a serious issue affecting the performance of Scooby.
>
> The Scooby team is proposing a work around to add a default end  
> date (say 1 year) to the recurring events and a flag to tell Cosmo  
> that there is no end date. This way Cosmo will only create 52  
> events for that weekly recurrence. When the year passes, Cosmo  
> checks the flag and adds another year tot he recurring event.
>
> The most important thing is that the user doesn't see the man  
> behind the curtain and doesn't have to add an end. For example, it  
> would be bad form to add an end to a birthday event.
>
> This may require an additional attribute for the Chandler team to  
> add to recurring events. Depending on how Cosmo implement things  
> (Perhaps someone from the Cosmo team can chime in here.)
>
> What am I asking for:
> + Is there any feedback on the Chandler/Cosmo side to help solve  
> this problem?
>
> -Priscilla
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060418/5cfca200/attachment.htm