Bug 97709 - Bluecurve's home toolbar icon looks ugly
Summary: Bluecurve's home toolbar icon looks ugly
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-artwork
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Garrett LeSage
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-06-19 15:52 UTC by Mark A J Ashdown
Modified: 2007-04-18 16:54 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-08-07 08:03:24 UTC
Embargoed:


Attachments (Terms of Use)

Description Mark A J Ashdown 2003-06-19 15:52:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686) Gecko/20030313 Galeon/1.3.5

Description of problem:
Bluecurve's home icon on Gnome 2 application toolbars

  /usr/share/icons/Bluecurve/24x24/stock/gtk-home.png

is ugly! (I see it most often in nautilus and galeon 1.3.x.) Most of the toolbar
icons are "flat" whereas the most of the application icons are "edge on". The
home icon seems to be a disconcerting mixture of the two - the roof is edge on
whereas the front wall is flat.

I know it's a strange thing to complain about, but it is these little aesthetic
details that make the difference between a good theme and a great one.
Especially so as it is one of the most-seen icons in Gnome 2 applications.

Bluecurve is such a beautiful theme otherwise. Keep up the good work.

Version-Release number of selected component (if applicable):
redhat-artwork-0.73-1

How reproducible:
Always

Steps to Reproduce:
1. Start nautilus.
2. Look at home icon in toolbar.
3. Say "Urghh!"
    

Additional info:

Comment 1 Alexander Larsson 2003-08-06 09:18:14 UTC
Garrett, this is your call.


Comment 2 Garrett LeSage 2003-08-06 15:30:40 UTC
There's a new version in the latest redhat-artwork package. It's also in the
Severn beta.

It looks similar, yet better.

Comment 3 Alexander Larsson 2003-08-07 08:03:24 UTC
Then i'll close this bug.


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