Bug 1042040

Summary:	[RFE][horizon]: Change current bitmap icons for font icons
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	aberezin, ajeain, aortega, jpichon, markmc, mrunge, rhos-flags, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/font-icons
Whiteboard:	upstream_milestone_juno-3 upstream_status_implemented upstream_definition_approved
Fixed In Version:	python-django-horizon-2014.2-4.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-09 14:54:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 20:41:54 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/font-icons.

Description:

Bitmap icons provide us only one size, one color, etc. In general they are not flexible.

Having font icon library, we can operate much better with sizes, colors, background-positions, drop shadows, etc.

Step 1: Choose font library (select needed icons)
Step 2: Include the font into the project (together with all css rules)
Step 3: Indicate all bitmap icons and replace them with font icons

Don't forget about proper documentation (list of included icons and related css classes).

More information about our possibilities follows in Whiteboard.

Specification URL (additional information):

None

Comment 3 Matthias Runge 2014-11-21 08:56:47 UTC

This is development related, no change for end user.

It's not testable.

Comment 6 errata-xmlrpc 2015-02-09 14:54:17 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0154.html