Hi Jeremy,
I think while this scenario is certainly possible because the UI will
allow it, it's highly unlikely to happen. People generally either
live in a world where they keep timezone information in their
head...or they turn on timezone support and have timezones on all of
their events.
Does anyone have an example of when they specifically assign a
floating timezone to an event?
I think I'm also not sure why this example necessitates a modal
prompt to turn on timezones?
I agree that if there is timezone information the CC needs to be able
to see the calendar displayed in some timezone. I'm agnostic as to
whether it's a timezone the CC assigns or it's a timezone that is
assigned for the CC based on the sharer's original calendar canvas.
But I don't think we can force the CC to get an account just to be
able to see the collection in a timezone.
Mimi
On Dec 5, 2006, at 2:41 PM, Jeremy Epstein wrote:
The alert needs to be modal (thus annoying)
let me explain:
Say there are 4 events on a collection that is nominally floating:
2 events are floating
one event is at 3pm est.
one event is at 3pm pst.
(I understand this to be a possible case, please correct if I am
wrong)
now, lets assume a user without an account (not logged in) we have
no way to determine the frame of reference to draw the two non
floating events. This was Mitch's original issue
How obvious does the prompt need to be-- obvious enough to tell you
that something is wrong with your calendar.
Do we draw the two events with timezone at the same time? (the
inital proposal) well, you could miss your meeting that way or you
may have a conflict that you don't see.
We could highlight those events, but they might get lost in the
calendar color noise. There is a lot of meaning in the calendar
already, it might even be overloaded with too much meaning.
I also do not completely agree (not that agreement is required :))
with the "what if I am in NY" argument. The primary viewer in this
case is a chandler user-- the chandler user's local system settings
never propagate to Cosmo. The CC's primarily consume content in
this unauthenticated circumstance. If they worked regularly they
would have an account if for no other reason then managing a set of
tickets in email will infuriate you after a very short while.
I'm not sure I'm following. In Bobby's scenario I think Bobby is the
CC who is looking at bcm's calendar. I agree that since mostly he's
looking at bcm's calendar and not his own, it's probably okay for the
calendar to be displayed on a PST canvas and if Bobby wants to change
the timezone to be EST, he should get an account to do that. But I
think the use case he's describing is still a CC use case. Maybe
we're saying the same thing with different words ;)
Jeremy
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
