On 4/20/06, Sheila Mooney <[EMAIL PROTECTED]> wrote: > Basically Scooby timezone support, as we implement it, > needs to move in lock-step with Scooby for most issues. We do understand > however that there are subtle differences in the way we need to handle > certain things (storing defaults, persisting info across sessions) and these > need to be discussed.
assuming that you mean "move in lock-step with chandler" - you could solve this problem within the constraints you've layed down by making chandler save the chosen timezone (if any) as the caldav timezone for a calendar when chandler shares/syncs the calendar. then scooby could basically not worry about timezones at all, because cosmo would always give its data back to scooby in terms of the timezone stored with the calendar (or floating, if the user never selected a timezone in chandler). _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
