After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757818 - Some icons are old looking and should be refreshed
Some icons are old looking and should be refreshed
Status: RESOLVED DUPLICATE of bug 616931
Product: evolution
Classification: Applications
Component: general
3.18.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2015-11-09 14:29 UTC by simon
Modified: 2015-11-12 14:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description simon 2015-11-09 14:29:18 UTC
Some icons are old looking and should be refreshed.

Mostly of them are action icons.

I worked on it and here is the result : https://docs.google.com/document/d/1zEFC1vcRkTymrFwRanbsqSGfs2C-c40RKT4FYaYicWY/pub

I'll post a zip as soon as we reach an agreement.
Comment 1 Milan Crha 2015-11-09 18:13:31 UTC
Thanks for the bug report and all the work on this. I agree with the way of getting to the agreement first - your page works just fine for me.

We were talking about the difference between stock_todo and stock_task. It seemed to me that they are the same conceptually, but after I looked on their usage then the stock_todo is used for the Task List, like in File->New->Task List, while the stock_task is used for individual items of any Task List, like in File->New->Task.

Most of the icons are fine. I'll comment only on those I'd like to change. We also spoke about few on the IRC, thus I'll just repeat here myself for the completeness of the history.

stock_bell: wouldn't be there any nicer icon?

stock_notes versus stock_insert-note: it's a similar thing as with stock_todo and stock_task; they might not be the same ideally. These also refer Memos. Could you use the variant with a pen for the stock_notes?

stock_mail-flag-for-followup/stock_mail-flag-for-followup-done: the red/green color is not good, this is not a semaphore of the kind bad/good things will happen (or stop/go case). Using the magenta/blue colors, similar/lighter from the old icon colors would be better.

stock_new-24h-appointment: the one at 48x48 looks pretty good, with its shading and gradient and so on. I would keep it, just push it to smaller sizes too (the original 16x16 looks like it uses only 16 colors, instead of the full spectrum).

stock_new-meeting: "shaking hands", it's pretty hard to replace it, to find a good representative of a meeting. I think the original author meant it as it's an event with agreement from all the attendees, or something like that - I only guess here. It's not used only for File->New->Meeting, but also in the mail message list, component editor and couple other places. I would replace it, but I do not know with what, I'm used to the "shaking hands". The proposed icon looks like a "group of people" to me.

stock_people: is it a typo on the page? The icon looks like the current  File->New->Address Book. What about using the proposed stock_new-meeting here, instead of there?

stock_task: could you make the check-mark blue, instead of green. The blue fits there pretty well, from my point of view. Considering the above difference between stock_todo and stock_task, I would use the icon with the check-mark for the task list and without the check-mark for the task itself. There probably should be those check-rectangles as well for the one task, because one task has up to one check (completed) flag. Basically, use the icon for stock_task-assigned, only remove the arrow from it.

stock_task-recurring: the name of this icon is confusing, it refers 'task', but this is for recurrences in general. The arrows in circle are fine, even real recurrences do not repeat in a circle, they just repeat the event again in the future. I mean with that that the two arrows have its meaning. The background of it, like the task, is not important. I would be fine without the background completely, if it'll not look like "Refresh", or "recycle" icons.

stock_text-monospaced: could it be lighter? It looks like a button on its own, while it'll be placed inside a button. A paper with a monospaced letters would be fine.

stock_timezone: The first impression of the icon is it's a map with a mark of some location, like when you search for some place in Google maps or similar software and it highlights the place for you with this mark. It's close to the timezone, but doesn't feel right. You had there a globe earlier. What about using a globe icon with a pin-point there? The globe could even shown there the timezones (vertical lines), but it won't be visible in the 16x16 variant. I cannot guarantee I'll like it, it depends how it'll look like.

------------------------------------------------------------------------------

I also noticed inconsistencies between the size versions. For example the stock_notes (Memos) shouldn't be the same as stock_todo (Tasks). Maybe if you change the page to show the same icons, only different sized, on the same row, then it'll be easier to spot the inconsistencies between sizes.

Let's iterate on this (I hope I didn't forget of anything).
Comment 2 simon 2015-11-10 09:13:01 UTC
1) We were talking about the difference between stock_todo and stock_task. It seemed to me that they are the same conceptually, but after I looked on their usage then the stock_todo is used for the Task List, like in File->New->Task List, while the stock_task is used for individual items of any Task List, like in File->New->Task.

