https://bugzilla.novell.com/show_bug.cgi?id=679198 https://bugzilla.novell.com/show_bug.cgi?id=679198#c1 Ricardo Cruz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rpmcruz@alunos.dcc.fc.up.pt AssignedTo|bnc-team-screening@forge.pr |rpmcruz@alunos.dcc.fc.up.pt |ovo.novell.com | Severity|Normal |Minor --- Comment #1 from Ricardo Cruz 2011-03-13 20:12:27 UTC --- I agree there is space for improvement here. I completely disagree about it being an "usability abuse". The check-box works like everywhere else: on and off, if the package is installed. Inactive if the package is locked. (A tool-tip is even shown when the package is locked to make it clear.) This is the same approach used by PackageKit-gtk, the Mandriva software manager, and others. The design was an open process, and yours would be the first bug report about this part of the design (and this tool was already shipped as is back in 11.3). The look of the check-box depends on your gtk style. --- Where I'd agree there is room for improvement (if this is part of your complain) is that the check-box (like any other check-box) does not indicate change per se. You cannot know whether it was already 'on', or it has been changed. We do indicate whether the package has been changed by showing a yellow-ish background color. But in a software manager, we should probably do more than that: and indicate exactly what has been changed: particularly, if it's a version change. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679198 https://bugzilla.novell.com/show_bug.cgi?id=679198#c3 --- Comment #3 from Maciej Pilichowski 2011-03-14 13:59:42 UTC --- "Inactive if the package is locked". Inactive checkbox means user cannot change it. It is not true. In this case, user disables actions for system, not vice versa. Ricardo, with all due respect, I won't mail it further. It is futile and tiresome. I, user, spotted an issue/problem/bug/feature. I posted it at right site. This required some time. Next, I am redirected to some other site/ML to repeat the problem. Then, there are objections, like -- any healthy marine sharpshooter can tell the difference from 12 feet, so it is your problem. So, again, time spent for nothing. It is much quicker for me, ignore the problem, install Yast/Qt (what I already did, because of the status icons) and live with it. Yast/Qt presents information in manner which are clear and _readable_ (UIs are for people). Productivity -- less time spent. If someone decided such scattered infrastructure (Bugzilla+Features+MLs+...?) helps improving openSUSE, well, I don't have to agree or use it further. I did my part, the issue is reported. If you feel this report is invalid, inaccurate, close it. Thank you. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=679198 https://bugzilla.novell.com/show_bug.cgi?id=679198#c5 Ricardo Cruz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |WONTFIX --- Comment #5 from Ricardo Cruz 2011-07-31 22:17:13 UTC --- This feature will require quite a bit of work, and there doesn't seem to exist enough interest to warrant it. I would hate to get something like this done, only to have people complain and I have to ditch the code. Anyhow, I would love to learn and do more work on UI design, and so I might come back to this in the future, when I have less projects in the sideline. Meanwhile, yast3 should be finally producing fruits, and so it makes more sense to concentrate on that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.