Hi Mimi, > I agree, it's not a heavy cost to have to see the prompt. However, > popping up the time zone prompt *before* subscribing to the collection > puts the user in the position of having to make a decision before they > have the information they need to make it. How will the user know if > they should turn on time zone support or not if they don't know if the > collection they're subscribing to has time zones or not? > > The pop-up should be: The collection you just subscribed to containes > time zone information. To view events and alarms correctly, we recommend > that you assign a time zone to your events and alarms as well.
It would take a little more work to distinguish between importing an ics file and subscribing to a collection in the dialog text. So text that worked for importing and subscribing would be nice. > I'm not sure I understand the performance issue. If the events being > subscribed to are floating, shouldn't they stay floating? Turning on > time zones only assigns a time zone to the users existing events, correct? The performance issue isn't huge if you don't have thousands of floating or all-day events, it's just that changing timezones means re-indexing existing floating events, so if we changed timezones before subscribing we wouldn't have to reindex. The extra indexing is significant when subscribing to the office calendar. It's working now for the dialog to pop up as soon as a timezoned event is encountered, so it's not extra work to make the behavior you describe happen. We pop up the dialog before letting users publish. How do users know if they should use timezones when publishing? I guess in that case they're imagining sharing with specific people, and they can make a decision based on where those sharees are. OK, I'm fine with going either way. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
