http://bugzilla.novell.com/show_bug.cgi?id=547075
User rpmcruz@alunos.dcc.fc.up.pt added comment
http://bugzilla.novell.com/show_bug.cgi?id=547075#c11
--- Comment #11 from Ricardo Cruz 2009-10-16 16:50:23 MDT ---
Sanford, tell me if you're fine with current SVN. I've kept the current undo
widget, but applied the 11.1 treatment. (Sure, there's some ambiguity with
regard to same or down-grading, but still a big improvement over the old widget
from the feedback.)
I do think after 11.2 we should re-experiment with demoting that widget to its
tab and confirmation dialog in order to simplify the UI for new comers. In
fact, the #1 complain has been the overexposure of function, this by users of
the entire spectrum of skill. At the same time, we should work on providing a
clear and permanent way to allow the user to move it to the sidebar. But
because of the lack of time for dialog, as the yast2-gtk Factory package has
been stalled since 11.1 till now, I think it's only reasonable to accommodate
those who were displeased about some of the changes (but let's keep it to a
minimum to avoid breaking stuff).
I have not been able to reach Christian, so I guess I'll have to make the call
about the labeling. I do see the annoyance action oriented labels can be for an
advanced user, since the label may not suit what she is trying to achieve with
the pool (suppose she runs the software manager in order to set some installed
package as locked, action labels would not be intuitive; more on comment 2). On
the other hand, the problem seems overstated in this thread, even compensating
for the selection bias (e.g. Description).
Either way, one problem I have with reverting the labels is that the undo
widget shares them (in a different tense), as well as the icons, making it
clear how actions map to the undo widget. Also, they provide a context to the
check boxes. The check boxes purpose isn't clear with a tab label such as
"Available". Since the inconvenience seems minimal, I am inclined to say keep
them. One possible solution if people feel strongly abut it, and there is no
alternative proposal that copes with the issues I mention, is to suffix the
pool description: e.g. "Install (Available)". Maybe if we do keep the icon and
revert the label that would be enough to serve the purpose of conveying action.
I do feel uncomfortable however to be dependent on an icon, especially since
accessibility is one of the yast2-gtk selling points (was?). Also a icon/label
mixed semantic pair, as it is unusual, could cause the user cognitive
dissonance (unlikely to offset the backward induction from advanced uses).
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
