My interpretation of "leaving the user in a lurch" is as follows. When
you encounter a dialog that says your next action can cause all your
data may be deleted, many people may become somewhat alarmed and want to
be very careful about what next step they take. The problem to me in
this situation is that "cancel" is not as explicitly a safe move as
something like "quit without deleting data". If you don't want to
delete your data it is very comforting to be presented with a choice
that is very explicit that it won't delete the data, whereas a plain
cancel button makes me question "what exactly am I canceling".
As for three choices rather than two I imagine that if you encountering
this dialog for the sixth time of the morning you probably don't need to
see instructions on what to do. If you have never encountered the
dialog before having an easy way to access instructions on how to
proceed would likely be appreciated.
Those were my thoughts when coming up with the three choices.
Dan
Mimi Yin wrote:
Hi Philippe,
I'm not sure I understand how this leaves the user in a lurch. Is it
because your only options are to delete your data or cancel out of
start up?
What if instead of [Cancel], we had [Move Data] and that was a link to
the migration instructions?
My concern is that we need to explain to the user that we need to
delete their data in order to start Chandler. Just something to
explicitly connect the dots between "your data is incompatible with
this version of Chandler'
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.
Mimi
On Sep 5, 2007, at 3:56 PM, Philippe Bossut wrote:
Mimi Yin wrote:
What if we just made it a 2 button dialog? (Also trying to avoid
jargon like repository and migrate.)
===
Your data was created by an incompatible version of Chandler.
In order to proceed, all of your existing data must be deleted. To
preserve your data, <LINK>follow instructions on how to move data
from one version of Chandler to another.
[Cancel] [Delete Data]
===
I think it leaves the user too much in a lurch. I prefer the 3
options proposed by Dan: at that point in the code, there are few
enough things to do that we can afford to be super detailed and
explicit for each.
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
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
