GNOME Bugzilla – Bug 616931
replace legacy stock_* icons with new artwork
Last modified: 2021-05-19 12:28:53 UTC
Evolution relies on some ancient stock icons in its UI. We are introducing some replacements in the base theme (gnome-icon-theme) that we are adding to the icon name spec, but some icon are not generic enough and should be shipped with evolution itself. We will provide the artwork. Here's an initial list from my quick observation (with proposed name): * stock_task-recurring -> task-recurring (status) * stock_new-24h-appointment -> appointment-all-day (status) * stock_text-monospaced -> format-text-monospaced (actions) * stock_alarm -> alert-sound * stock_bell -> alert-sound * stock_contact-list -> user-group/contact-list * stock_new-meeting -> meeting-new What we will cover in the base theme: * stock_person -> avatar-default * stock_inbox -> user-inbox * stock_outbox -> user-outbox * gtk-dialog-error (misused for show-as-busy) -> user-busy Stuff I didn't find filenames for: * new assigned task * new memo * new shared memo * new task * new task list * new memo list
*** Bug 554310 has been marked as a duplicate of this bug. ***
Confirming, it's a good time to do this in master, till it's enough time to any freezes, but I do not agree with this: > * stock_alarm -> alert-sound > * stock_bell -> alert-sound Those are quite different icons, each used for something else. The first is used for an alarm notification daemon, the second in the UI, as a status icon on the event. To answer you question: > * new assigned task stock_task > * new memo stock_insert-note > * new shared memo stock_insert-note > * new task stock_task > * new task list stock_todo > * new memo list stock_notes By the way, there is also a bug report (I'm lazy to find it) about new icons for categories. It would be great to have fresh new icons for them in gnome3/2.34.x+.
Milan, Jakub refers to naming spec compliant names for the aformentioned stuff, so stock_* is a no-go. I'm not an evolution user for a long time, can you guys contextualize the icons a bit? I mean where these icons are used and why. From Milan comment I guess the "new assigned task" and "new task" actually use the same icon, same for "new memo" and "new shared memo" is there a need for different icons then? I think something like this could work: *new assigned task -> actions/task-new (or assigned-task-new if it makes sense) Something like task-due with a check mark istead of the question mark *new memo -> actions/note-new (this is used by other stuff so it may be added to the base theme and probably to the naming specs base set). We could draw a single post-it *new shared memo -> actions/note-new (or actions/note-shared-new or note-public-new or something along the lines) *new task -> actions/task-new Those two are tricky, we could use places like we did for bookmarks *new task list -> places/user-tasks *new memo list -> places/user-notes
There was a proposal sometime back to reduce the number of items in our New menu. For example to just list New Task and New Memo and to be able to switch between Task/Assigned Task and Memo/Shared Memo on the fly once the editor window is open. I'd still like to pursue that, but in the interim I think using the same icon for the various tasks and another icon for the various memos is fine.
(In reply to comment #2) > By the way, there is also a bug report (I'm lazy to find it) about new icons > for categories. Bug 260823
(In reply to comment #4) > There was a proposal sometime back to reduce the number of items in our New > menu. bug 501354?
*** Bug 757818 has been marked as a duplicate of this bug. ***
I committed Simon's work (bug #757818) into the sources: Created commit 9f8bc36 in evo master (3.19.2+) Looking into the result in the UI, the 24hour icon looks odd in the File->New->... message, and the new Memo and Shared Memo looks too oldish in there now. I do not know what with the 24h icon. The new Memo/Shared Memo might be good to add a pen on top of the new stock_memos icon, thus it'll look new and shiny. Simon, would you mind to look on these two things, please?
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new bug report ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.