Personally, I prefer branding icons much over functionality. It would be horrible if all my browsers and code editors would have the same icon. I want to know when I look in my task bar, what apps exactly I have open. Furthermore, it's always been like that ... no app on my phone or somewhere else uses a generic icon ... for good reason, I search for an app by looking at the icon and not at the text (in fact, some icons don't even have text like the icon in the bottom "favourite bar" on iOS).
Imho, a good branding icon gives some hint about the functionality as well, but it doesn't have to. And well the branding icon is designed by the application, not by breeze.
i m all in with this. Keyboard shortcuts an navigation is one of the most basic parts for accessibility and power users. I will do some investigation here and come back with hopefully something useful.
Let's get it in 5.17 beta branch then as well. Tested it on X11 and Wayland and no related compile warnings.
Iterated with Nate's feedback
EDIT: I have already said this here and there but please don't run any automated script to SVG icons, because when opening them back in Inkscape they are corrupted and everytime I edit a Breeze icon I have to do additional work to fix shapes and gradients corrupted by the scripts.
This is something you should bring up in the VDG chatroom and discuss with @ndavis in particular as we currently make heavy use of these scripts for optimization purposes. Hopefully we can come up with a solution together.
I actually hand check for errors when I optimize. If the gradients are out of place, then I put them back into place, optimize again and check again. Usually, the gradients get messed up when they're missing some data that is supposed to be in there and they get optimized with SVG Cleaner. If you ever see Warning: The 'stop' element must have an 'offset' attribute. Fallback to 'offset=0'., you need to check the gradients.
There are a fair amount of icons with gradient handles that are lined up right, but are way off to the side. Those were there before I started working on breeze-icons and I fix them as I go.
- Use dynamic plugins instead of static plugins
- Changed CMakeLists, so plugins will be compiled to shared libs (dymanic plugins)
- Use json metadata
- Improved auto selection algorithm (added "recommended" field in .json, so the algo knows, which plugin should be preferred)
- Added runtime checks, so the plugins can check whether all requirements are fullfilled (for example if kwin is available)
- Fixed some Bugs
Are you consuming this in PBI in that format?
Let's see which branch this ends up in, don't use 5, 14, 0 just yet, it might end up in 5.13.2.
Good catch, but then this is a bug in QMimeDatabase::suffixForFileName.
Are you consuming this in PBI in that format? Or should we rather normalize this to Action::name during input?