Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

computer/security: icons for CPU vulnerabilities [v3] #405

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

bp0
Copy link
Collaborator

@bp0 bp0 commented Jul 6, 2019

@lpereira
Copy link
Owner

lpereira commented Jul 6, 2019

The problem in using only colors is that this makes it harder for color-blind people to distinguish those icons. Using the ⚠️ or ✔️ are better choices. Even 👍 might be an issue in some cultures...

@bp0
Copy link
Collaborator Author

bp0 commented Jul 6, 2019

Well, in this case the icons aren't by themselves. The text is right there next to it for the colorblind folks.
Anyway, it's just an idea.

@bp0
Copy link
Collaborator Author

bp0 commented Jul 6, 2019

Oh, I forgot to mention, there is a little demonstration in this PR where I used 128x128 sized icons and they work well. In the HTML view they will automatically get better with zoom or on HiDPI monitors, and since HardInfo is already using icon_cache_get_pixbuf_at_size() we could maybe adjust the size requested for that as well, based on the display.

@bp0
Copy link
Collaborator Author

bp0 commented Jul 7, 2019

@lpereira, hows this? Changed to color+signs, and using SVG now, so it will need #407's SVG support in HTML reports patch.
vuln_lights2
One with Vulnerable:
frog-security

@bp0 bp0 changed the title computer/security: colored light icons for CPU vulnerabilities computer/security: icons for CPU vulnerabilities Jul 11, 2019
@bp0 bp0 force-pushed the vulnicons branch 4 times, most recently from 170bf19 to 8f9824f Compare July 17, 2019 03:30
@bp0 bp0 changed the title computer/security: icons for CPU vulnerabilities computer/security: icons for CPU vulnerabilities [v3] Jul 17, 2019
@bp0
Copy link
Collaborator Author

bp0 commented Aug 3, 2019

Now that the icons have shapes and are not color-only, do you still have an objection?

@lpereira
Copy link
Owner

Icons look better with distinctive shapes, but it would be nicer if they were using the same style as the rest of the icons.

@bp0
Copy link
Collaborator Author

bp0 commented Nov 23, 2019

I've changed the green and red to match colors from existing icons. The green is from memory.png and the red is from dialog-error.png. They look pretty good with the others, in my opinion. I don't know that I have the talent to try and make new graphics that match the style of the old ones, so I'd ask that you just accept this PR and then replace the images with ones that you would prefer. I really think that going with SVG is a good idea as the old PNGs will look very bad on high resolution (FHD+) displays. I also think that there is value in having a generic set of "good", "ok/mixed", and "bad" icons like these.

Here is a screen capture with the tweaked colors:
Screenshot_2019-11-23_00-57-21

@mckaygerhard
Copy link
Contributor

hi guys.. great to see how are growing hardinfo.. .. i have friend blind person, testing in right way you must use orca.. currently i'm very busy but i noted we need a nithly build system.. of statically linked binaries for those test.. .. i dont remenber the GTK API but you @bp0 must take care that GTK2 and GTK3 can complaint/integrate with atspi api correctly (there's no so much rather than use the GTK right funtions.. that have support, like pass text inclusivelly if have a icon assigned)

this it's not the only case @lpereira.. seems there's some code in old inherit that need some work too.. i'll try to compile a package and pass to my friend and report feedback

bp0 added 2 commits December 26, 2019 22:42
Change colors to match previously existing icons.
* Red is from dialog-error.png
* Green is from memory.png

Signed-off-by: Burt P <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants