No, the current webYaST concept means that icons should be handled
with care.
One idea for a style guide text would be:
"Do not use just an icon to display an action as icons are often
perceived in a different way by different users. That means that just
displaying an icon makes it more difficult for the user to get the
meaning of an action.
To avoid confusion and ease the use of webYaST always use an icon and
some explanatory text."
[http://en.opensuse.org/YaST/Web/Docu/Style_Guide/Generic_Layout]
Concerning help:
Currently there is no explicit "help" concept in webYaST.
One reason is that usability studies showed that users often find
"Help" quite unhelpful and the other reason is that it is our aim to
create an UI which is so simple and self-explanatory that "Help"
becomes superflous.
If you want to give the user detailled information about a setting use
either prefilled input fields or a short explanatory text below the
settings label.
Do not use "help" icons, pop ups or similar stuff. These will breake
the otherwise clear and easy webYaST layout and the ease of it`s user
experience.
Try to make the wording of a setting as easy and self-descriptive as
possible.
[http://en.opensuse.org/YaST/Web/Help]
What do you think?
Cu,
Martin
On 22.02.2010, at 16:44, Katarina Machalkova wrote:
Explaining "Priorities":
An icon would be one solution, but it would break with the rest of
the
current webYaST concept.
Shall I read it as "current webYaST concept doesn't allow icons"?
Where is
this defined?
fB.
--
\\\\\ Katarina Machalkova
\\\\\\\__o YaST developer
__\\\\\\\'/_ & hedgehog painter
----------------------------------------------------------------
Martin Schmidkunz
User Experience Specialist
[email protected]
+49 (0) 911 740 53-346
-----------------------------------------------------------------
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
-----------------------------------------------------------------
Novell, Inc.
Novell® Making IT Work As One™
