Bug 399677

Summary: software management: configurable icon size for package status
Product: [openSUSE] openSUSE 11.0 Reporter: macias - <bluedzins>
Component: YaST2Assignee: Stefan Hundhammer <shundhammer>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Enhancement    
Priority: P5 - None CC: tgoettlicher
Version: RC 1   
Target Milestone: ---   
Hardware: i586   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description macias - 2008-06-12 14:20:59 UTC
Since Yast is KDE app it could use the same sizes as KDE uses for toolbar icons (I know, status!=toolbar), but I think it would be a nice gesture for users, so for example some older people could set "big".

The shape of course should remain the same.

Btw. I don't mean the icons should be just zoomed, they should be as crisp as before, but bigger/smaller.
Comment 1 Ladislav Slezák 2008-06-13 10:24:03 UTC
No, Yast is NOT a KDE application. You can even start it in a console in text mode. There is no connection to the current desktop.
Comment 2 macias - 2008-06-13 10:36:16 UTC
When I start in text mode I sure see the same GUI, right? 

Ladislav, and that is the reason you closed this report?

What about people with disabilities (vision impairment)? You will tell them that icons are dead small, and they should not use OS, because, well, yast is not KDE app? That is your answer?
Comment 3 Ladislav Slezák 2008-06-13 11:12:11 UTC
Yes, in textmode you will see the same dialogs, but displayed only using text characters (no icons, no background images, no nice fonts, no graphics elements, etc...).

Why a small icon could prevent them to use the system? I cannot imagine any case.

The bug was marked as invalid because I don't see any real benefit, I think that the icon size does not prevent visually impaired users from using yast. There is no connection between icons and system usability, Yast can be used even by blind people.
Comment 4 macias - 2008-06-13 15:05:00 UTC
Ladislav, ok, let's discuss that.

Let's assume I wear glasses, and I have difficulties to distinguish icons which are 5x5 pixels.

TESTCASES:
KMail -- I move mouse over the toolbar, I click icon size, I choose big, now I can use toolbar without problem

Yast -- I run yast, I see pixels 5x5 pixels (super tiny in other words), I have to ruin my eyes by extra effort on focusing on those little dots that make the difference


Please, explain how Yast solves accessibility problem, because I cannot see anything like that.
Comment 5 Ladislav Slezák 2008-06-13 15:26:11 UTC
There is no toolbar in yast modules, do you mean yast control center?

Anyway, the icons the control center are not unique, you have to read the texts next to the icons. Because several modules use the same icon you cannot look at the icons only, you have to read the labels to choose the right module. So the icon size is not relevant.

Do you have any real example (screenshot), where you cannot do something with small icons?
Comment 6 macias - 2008-06-13 15:41:24 UTC
Ladislav, I mean software management module (see summary). The only way to know what will happen with package is to look at the icons.

And those icons are absurdly tiny. Looking at differences between install, update and auto variations are real strain for my eyes.

I can attach screenshot but there is no point -- I use 1400x1050, if you have smaller resolution for you icons will be quite ok. Note, it is not hires really, because you can buy today monitor with higher resolutions.

Toolbar in KMail was just an example -- KDE apps are _fully_ configurable. Yast is not, this report is about configuring size of the icons.


Again, how older users can use SM? Or people with glasses (as me)?

Besides, configurable text & icon size should be considered a standard nowadays, and not the issue to discuss.
Comment 7 Ladislav Slezák 2008-06-13 15:56:22 UTC
Ah, I see... Yes, this a valid request then. I forgot that the state is displayed using an icon. In another modules the icons are just decorations without real function...

Configuring the text size is already possible for some time (via qtconfig), so no problem there.
Comment 8 Stefan Hundhammer 2008-06-17 11:03:18 UTC
Duplicate to your own (!) bug report

*** This bug has been marked as a duplicate of bug 398618 ***
Comment 9 macias - 2008-06-17 11:24:03 UTC
Stefan, to simply put -- you are AN IDIOT (*) beyond imagination. You just waste people time.

Grab some English dictionary and note the difference between size (you know: small, huge, big) and shape (circle, rectangle, arc).

All you do is sabotaging UI, I have better things to do that keep fighting with you over UI. I spent several years reporting on KDE issues, some time to opensuse, but such person as you -- you are exceptionally. Unfortunately in very bad way.

(*) not offense, not emotions -- it is pure fact. You can't (don't?) read.
Comment 10 Stefan Hundhammer 2008-06-17 13:40:18 UTC
(In reply to comment #9 from Maciej Pilichowski)
> Stefan, to simply put -- you are AN IDIOT (*) beyond imagination. You just
> waste people time.
...
> (*) not offense, not emotions -- it is pure fact. You can't (don't?) read.

No offense?

DAMMIT, I TAKE OFFENSE when I am offended. It is not something for you to decide when I have the right to be offended.

Comment 11 Stefan Hundhammer 2008-06-17 13:42:55 UTC
(In reply to comment #9 from Maciej Pilichowski)
> All you do is sabotaging UI, I have better things to do that keep fighting 
> with you over UI. 

Don't let the door knob hit you in the back on your way out.


> I spent several years reporting on KDE issues, 

Yes, I heard about that, too. You made just as many friends there as you make here...
Comment 12 Stefan Hundhammer 2008-06-17 13:49:01 UTC
BTW don't you think it's very obvious how you try to push your pet features?

First you don't like the new icon set. Then you want it configurable. That gets rejected. Then you invent yet another reason why you think it should be configurable.


We don't have the resources to jump and implement every user's favourite feature. And even if we did, we'd still have to maintain all the resulting code. I tried to explain that to you only lately. See bug #398618 comment #6.