Update the icon for GNOME Firmware and more#3502
Update the icon for GNOME Firmware and more#3502SmartFinn merged 6 commits intoPapirusDevelopmentTeam:masterfrom morganist:gnome-firmware
Conversation
|
Is this even the right way to symlink things? I don't quite understand the difference between executable names, desktop file names and flatpak apps names. But in general i see that the majority of icons is named like their executable names, not flathub/flatpak/desktop filenames - these are symlinked. It is quite hard, to be honest... I just want to help clearing this mess up. |
|
@morganist no matter what name you use for an icon, or what you use for symlink. But when you choose between a common name (e.g. disk-usage-analyzer) and an app name (e.g. |
|
i just think it simplefies things — it is easier to search for an icon when the source icon (not a symlink) is not named "comnetorg.developer.longappname" or something |
|
I'll be preferred to keep the old |
Updated GNOME Firmware icon to a new version (closes #2392):
It is based on the Gtkstresstesting icon, but recoloured to represent a green pcb instead of a red one;
Introduced
gst.svg(copied fromcom.leinardi.gst.svg);Made
gst.svgthe main Gtkstresstesting icon because it is the name of its native (non-flatpak) executable;Tweaked
gst.svg(Gtkstresstesting icon): tweaked shadows, added a shadow and an outline on the chip;Symlinked
com.leinardi.gst.svgtogst.svg;Introduced
gnome-firmware.svg(copied fromcom.gnome.Firmware.svg);Made
gnome-firmware.svgthe main GNOME Firmware icon because it is the name of its native (non-flatpak) executable;Symlinked
firmware-manager.svgandapplication-x-firmware.svgtognome-firmware.svginstead ofcom.gnome.Firmware.svg;And of course, symlinked
com.gnome.Firmware.svgtognome-firmware.svg;