<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Latest Digital Trends &#187; CSS</title>
	<atom:link href="http://www.micelistudios.com/blog/tag/css/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.micelistudios.com/blog</link>
	<description>From New York - Interactive Design Tips and Latest Digital News.</description>
	<lastBuildDate>Wed, 04 Jan 2012 16:28:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>CSS Sprites for the web designer</title>
		<link>http://www.micelistudios.com/blog/2010/05/10/css-sprites-for-the-web-designer/</link>
		<comments>http://www.micelistudios.com/blog/2010/05/10/css-sprites-for-the-web-designer/#comments</comments>
		<pubDate>Mon, 10 May 2010 22:04:12 +0000</pubDate>
		<dc:creator>web design New York City</dc:creator>
				<category><![CDATA[web design]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[sprites]]></category>
		<category><![CDATA[website design]]></category>

		<guid isPermaLink="false">http://www.micelistudios.com/blog/?p=748</guid>
		<description><![CDATA[What is a sprite? A sprite is actually one big image. Have you ever seen the CSS technique where the “on” and “off” states of a button are contained within the same image and are activated by shifting the background-position? I like this because it means no use of image preloading for image rollovers or [...]]]></description>
			<content:encoded><![CDATA[<p><strong>What is a sprite?</strong><br />
A sprite is actually one big image. Have you ever seen  the CSS technique where the “on” and “off” states of a button are  contained within the same image and are activated by shifting the  background-position? I like this because it means no use of image preloading for image rollovers or hover states. Also because it make your website design lighter!</p>
<p>This isn&#8217;t anything new <a href="http://www.alistapart.com/articles/sprites" target="_blank">A List Apart</a> wrote about this back in 2004, but with page-speed being a concern these days, regarding a faster page load could mean better rankings in Google, and it&#8217;s an easy way to optimize a website design.</p>
<p><strong>Below is an example of an on and off state for a button</strong> in a single image.<br />
<img class="alignnone" src="http://www.micelistudios.com/images/buttonupstate2.gif" alt="" width="285" height="52" /><br />
What this image shows is the normal state and the hover state of a button. What we want to do is just add a line of code to your CSS like this: <em> background-position:0px -26px; </em>on the hover state and it will shift the position of the image.<em><br />
</em></p>
<p><em>A sprite would be just like this, but contain all or most of your button on and off states, little icons, header graphic, images for your navigation buttons, graphic headers and basically anything that can be ganged up into one image.<br />
</em></p>
<p><strong>Why is this better than a whole bunch of small images ?<br />
</strong>Wouldn&#8217;t it be faster to load a whole bunch of small images ? Isn&#8217;t everyone slicing up images trying to get them to load faster ? Nope! Those are<strong> </strong>old school techniques that never really got us anywhere (so excuse us for mentioning something that you already know, but it&#8217;s just a healthy reminder! and since Google and page speed have been mentioned a lot in the web design and web development news lately &#8212; and having better rankings involves faster page load speed) So loading a bunch of small images really just fool the eye to make it look like the page  was loading faster by loading bits and pieces all over at once. Each one  of those images is a separate HTTP-Request, and the more of those, the  less efficient your page is. So in short&#8230; <strong>reducing the number of HTTP requests has the biggest impact on  reducing response time and is often the easiest performance improvement  to make</strong>.</p>
<p>If you want to check a site and see how you can create a sprite from the existing website design &#8212; a good choice is <a href="http://spriteme.org/" target="_blank">SpriteMe</a> &#8212; it will open up an overlay  over the right side of your browser and help you make a sprite.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.micelistudios.com/blog/2010/05/10/css-sprites-for-the-web-designer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