I've got an idea, i'll use the new GNOME Todo icon for "app" icon, and i'll use classic todo icon for items.

2) stock_bell: wouldn't be there any nicer icon?

Hey ! That's mean ! I had a hard time trying to do it ;)

I'll try to come up with something new. Perhaps something completely different ... We'll see.

3) stock_notes versus stock_insert-note: it's a similar thing as with stock_todo and stock_task; they might not be the same ideally. These also refer Memos. Could you use the variant with a pen for the stock_notes?

Will do

4) stock_mail-flag-for-followup/stock_mail-flag-for-followup-done: the red/green color is not good, this is not a semaphore of the kind bad/good things will happen (or stop/go case). Using the magenta/blue colors, similar/lighter from the old icon colors would be better.

Will do

5) stock_new-24h-appointment: the one at 48x48 looks pretty good, with its shading and gradient and so on. I would keep it, just push it to smaller sizes too (the original 16x16 looks like it uses only 16 colors, instead of the full spectrum).

Already done (i think, unless you mean that the icon i create are not colorful enough)

6) stock_new-meeting: "shaking hands", it's pretty hard to replace it, to find a good representative of a meeting. I think the original author meant it as it's an event with agreement from all the attendees, or something like that - I only guess here. It's not used only for File->New->Meeting, but also in the mail message list, component editor and couple other places. I would replace it, but I do not know with what, I'm used to the "shaking hands". The proposed icon looks like a "group of people" to me.

Well, i understand your point. The "shaking hands" HAVE to be refreshed, but i agree that we have to think a bit more about it.

7) stock_task-recurring: the name of this icon is confusing, it refers 'task', but this is for recurrences in general. The arrows in circle are fine, even real recurrences do not repeat in a circle, they just repeat the event again in the future. I mean with that that the two arrows have its meaning. The background of it, like the task, is not important. I would be fine without the background completely, if it'll not look like "Refresh", or "recycle" icons.

Ok, i'll just use arrow in circle. That's even better anyway.

8) stock_text-monospaced: could it be lighter? It looks like a button on its own, while it'll be placed inside a button. A paper with a monospaced letters would be fine.

Done

9) stock_timezone: The first impression of the icon is it's a map with a mark of some location, like when you search for some place in Google maps or similar software and it highlights the place for you with this mark. It's close to the timezone, but doesn't feel right. You had there a globe earlier. What about using a globe icon with a pin-point there? The globe could even shown there the timezones (vertical lines), but it won't be visible in the 16x16 variant. I cannot guarantee I'll like it, it depends how it'll look like.

Perhaps the map with a clock instead of a pin ?

10) I also noticed inconsistencies between the size versions. For example the stock_notes (Memos) shouldn't be the same as stock_todo (Tasks). Maybe if you change the page to show the same icons, only different sized, on the same row, then it'll be easier to spot the inconsistencies between sizes.

I'll review the organisation
Comment 3 Milan Crha 2015-11-10 11:57:25 UTC
By the way, this is bug #616931, maybe we should move there and mark this as a duplicate of it.

(In reply to Simon Baconnais from comment #2)
> 5) stock_new-24h-appointment:...
>
> Already done (i think, unless you mean that the icon i create are not
> colorful enough)

I meant with that that the smaller icons might be updated to be similar to the 48x48 original icon, because that looks mostly modern. Those suggested black clocks aren't that fancy (from my point of view).

> 9) stock_timezone: ...
> 
> Perhaps the map with a clock instead of a pin ?

The map should not look like a map from a map (search for a place) application, to not confuse users. The timezone is tight to a particular place on the globe, but I'm afraid the people are used to that icon as a reference for an application where they can find their friends.
Comment 4 simon 2015-11-10 13:23:40 UTC
All done.

Is it better ?
Comment 5 Milan Crha 2015-11-12 14:35:49 UTC
We finished this on the IRC (better live session), where I also decided to mark this as a duplicate of the old bug #616931, thus let's move there with this. Thanks.

*** This bug has been marked as a duplicate of bug 616931 ***