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
On Fri, 07 Sep 2007 20:40:44 -0700, "Philippe Bossut" <[EMAIL PROTECTED]> said: > 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 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
