please find a new version of the YaST style guide draft at: http://en.opensuse.org/Image:Ysg2.pdf
The goal is to have a developer friendly style guide which ensures the greatest possible consistency between various modules and various environments.
The time line for the style guide is to discuss it the next two weeks and to have an executable style guide by the end of the YaST workshop.
I would like to ask and encourage you again to discuss it! What do you like? What do you dislike? What is missing?
Just to come up with some points of discussion: * button labeling: OK/Cancel instead of Apply/Accept/Abort/... and Next/Back/Cancel/Finish in a wizard/add workflow I know OK/Cancel is not 100% correct but with these two labels we are consistent to GNOME HIG and KDE http://library.gnome.org/devel/hig-book/stable/windows-utility.html.en#expli... http://developer.kde.org/documentation/standards/kde/style/dialogs/index.htm...
* Progress dialogs I propose to skip the cancel button because I made the experience that in many cases the cancel button does not work
* Number of steps in a wizard I propose to skip the display of "Step XX of XX" because the number of steps can not predicted in every module
* colons In accordance to GNOME (http://library.gnome.org/devel/hig-book/stable/controls-option-menus.html.en) and KDE style guide (http://developer.kde.org/documentation/standards/kde/style/basics/labels.htm...) I propose to use colons with the label of a combo box
And of course there might be many more issues worth to be discussed :-)
The style guide is based on the style guide in the wiki (http://en.opensuse.org/YaST/Style_Guide) developed by Lukas and me and when we agreed on one version it will be published in the openSUSE wiki again.
Looking forward to your opinions!
Hi, Seg, 2008-06-23 às 17:34 +0200, Martin Schmidkunz escreveu:
- Number of steps in a wizard
I propose to skip the display of "Step XX of XX" because the number of steps can not predicted in every module
Can't you just write some rules to deal with those cases in the most satisfactory, predictable manner possible? like: - start counting after first step if necessary. e.g. user clicks "add printer". you first may have to ask whether it is locally connected, network or something before you start counting. - skip if obvious those steps don't need to be taken. e.g. if the user ticks off the "test printer" check then it's already to skip a step. - only count users interactions. e.g. if some software needs to be installed at some point, those don't count. Maybe limiting steps to Next button hits.
The goal here is to make things a bit more predictable. If the counter advances two steps or whatever, it's still better than keeping the user in the darkness.