On Dec 5, 2006, at 2:41 PM, Brian Moseley wrote:
On 12/5/06, Bobby Rullo <[EMAIL PROTECTED]> wrote:
Yes, but there a lot of workflow issues to address with this like:
i'm talking about chandler. either it can set a timezone on the
collection, or it can't. i don't really care how it chooses what to
set or whether to set anything at all. i'm simply saying that we don't
need to go burrowing through the sharer's server account details to
find any such information.
Well, this is a design discussion, so the whole point is to care
about how it gets set and how the existence of such an attribute
affects user workflow. Just because an attribute exists doesn't mean
it's a great idea to have a UI affordance in your product for it. And
if you do have such an affordance, my questions are valid whether we
are talking about Cosmo or Chandler since neither right now has such
a setting.
3) I am viewing BCM's calendar which has a timezone of
PST, but I am
in New York - how do I tell the UI that I want to view stuff in EST
regardless of what the collection timezone is?
priscilla is concerned with the cosmo-ui-user-is-not-logged-in use
case. i think it's fair to say that if you can't be bothered to create
an account and log in, you don't get to look at the calendar in any
timezone other than the one the sharer specified.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
I actually was talking about the logged in user, but I guess logged
the users' timezone setting would just override whatever the calendar
collection setting.
bobby
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
