Sorry for not explaining better my rationales. It was a combination
of the following concerns:
a) That there is still too much up in the air design-wise. I talked
to Priscilla this weekend about it and am less seems to be up in the
air than I thought. Just to make sure that we're all on the same page
about what would be included if we don't defer, I'll briefly
summarize my understanding of the features at the end of this email.
b) That there would be scheduling concerns implementing the full
timezone proposal for 0.6 that would take us away from the cas.
collab workflow stuff. We have no mechanisms right now to view events
relative to any other timezone (including floating) and we don't have
a Preference/Settings panel yet (although it is slated for this
release.) I'm not sure how hard it is to do the former or how long
it'll take to do the latter since I'm not that familiar with the code
which places events on the canvas, and mde's doing the preference
panel. Since I'm not sure of the difficulty of either of these things
or where in Matthew's schedule the prefs are in relation to the rest
of cas. collab. I was concerned. Matthew, could you speak to these
issues here?
After speaking with Priss and Ted, it seems that it would be
reasonable to stop working on timezones right now and start working
on the casual collaborator stuff and see if we have time for the rest
of the timezone functionality after the CC stuff is done. My
understanding of the remaining functionality is:
a) Option to turn timezones on/off in the preference panel
b) Timezone selector in the preference panel to choose "default
timezone"
c) Timezone selector on the calendar canvas which does the same thing
d) Timezone selectors have a floating timezone option
e) Non-logged in users see events in floating time
f) user notification when logged in user with timezones turned off
is viewing a collection with events that have timezones *** in
discussion
g) new events automatically are populated with whatever timezone is
the default timezone.
Bobby
On Dec 1, 2006, at 3:40 PM, Ted Leung wrote:
Hi Bobby,
Just looking to get some more information here. Are you proposing
to defer these items because of impacts to the Cosmo 0.6
schedule? I'm not sure I understand the rationale behind deferring.
Thanks,
Ted
On Dec 1, 2006, at 3:03 PM, Bobby Rullo wrote:
Sheila,
My proposed staging would have the editing of timezones for
events. Again the only things lacking would be
1) Turning off timezones (floating mode)
2) Choosing what timezone to view events in
Instead, you'd always see events on the canvas placed relative to
your browser's timezone.
On Dec 1, 2006, at 2:28 PM, Sheila Mooney wrote:
I have no real objection to staging the timezone features but the
main advantage for us to try and get this into 0.6 is so we can
test it. I expect we will find some bugs editing timezones for
the same calendar via both Chandler and Cosmo. I know it's taken
us a while to flush out all the timezone bugs in the desktop.
Ted, Priscilla, you are more familiar with the cost of
implementing the proposed deferred features and how these
prioritize against the other 0.6 features (stuff we could defer
if we wanted to do all the timezone work).
On Nov 30, 2006, at 1:32 PM, Bobby Rullo wrote:
Sorry for not responding earlier.
This all makes good sense.
However, the way things work right now, even after basic
timezone support has been added is that since we don't yet have
the concept of user preferred timezones, or the ability to
display within a particular timezone, the UI displays events on
the canvas in whatever timezone your browser happens to be in.
Events w/o a timezone float, but there is no facility to make
the ALL events float (i.e. turning TZ support off) or to choose
what timezone to view you calendar in.
Can we defer those features for the next release, or do you
think they are a priority for this one? Again the features to be
deferred would be:
1) Turning off/on timezone support
2) Choosing what timezone to view events in on the canvas.
What we will have in 0.6 no matter what:
1) timezone infrastructure work done
2) Editing timezones for events in the Cosmo UI
Bobby
On Nov 30, 2006, at 12:03 PM, Priscilla Chung wrote:
I sent this out last week and wanted to follow up if anyone had
any last comments.
Thanks, -Priscilla
On Nov 21, 2006, at 12:16 PM, Priscilla Chung wrote:
Mimi send out a summary of the time-zones on the Cosmo UI:
http://lists.osafoundation.org/pipermail/design/2006-November/
005724.html
I just wanted to pull it out of the 'Login-related workflows
update' thread to confirm the direction we're taking:
*Not Logged-in Cosmo*
+ The calendar canvas will be viewed in floating time-zone
(ie. if you have 2 events at 2:00pm PST and 2:00pm EST, they
both show up at 2:00pm)
+ Clicking on an individual event will display the time-zone
information it was created in the detail view (ie. PST, EST etc).
*Logged-into Cosmo*
+ If time-zone support is turned off, the calendar canvas
displays events in floating time. Selecting on individual
events displays no information about time-zones in the detail
view. There are no labels for the calendar canvas, the
collection and for the individual item.
+ If time-zone support is turned on, then the user will make a
selection from the pull down (where Floating is one of the
options). Based on the selection, the events will adjust
accordingly on the calendar canvas. When selecting on the
individual events the time-zone information will appear in the
detail view.
*Note: When you subscribe to a collection and add it to your
Cosmo account:
*If time-zone support is turned on*
+ Based on the selection, the events will adjust accordingly
on the calendar canvas. When selecting on the individual
events the time-zone information will appear in the detail
view based on the time-zone it was created in.
*If time-zone support is turned off*
+ The events appear positioned on the canvas in floating
time. Selecting on individual events displays no information
about time-zones in the detail view. There are no labels for
the calendar canvas, the collection and for the individual item.
Understandably, this last case (if TZ is turned off) may not
be as fluid as we'd like, especially when you just saw the
time-zone before subscribing. I'm just going to file a bug to
revisit the time-zone issue for future.
-Priscilla
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
