My concerns with the 'Hey you can't create an item in this
collection.' error message are:
+ The message may not make sense. It is 1-step removed from the goal
they have in their mind, which is to reply or forward an existing
message. They aren't actually trying to create a new item in the
selected, a new item gets crreated in the selected as a result of
hitting Reply/Forward in the toolbar, but that's a mechanism inside
the app that the user would have to understand before they could
understand that error message.
+ It's true of the Trash collection, but not true of the Out
collection because users can create new outbound messages in the Out
collection.
But my first preference would be to allow users to Reply/Forward in
all collections and if they're in the Trash or Out collection, don't
create an item in the collection and don't switch the user out of the
collection.
If we can't do that, I'd prefer to just switch the user out of the
collection into the Out collection, or we could drop them in the
Dashboard? that might be better.
Mimi
On Mar 6, 2007, at 11:52 AM, Brian Kirsch wrote:
On Mar 5, 2007, at 5:26 PM, Mimi Yin wrote:
Hi Brian,
I agree :o) The only place where this gets weird is if you're in
the IN collection or say the Trash collection. Could we make
exceptions for that?
It should be possible to prevent users from creating items in the
Trash and In collection. I think this might be the best behavior.
I would be more in favor of warning the user that it is not
possible to create items in the In or Trash collections rather
than just switching the collection they are working in.
I think it is unlikely someone would intentionally want to actually
create something in the In or Trash collection. It would
probably be the result of not realizing they had that collection
selected. In which case we don't want to go make matters
worse by switching the collection again.
It should be noted that the Out collection might want to have the
same limitations as the In collection in that only things from
"me" appear
in the Out. If no "me" has yet been configured then what does that
mean?
We could even stay in the IN/Trash collections, but just not add
the item to those collections. I'm not sure if that's possible
I believe this might be over thinking the problem and leading to
more developer work then is needed. How about a
nice "Hey you can't create an item in this collection" or a "Hey
you can't create an item in this collection.
Would you like to add the item to the Dashboard?" popup. The latter
would add the item to the dashboard
and select the dashboard collection.
. That would require displaying an item in the Detail View that
doesn't exist in the currently selected collection. Otherwise, we
can just switch to the OUT collection.
I am not in favor of switching to the Out collection.
Honestly, I think for Preview just the "Hey you can't create an
item in this collection" popup is enough.
Thanks,
Brian
Mimi
PS I think Aparna logged a bug about this, or something very like
this: https://bugzilla.osafoundation.org/show_bug.cgi?id=8171
On Mar 5, 2007, at 6:15 PM, Brian Kirsch wrote:
Hello,
I would like to suggest that we do not change the sidebar
collection when Replying and Forwarding mail.
Currently, when a user hits reply or forward the out collection
is selected and the focus put on the mail message.
I think this is very counter intuitive to current mail apps. It
is very easy for a user not realize that the collection
they were working in has changed.
So here is a scenario I hit a couple of times today while testing
the reply / forward logic.
I am working in the dashboard. I select a mail to reply to. I hit
reply. I respond to the message and send it.
I then hit sync and see that new mail is being downloaded.
However, I don't see the mail in Chandler.
My first thought and I believe the first users thought will be
that something is not working correctly (bug).
Why?
Because I was working in the Dashboard and Chandler decided to
move on its own to the Out collection.
In a traditional mail app (Thunderbird, Outlook, etc) the folder
one is reading and responding to mail in
does not change because a user hits the reply or forward button.
To sum up I think users will get confused and I don't see a
benefit to doing it.
Thats my two sense.
Thoughts?
-Brian
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
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
