Mailinglist Archive: yast-devel (105 mails)

< Previous Next >
Re: [yast-devel] Enforcing okButton and cancelButton
  • From: Ricardo Cruz <rpmcruz@xxxxxxxxxxxxxxxxxxx>
  • Date: Wed, 10 Sep 2008 15:54:40 +0100
  • Message-id: <1221058480.17885.40.camel@xxxxxxxxxx>
Seg, 2008-09-08 às 09:59 +0200, Lukas Ocilka escreveu:
Ricardo Cruz wrote:
Hi there,

Qui, 2008-09-04 às 12:51 +0200, Stefan Hundhammer escreveu:
https://bugzilla.novell.com/show_bug.cgi?id=422612

This shows that there are cases where it is legitimate to have a pop-up
dialog
with a ButtonBox with more than one button, but only an okButton and no
cancelButton:


...message...
<Countdown>

[Stop] [OK]


We (mschmidkunz + tgoettlicher + sh) thought that this is the one
exception
from that rule; in general, all dialogs with more than one button should
have
an okButton (for the regular end) and a cancelButton (as a safe escape).

I'm not sure what the problem is with this one. The Stop button is
clearly acting as a Cancel button here. It could have been re-labeled as
such, and you wouldn't know the difference.

Well, this is actually `specialButton as it doesn't cancel anything, it
stops the countdown and waits. If you click on the OK button, it's just
as it was a normal informational message with OK button only.

I see. I still see it as a cancelButton because it currently means two
slightly different roles:
* dismiss an operation. The user triggers some operation that prompts
him a dialog, so the developer offers a Cancel button in case he made a
mistake and wants to restore the previous state.
* deny an operation. A dialog asks the user about performing an
operation, allowing the user to reject it.

Probably this is functioning more in line of a No button, but either
way, I still see it as a cancelButton. Anyway, please put the "OK"
button there as the okButton, and that one as something else.

By the way, we may want to split the cancelButton by those two roles,
so we can support close dialogs like: "Some documents are not saved.
Save them? [Cancel] [No] [Yes]".
(If you do change that, you may want to consider renaming the okButton
to confirmButton, but maybe I guess I'm just being too picky. ;P)

So what the Stop button does? Changes the the countdown message to
informational message --> clearly a "special function".

Now locilka found one more exception:

...error...
[OK] [Details...]

I would vote to align that Details button as a Help button, since it
doesn't trigger an action, and it's providing information. I think I've
seen the Details button aligned to the Left in KDE error messages as
well (in Gnome, an expander is generally used, so dunno).

This idea sounds good. It's really similar to the Help button
considering the type of information it provides.

Yeah, but I think you should try to keep the Details a checkbox as you
do in some dialogs; it should then expands the dialog to show that extra
information in a plain YRichText (you guys do that at least for some
sw_single dialog as I recall...).

Cheers,
Ricardo


--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >