[Pharo-project] call for better pop up messages and UI for them
hi guys I do not you but me I'm losing half of a second to read (even if I know it by hearth) this stupid window It would be so cool to have only two buttons because I do not understand what is the field input and the cancel and two buttons (Discard changes) (Keep changes) I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic .... Any taker? Stef
of course I forgot this one. Changes have not been saved. (Discard changes) (Keep changes) On Aug 19, 2009, at 11:17 PM, Stéphane Ducasse wrote:
hi guys
I do not you but me I'm losing half of a second to read (even if I know it by hearth) this stupid window
<Picture 3.png>
It would be so cool to have only two buttons because I do not understand what is the field input and the cancel
and two buttons (Discard changes) (Keep changes)
I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic ....
Any taker?
Stef_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
yes, this old dialog is really bad from a usability point of view. For your improved dialog, what does "Keep changes" do? If it is the old behavior of "Cancel" then this may be a bit misleading because nothing is saved, you just stop moving the focus away from the method. Maybe something along the lines of "Back to modified method" would be better? Adrian On Aug 19, 2009, at 23:25 , Stéphane Ducasse wrote:
<Picture 5.png>
of course I forgot this one.
Changes have not been saved.
(Discard changes) (Keep changes)
On Aug 19, 2009, at 11:17 PM, Stéphane Ducasse wrote:
hi guys
I do not you but me I'm losing half of a second to read (even if I know it by hearth) this stupid window
<Picture 3.png>
It would be so cool to have only two buttons because I do not understand what is the field input and the cancel
and two buttons (Discard changes) (Keep changes)
I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic ....
Any taker?
Stef_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
yes, this old dialog is really bad from a usability point of view.
For your improved dialog, what does "Keep changes" do? If it is the old behavior of "Cancel" then this may be a bit misleading because nothing is saved, you just stop moving the focus away from the method. Maybe something along the lines of "Back to modified method" would be better?
(Discard changes) (Don't) (Discard changes) (Don't do anything) (Discard changes) (Keep original method) <- probably better
Adrian
On Aug 19, 2009, at 23:25 , Stéphane Ducasse wrote:
<Picture 5.png>
of course I forgot this one.
Changes have not been saved.
(Discard changes) (Keep changes)
On Aug 19, 2009, at 11:17 PM, Stéphane Ducasse wrote:
hi guys
I do not you but me I'm losing half of a second to read (even if I know it by hearth) this stupid window
<Picture 3.png>
It would be so cool to have only two buttons because I do not understand what is the field input and the cancel
and two buttons (Discard changes) (Keep changes)
I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic ....
Any taker?
Stef_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Doesn't (Keep original method) imply that the old version of the method, the one before you started editing, will be kept (which would be the same like discarding the changes)? Therefore, I like best:
(Discard changes) (Don't do anything)
Or what about? (Discard changes) (Back) Adrian On Aug 20, 2009, at 09:20 , Stéphane Ducasse wrote:
yes, this old dialog is really bad from a usability point of view.
For your improved dialog, what does "Keep changes" do? If it is the old behavior of "Cancel" then this may be a bit misleading because nothing is saved, you just stop moving the focus away from the method. Maybe something along the lines of "Back to modified method" would be better?
(Discard changes) (Don't) (Discard changes) (Don't do anything) (Discard changes) (Keep original method) <- probably better
Adrian
On Aug 19, 2009, at 23:25 , Stéphane Ducasse wrote:
<Picture 5.png>
of course I forgot this one.
Changes have not been saved.
(Discard changes) (Keep changes)
On Aug 19, 2009, at 11:17 PM, Stéphane Ducasse wrote:
hi guys
I do not you but me I'm losing half of a second to read (even if I know it by hearth) this stupid window
<Picture 3.png>
It would be so cool to have only two buttons because I do not understand what is the field input and the cancel
and two buttons (Discard changes) (Keep changes)
I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic ....
Any taker?
Stef_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Aug 20, 2009, at 9:25 AM, Adrian Lienhard wrote:
Doesn't (Keep original method) imply that the old version of the method, the one before you started editing, will be kept (which would be the same like discarding the changes)?
Therefore, I like best:
(Discard changes) (Don't do anything)
Or what about?
(Discard changes) (Back)
yes this one or the previous one is good. Stef
Adrian
On Aug 20, 2009, at 09:20 , Stéphane Ducasse wrote:
yes, this old dialog is really bad from a usability point of view.
For your improved dialog, what does "Keep changes" do? If it is the old behavior of "Cancel" then this may be a bit misleading because nothing is saved, you just stop moving the focus away from the method. Maybe something along the lines of "Back to modified method" would be better?
(Discard changes) (Don't) (Discard changes) (Don't do anything) (Discard changes) (Keep original method) <- probably better
Adrian
On Aug 19, 2009, at 23:25 , Stéphane Ducasse wrote:
<Picture 5.png>
of course I forgot this one.
Changes have not been saved.
(Discard changes) (Keep changes)
On Aug 19, 2009, at 11:17 PM, Stéphane Ducasse wrote:
hi guys
I do not you but me I'm losing half of a second to read (even if I know it by hearth) this stupid window
<Picture 3.png>
It would be so cool to have only two buttons because I do not understand what is the field input and the cancel
and two buttons (Discard changes) (Keep changes)
I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic ....
Any taker?
Stef_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Why can't it be done *exactly* the same way as it is handled in all "reasonable" desktop applications such Apple Works or Microsoft Office? Do you want to accept the changes you made? Your changes will be lost if you don't accept them. Don't Accept Cancel Accept Cheers, Lukas 2009/8/20 Stéphane Ducasse <stephane.ducasse@inria.fr>:
On Aug 20, 2009, at 9:25 AM, Adrian Lienhard wrote:
Doesn't (Keep original method) imply that the old version of the method, the one before you started editing, will be kept (which would be the same like discarding the changes)?
Therefore, I like best:
(Discard changes) (Don't do anything)
Or what about?
(Discard changes) (Back)
yes this one or the previous one is good.
Stef
Adrian
On Aug 20, 2009, at 09:20 , Stéphane Ducasse wrote:
yes, this old dialog is really bad from a usability point of view.
For your improved dialog, what does "Keep changes" do? If it is the old behavior of "Cancel" then this may be a bit misleading because nothing is saved, you just stop moving the focus away from the method. Maybe something along the lines of "Back to modified method" would be better?
   (Discard changes) (Don't)    (Discard changes) (Don't do anything)    (Discard changes) (Keep original method)     <- probably better
Adrian
On Aug 19, 2009, at 23:25 , Stéphane Ducasse wrote:
<Picture 5.png>
of course I forgot this one.
  Changes have not been saved.
      (Discard changes)   (Keep changes)
On Aug 19, 2009, at 11:17 PM, Stéphane Ducasse wrote:
hi guys
I do not you but me I'm losing half of a second to read (even if I know it by hearth) this stupid window
<Picture 3.png>
It would be so cool to have only two buttons because I do not understand what is the field input and the cancel
and two buttons  (Discard changes) (Keep changes)
I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic ....
Any taker?
Stef_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
Good point! Adrian On Aug 20, 2009, at 09:41 , Lukas Renggli wrote:
Why can't it be done *exactly* the same way as it is handled in all "reasonable" desktop applications such Apple Works or Microsoft Office?
Do you want to accept the changes you made? Your changes will be lost if you don't accept them.
Don't Accept
Cancel Accept
Cheers, Lukas
2009/8/20 Stéphane Ducasse <stephane.ducasse@inria.fr>:
On Aug 20, 2009, at 9:25 AM, Adrian Lienhard wrote:
Doesn't (Keep original method) imply that the old version of the method, the one before you started editing, will be kept (which would be the same like discarding the changes)?
Therefore, I like best:
(Discard changes) (Don't do anything)
Or what about?
(Discard changes) (Back)
yes this one or the previous one is good.
Stef
Adrian
On Aug 20, 2009, at 09:20 , Stéphane Ducasse wrote:
yes, this old dialog is really bad from a usability point of view.
For your improved dialog, what does "Keep changes" do? If it is the old behavior of "Cancel" then this may be a bit misleading because nothing is saved, you just stop moving the focus away from the method. Maybe something along the lines of "Back to modified method" would be better?
(Discard changes) (Don't) (Discard changes) (Don't do anything) (Discard changes) (Keep original method) <- probably better
Adrian
On Aug 19, 2009, at 23:25 , Stéphane Ducasse wrote:
<Picture 5.png>
of course I forgot this one.
Changes have not been saved.
(Discard changes) (Keep changes)
On Aug 19, 2009, at 11:17 PM, Stéphane Ducasse wrote:
hi guys
I do not you but me I'm losing half of a second to read (even if I know it by hearth) this stupid window
<Picture 3.png>
It would be so cool to have only two buttons because I do not understand what is the field input and the cancel
and two buttons (Discard changes) (Keep changes)
I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic ....
Any taker?
Stef_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch < confirmation .png
<confirmation2.png>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
probably we shoudl try it for me I'm always stopped and forced to read this stuff while it should be totally intuitive stef On Aug 20, 2009, at 9:41 AM, Lukas Renggli wrote:
Why can't it be done *exactly* the same way as it is handled in all "reasonable" desktop applications such Apple Works or Microsoft Office?
Do you want to accept the changes you made? Your changes will be lost if you don't accept them.
Don't Accept
Cancel Accept
Cheers, Lukas
2009/8/20 Stéphane Ducasse <stephane.ducasse@inria.fr>:
On Aug 20, 2009, at 9:25 AM, Adrian Lienhard wrote:
Doesn't (Keep original method) imply that the old version of the method, the one before you started editing, will be kept (which would be the same like discarding the changes)?
Therefore, I like best:
(Discard changes) (Don't do anything)
Or what about?
(Discard changes) (Back)
yes this one or the previous one is good.
Stef
Adrian
On Aug 20, 2009, at 09:20 , Stéphane Ducasse wrote:
yes, this old dialog is really bad from a usability point of view.
For your improved dialog, what does "Keep changes" do? If it is the old behavior of "Cancel" then this may be a bit misleading because nothing is saved, you just stop moving the focus away from the method. Maybe something along the lines of "Back to modified method" would be better?
(Discard changes) (Don't) (Discard changes) (Don't do anything) (Discard changes) (Keep original method) <- probably better
Adrian
On Aug 19, 2009, at 23:25 , Stéphane Ducasse wrote:
<Picture 5.png>
of course I forgot this one.
Changes have not been saved.
(Discard changes) (Keep changes)
On Aug 19, 2009, at 11:17 PM, Stéphane Ducasse wrote:
hi guys
I do not you but me I'm losing half of a second to read (even if I know it by hearth) this stupid window
<Picture 3.png>
It would be so cool to have only two buttons because I do not understand what is the field input and the cancel
and two buttons (Discard changes) (Keep changes)
I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic ....
Any taker?
Stef_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch < confirmation .png
<confirmation2.png>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
For another example, in OpenOffice style, the dialog would read: The method "XXX" has been modified Do you want to accept your changes? and the three buttons used are: - Accept (Accept and leave) - Discard (Don't accept, but leave) - Cancel (Don't accept and stay) Personally, I find Discard to be a better choice of words than Don't Accept, but the ordering in the others is better, since there's less chance of incidentally not saving your changes since Discard button is by itself. (Btw: the dialog in Works/Office is misleading, as you WON'T lose your changes if you press cancel...) Cheers, Henry On Aug 20, 2009, at 9:54 34AM, Stéphane Ducasse wrote:
probably we shoudl try it for me I'm always stopped and forced to read this stuff while it should be totally intuitive
stef
On Aug 20, 2009, at 9:41 AM, Lukas Renggli wrote:
Why can't it be done *exactly* the same way as it is handled in all "reasonable" desktop applications such Apple Works or Microsoft Office?
Do you want to accept the changes you made? Your changes will be lost if you don't accept them.
Don't Accept
Cancel Accept
Cheers, Lukas
2009/8/20 Stéphane Ducasse <stephane.ducasse@inria.fr>:
On Aug 20, 2009, at 9:25 AM, Adrian Lienhard wrote:
Doesn't (Keep original method) imply that the old version of the method, the one before you started editing, will be kept (which would be the same like discarding the changes)?
Therefore, I like best:
(Discard changes) (Don't do anything)
Or what about?
(Discard changes) (Back)
yes this one or the previous one is good.
Stef
Adrian
On Aug 20, 2009, at 09:20 , Stéphane Ducasse wrote:
yes, this old dialog is really bad from a usability point of view.
For your improved dialog, what does "Keep changes" do? If it is the old behavior of "Cancel" then this may be a bit misleading because nothing is saved, you just stop moving the focus away from the method. Maybe something along the lines of "Back to modified method" would be better?
(Discard changes) (Don't) (Discard changes) (Don't do anything) (Discard changes) (Keep original method) <- probably better
Adrian
On Aug 19, 2009, at 23:25 , Stéphane Ducasse wrote:
<Picture 5.png>
of course I forgot this one.
Changes have not been saved.
(Discard changes) (Keep changes)
On Aug 19, 2009, at 11:17 PM, Stéphane Ducasse wrote:
hi guys
I do not you but me I'm losing half of a second to read (even if I know it by hearth) this stupid window
<Picture 3.png>
It would be so cool to have only two buttons because I do not understand what is the field input and the cancel
and two buttons (Discard changes) (Keep changes)
I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic ....
Any taker?
Stef_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch < confirmation .png
<confirmation2.png>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I agree. I must add that order is relevant. Our culture thinks progress from the left to the right. The contrary direction means to go backwards (like not doing or undoing something). That's why the buttons to regret from an action are at the left and the commit kind of buttons at the right. And yes, that's why windows does it broken for western cultures. To create intelligent stuff you need to know when to stop being creative. cheers, sebastian
-----Mensaje original----- De: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] En nombre de Lukas Renggli Enviado el: Thursday, August 20, 2009 04:41 Para: Pharo-project@lists.gforge.inria.fr Asunto: Re: [Pharo-project] call for better pop up messages and UI for them
Why can't it be done *exactly* the same way as it is handled in all "reasonable" desktop applications such Apple Works or Microsoft Office?
Do you want to accept the changes you made? Your changes will be lost if you don't accept them.
Don't Accept
Cancel Accept
Cheers, Lukas
2009/8/20 Stéphane Ducasse <stephane.ducasse@inria.fr>:
On Aug 20, 2009, at 9:25 AM, Adrian Lienhard wrote:
Doesn't (Keep original method) imply that the old version of the method, the one before you started editing, will be kept
(which would
be the same like discarding the changes)?
Therefore, I like best:
(Discard changes) (Don't do anything)
Or what about?
(Discard changes) (Back)
yes this one or the previous one is good.
Stef
Adrian
On Aug 20, 2009, at 09:20 , Stéphane Ducasse wrote:
yes, this old dialog is really bad from a usability
point of view.
For your improved dialog, what does "Keep changes" do?
If it is the
old behavior of "Cancel" then this may be a bit misleading because nothing is saved, you just stop moving the focus away from the method. Maybe something along the lines of "Back to modified method" would be better?
   (Discard changes) (Don't)    (Discard changes) (Don't do anything)    (Discard changes) (Keep original method)     <- probably better
Adrian
On Aug 19, 2009, at 23:25 , Stéphane Ducasse wrote:
<Picture 5.png>
of course I forgot this one.
  Changes have not been saved.
      (Discard changes)   (Keep changes)
On Aug 19, 2009, at 11:17 PM, Stéphane Ducasse wrote:
hi guys
I do not you but me I'm losing half of a second to
read (even if I
know it by hearth) this stupid window
<Picture 3.png>
It would be so cool to have only two buttons because I do not understand what is the field input and the cancel
and two buttons  (Discard changes) (Keep changes)
I'm so stupid: I do not understand what is cancel here (of course this is cancel the change of method but in UI flow I do not know that I was selecting or changing - now I get this crappy question and I panic ....
Any taker?
Stef_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
Em 20/08/2009 04:20, Stéphane Ducasse < stephane.ducasse@inria.fr > escreveu:
yes, this old dialog is really bad from a usability point of view.
For your improved dialog, what does "Keep changes" do? If it is the old behavior of "Cancel" then this may be a bit misleading because nothing is saved, you just stop moving the focus away from the method. Maybe something along the lines of "Back to modified method" would be better?
(Discard changes) (Don't) (Discard changes) (Don't do anything) (Discard changes) (Keep original method) <- probably better
Yes, but for other panes you'll need to change the text, for example if you edit comments, the word "method" will not make sense...
participants (6)
-
Adrian Lienhard -
csrabak＠bol.com.br -
Henrik Johansen -
Lukas Renggli -
Sebastian Sastre -
Stéphane Ducasse