Mailinglist Archive: yast-devel (55 mails)

< Previous Next >
[yast-devel] YaST Dialog Button Order in KDE
  • From: Lukas Ocilka <lukas.ocilka@xxxxxxx>
  • Date: Wed, 31 Aug 2011 10:35:15 +0200
  • Message-id: <4E5DF243.3020401@suse.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I've got a very nice bug - actually a never-ending story - about button
order in YaST dialogs. This one is not about using ButtonBox widget (at
least not from the developer's point of view) because the inconsistency
is in our design of the whole Wizard dialog.

See https://bugzilla.novell.com/show_bug.cgi?id=571939
Especially https://bugzillafiles.novell.org/attachment.cgi?id=339226

[Cancel] [OK] button order

The root of the issue is, from my POV, the way how we define the Wizard
behavior and how we later work with it, e.g., by calling
SetNextButton(any id, string label). We often use this approach for
configuration wizards:

[/Back/][Next]
[Back] [Next]
[Back] [Finish]

According to Keith Briscoe, who's already reported several
button-order-related bugs, this is in fact a bug considering our wiki
page http://old-en.opensuse.org/YaST/Development/Misc/Button_Order and
also considering the KDE style that tries to follow a human-speech order.

[OK] / [Apply] / [Continue] / [Finish] / [Yes] / ...

always presented before

[Cancel] / [No] / ...

So, in Wizard, we still use the GNOME button order although YaST runs in
KDE. I think that we could try to change the order in Wizard.ycp (or, in
fact, in its Qt implementation) but it would be quite a big change and
it needs to be discussed first. And that I wrote this e-mail :)

Thanks in advance for your ideas and opinions
Lukas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk5d8kIACgkQVSqMdRCqTix2agCfel5xmACjnrjWIxtimo0B5qPN
4VkAnRHOQN3kyK7+JHYU35Cjku0voTyY
=n+Ry
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
List Navigation