[chandler-users] [d/f] Assorted Usage Notes
jeffrey at osafoundation.org
Mon Jun 25 15:23:16 PDT 2007
Thanks for the ongoing "outside the development bubble" feedback, Andre.
> Is Update/Notify perhaps really intended for propagating changes to
> non-Chandler users? If so, maybe the label or tool-tip could
> clarify/amplify that intended purpose. If I'm missing the point, I
> apologize. Wanted to give you my candid impulse response without
> peeking first at the spec.
Actually, I think Update is targeted equally at Chandler users. For
instance, if I'm editing a get-together amongst an ad hoc group of
friends, the item may start as an outline without the formality of a
I imagine in this case, I'd send out a tentative event to a few friends,
and they'd reply with counter-proposals and discussion (whether they
were Chandler users or not). But as agreement was reached on details,
that could be reflected as an update to the original item, so the
outline could grow into a clear, centralized plan. Does that use case
Regarding the fact that the Update/Notify button doesn't immediately
convey I'm-going-to-send-an-email (which is a good point), how about if
we changed the button's title to Update by Email?
That suffers from the fact that it's kind of long for a toolbar item,
but it seems much clearer. I guess the Send state could be called Send
by Email then, too. I know we want to emphasize communication (could be
Jabber, say) instead of Email, but for Preview, we're just doing email.
I must confess I'm enamored of the way the icon states for updates look
like U's which connect to Update in my mind. That's not going to be
true in non-English languages so I probably shouldn't be attached, but
still, I prefer Update to Notify if we can use more text to clarify what
More information about the chandler-users