Well in this case, unlike 'upgrade prompts' this dialog pops up
*after* you've already taken the time and trouble to find and
download a new version of Chandler.
But I agree with the spirit of what both you and Andre are saying,
that's what the [Cancel] button does. I was simply questioning
whether users would launch their newly downloaded version of Chandler
and cancel multiple times a day.
Mimi
(I wouldn't normally expend this much energy on a dialog, but I think
we all sense that this one is especially important to get right! So I
appreciate everyone's patience and persistence in discussing this.)
On Sep 7, 2007, at 8:40 PM, Philippe Bossut wrote:
Mimi Yin wrote:
I also don't think we need to give the user 3 options. They either
want to proceed, delete their data and start with a fresh
Chandler; OR they want to follow instructions to dump/reload and
cancel out of starting up Chandler for now.
OR they don't "want" anything, they're just not ready for any of
this and would prefer to simply relaunch their old version and get
back to work.
That's what the 3rd case in Dan's proposal covers. I think "do
nothing" is a very valid choice, especially for a busy user. I
can't tell you how many time I clicked "Not now" in upgrade dialogs
in countless applications...
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
On Sep 7, 2007, at 9:12 PM, Andre Mueninghoff wrote:
Philippe, I think you've captured the crux of the point. At the first
sign of potential complexity or unknowns, frequently not only the
impulse, but the time-constrained, conservative next step is to
want to
retain the current state, and deal with the complex, new, or unknown
later. It's the triage workflow for this item, not now, not done, that
is, later.
Enjoy, Andre
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
