Bug 701888 - Email Settings has same icon as Evolution
Email Settings has same icon as Evolution
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
15
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-05-04 04:06 EDT by Elad Alfassa
Modified: 2012-08-07 13:04 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-08-07 13:04:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Elad Alfassa 2011-05-04 04:06:15 EDT
Same icon for both preferences and the client itself is wrong.
The long-term solution would be merging evolution configuration to gnome-control-center or at least to the application itself without separate desktop file. 

Short term solution would be creating a different icon for the preferences.
Why?
Because in gnome-shell, the icons are big and the text is small, and the user will get used to using the icons only without reading the text after few times.
Comment 1 Matthew Barnes 2011-05-04 08:22:14 EDT
Is this just about the window icon in Preferences?

The alternative is to just use the standard themed icon for preferences:
http://developer.gnome.org/gtk/unstable/gtk-Stock-Items.html#GTK-STOCK-PREFERENCES:CAPS

Matters not to me which one is used.
Comment 2 Elad Alfassa 2011-05-04 08:39:41 EDT
Not window icon, dekstop file icon.
gnome-shell displays desktop files that used to live in the system menu of gnome 2.32 with all other desktop files.
So Evolution's preferences desktop file should have a different icon, not the icon of Evolution itself.
Comment 3 Matthew Barnes 2011-05-04 09:22:41 EDT
Oh that thing.  I think I may just yank that from Fedora.  It was written for MeeGo, doesn't really fit in GNOME 3 and looks horrible.
Comment 4 Matthew Barnes 2011-05-04 09:25:42 EDT
You're talking about Email Settings.  At first I thought you meant Edit -> Preferences.
Comment 5 Elad Alfassa 2011-05-04 09:27:58 EDT
(In reply to comment #3)
> Oh that thing.  I think I may just yank that from Fedora.  It was written for
> MeeGo, doesn't really fit in GNOME 3 and looks horrible.
Sounds like a good solution to me.
(In reply to comment #4)
> You're talking about Email Settings.  At first I thought you meant Edit ->
> Preferences.
Sorry about that, I don't use English locale.
Comment 6 Fedora End Of Life 2012-08-07 13:04:04 EDT
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Note You need to log in before you can comment on or make changes to this bug.