Oh sorry, I misspoke, I meant apply timezones to all events in your
Chandler, except for the ones explicitly shared to as Floating by
other people.
On Dec 8, 2006, at 4:00 PM, Jeffrey Harris wrote:
Hi Mimi,
Mimi Yin wrote:
On Dec 7, 2006, at 11:49 AM, Jeffrey Harris wrote:
It's not clear to me, though, what happens when you say OK. Do we
convert existing floating events to have timezones? Or does this
really
mean "assign timezones to new events you create"?
No to existing events in that collection.
Changing timezones from floating on a collection by collection basis
seems problematic. What if you drag floating events from other
collections into that already converted collection? We'd need to
start
tracking which collections have been converted and which haven't, that
starts to sound complicated.
I don't think there's a perfect way to deal with floating events
that
already exist, since they could be shared events coming from
someone who
wants them floating...
Hmmm. Well hopefully with this prompt approach, this will be rare.
Can
we tell if it's an event from somebody else and special case those
events?
Well, I suppose we could change all events that don't live in an
already
shared collection. I think if we pop up this prompt before we
subscribe
to a shared collection, mostly people who are timezoners will switch
before they even have a chance to subscribe to any floating events.
Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
