Which is worse?
1) having to reset the timezone 100% of time with an annoying alert
2) the possibility you might have to reset the timezone some of the time.
A CC could change their view of the ecalendar.
Bobby Rullo wrote:
What if any user signs up for a Cosmo account, they have to pick a
working time-zone as part of sign up. This includes signing up for a
Cosmo account for Chandler too. This would mean all Cosmo accounts
would have a working time-zone. When a Casual Collaborator user
without a Cosmo account clicks on a URL/ticket, the working time-zone
used is from the Chandler user's Cosmo account to set the default
time-zone on the calendar canvas. If an account is in floating
time-zone, give it a working time-zone so it's still possible to
figure out where to put individual events with time-zones.
The problem with this is that when the user who created the calendar
changes their account's timezone, everyone all of a sudden sees
something different.
For example, I create a collection while my timezone is set to PST for
my Cosmo workmates to share, some of who don't want a Cosmo account.
Then I go to NY to work there a while and switch my timezone to EST
and all the CC's viewing the calendar see all the events in NY time.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
