<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Optimal CSS Files</title>
	<atom:link href="http://www.wisdump.com/design/optimal-css-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wisdump.com/design/optimal-css-files/#utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=optimal-css-files</link>
	<description>Dumping wisdom on the masses</description>
	<lastBuildDate>Tue, 09 Mar 2010 18:03:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Niek Kouwenberg</title>
		<link>http://www.wisdump.com/design/optimal-css-files/comment-page-1/#comment-27272</link>
		<dc:creator>Niek Kouwenberg</dc:creator>
		<pubDate>Tue, 21 Aug 2007 22:28:06 +0000</pubDate>
		<guid isPermaLink="false">http://wisdump.com/design/optimal-css-files/#comment-27272</guid>
		<description>I have been styling my CSS files in a similar matter since 2002. But I must say the the above example is not easy to scan. I add just a couple more spaces, divide my stylesheet into sections using a small comment (eg sidebar), and have somewhat of a default attribute order:

#wrapper [TAB] { width: 800px; margin: 0 auto; }
#header [TAB] { height: 100px; position: relative; }

Most of the time I don&#039;t want to find a certain property (go ctrl+f), but I want to change the style of an element, so I&#039;m always scanning the style sheet by its selectors. Beautiful formatted CSS isn&#039;t scanable. My own style sheet has got 63 selectors right under one another (1.5 page), but nicely formatted would result an a whopping 329 lines. Try scanning that.

Note: if you&#039;re editor highlights properties and values, one line is easy scanned for the small number of property it usually has.</description>
		<content:encoded><![CDATA[<p>I have been styling my CSS files in a similar matter since 2002. But I must say the the above example is not easy to scan. I add just a couple more spaces, divide my stylesheet into sections using a small comment (eg sidebar), and have somewhat of a default attribute order:</p>
<p>#wrapper [TAB] { width: 800px; margin: 0 auto; }<br />
#header [TAB] { height: 100px; position: relative; }</p>
<p>Most of the time I don&#8217;t want to find a certain property (go ctrl+f), but I want to change the style of an element, so I&#8217;m always scanning the style sheet by its selectors. Beautiful formatted CSS isn&#8217;t scanable. My own style sheet has got 63 selectors right under one another (1.5 page), but nicely formatted would result an a whopping 329 lines. Try scanning that.</p>
<p>Note: if you&#8217;re editor highlights properties and values, one line is easy scanned for the small number of property it usually has.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J David Macor</title>
		<link>http://www.wisdump.com/design/optimal-css-files/comment-page-1/#comment-26751</link>
		<dc:creator>J David Macor</dc:creator>
		<pubDate>Sun, 19 Aug 2007 23:50:37 +0000</pubDate>
		<guid isPermaLink="false">http://wisdump.com/design/optimal-css-files/#comment-26751</guid>
		<description>That&#039;s true Mason, but if you are scanning for something, ctrl-f sometimes doesn&#039;t help; like in those situations where you don&#039;t know what you&#039;re looking for, but you&#039;ll recognize it when you see it. But it is still a matter of preference.</description>
		<content:encoded><![CDATA[<p>That&#8217;s true Mason, but if you are scanning for something, ctrl-f sometimes doesn&#8217;t help; like in those situations where you don&#8217;t know what you&#8217;re looking for, but you&#8217;ll recognize it when you see it. But it is still a matter of preference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mason</title>
		<link>http://www.wisdump.com/design/optimal-css-files/comment-page-1/#comment-26730</link>
		<dc:creator>Mason</dc:creator>
		<pubDate>Sun, 19 Aug 2007 22:00:43 +0000</pubDate>
		<guid isPermaLink="false">http://wisdump.com/design/optimal-css-files/#comment-26730</guid>
		<description>Why does a 2000-line style-sheet matter when you have your trusty Ctrl-F? At that point, it just becomes more important to be able to read the attributes.</description>
		<content:encoded><![CDATA[<p>Why does a 2000-line style-sheet matter when you have your trusty Ctrl-F? At that point, it just becomes more important to be able to read the attributes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Best Design Week Ever: 7 &#124; J David Macor.com</title>
		<link>http://www.wisdump.com/design/optimal-css-files/comment-page-1/#comment-26292</link>
		<dc:creator>Best Design Week Ever: 7 &#124; J David Macor.com</dc:creator>
		<pubDate>Sat, 18 Aug 2007 14:39:02 +0000</pubDate>
		<guid isPermaLink="false">http://wisdump.com/design/optimal-css-files/#comment-26292</guid>
		<description>[...] Optimal CSS Files [...]</description>
		<content:encoded><![CDATA[<p>[...] Optimal CSS Files [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blake Brannon</title>
		<link>http://www.wisdump.com/design/optimal-css-files/comment-page-1/#comment-26139</link>
		<dc:creator>Blake Brannon</dc:creator>
		<pubDate>Sat, 18 Aug 2007 03:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://wisdump.com/design/optimal-css-files/#comment-26139</guid>
		<description>Thanks for the tip. I should run through my code and give it a good scrub.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip. I should run through my code and give it a good scrub.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Berry</title>
		<link>http://www.wisdump.com/design/optimal-css-files/comment-page-1/#comment-24912</link>
		<dc:creator>Jason Berry</dc:creator>
		<pubDate>Tue, 14 Aug 2007 07:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://wisdump.com/design/optimal-css-files/#comment-24912</guid>
		<description>I started out using the single line method, but switched over to multi line layout for debugging/readability reasons. I found myself accidentally putting in duplicate CSS attributes because it wasn&#039;t easily scannable to see whether I had already specified a particular attribute.</description>
		<content:encoded><![CDATA[<p>I started out using the single line method, but switched over to multi line layout for debugging/readability reasons. I found myself accidentally putting in duplicate CSS attributes because it wasn&#8217;t easily scannable to see whether I had already specified a particular attribute.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J David</title>
		<link>http://www.wisdump.com/design/optimal-css-files/comment-page-1/#comment-24670</link>
		<dc:creator>J David</dc:creator>
		<pubDate>Mon, 13 Aug 2007 17:11:57 +0000</pubDate>
		<guid isPermaLink="false">http://wisdump.com/design/optimal-css-files/#comment-24670</guid>
		<description>I just feel like once you start using the single line method, you get used to it reading it that way, and all you are left with is the advantage of easy scrolling, scanning and not having a 2000 line style sheet.</description>
		<content:encoded><![CDATA[<p>I just feel like once you start using the single line method, you get used to it reading it that way, and all you are left with is the advantage of easy scrolling, scanning and not having a 2000 line style sheet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.wisdump.com/design/optimal-css-files/comment-page-1/#comment-24667</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Mon, 13 Aug 2007 16:47:49 +0000</pubDate>
		<guid isPermaLink="false">http://wisdump.com/design/optimal-css-files/#comment-24667</guid>
		<description>I&#039;ll agree that it&#039;s easier to find a selector when formatted on one line. But, to me, that advantage is outweighed by the loss of being able to see the attributes clearly...

Just another way I guess</description>
		<content:encoded><![CDATA[<p>I&#8217;ll agree that it&#8217;s easier to find a selector when formatted on one line. But, to me, that advantage is outweighed by the loss of being able to see the attributes clearly&#8230;</p>
<p>Just another way I guess</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://www.wisdump.com/design/optimal-css-files/comment-page-1/#comment-24612</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Mon, 13 Aug 2007 09:19:19 +0000</pubDate>
		<guid isPermaLink="false">http://wisdump.com/design/optimal-css-files/#comment-24612</guid>
		<description>both ways are as good as each other imo.  The first is better layed out, and easier to read/edit.  the second just takes up less space.</description>
		<content:encoded><![CDATA[<p>both ways are as good as each other imo.  The first is better layed out, and easier to read/edit.  the second just takes up less space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DHTML Image Cropper</title>
		<link>http://www.wisdump.com/design/optimal-css-files/comment-page-1/#comment-24592</link>
		<dc:creator>DHTML Image Cropper</dc:creator>
		<pubDate>Mon, 13 Aug 2007 08:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://wisdump.com/design/optimal-css-files/#comment-24592</guid>
		<description>This good tip with css optimizing, but for more usability I think its better to use first variant.

Sergey Koksharov</description>
		<content:encoded><![CDATA[<p>This good tip with css optimizing, but for more usability I think its better to use first variant.</p>
<p>Sergey Koksharov</p>
]]></content:encoded>
	</item>
</channel>
</rss>
