<?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: I&#8217;ve optimized my CSS writing style</title>
	<atom:link href="http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/</link>
	<description>Articles, Tutorials and Resources for the Webdesigner</description>
	<pubDate>Wed, 07 Jan 2009 10:41:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sumesh</title>
		<link>http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/comment-page-1/#comment-8330</link>
		<dc:creator>Sumesh</dc:creator>
		<pubDate>Sat, 25 Oct 2008 18:20:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/?p=123#comment-8330</guid>
		<description>I began writing CSS in the single-line form, then switched to the old form when I saw the beauty of it, and am back in the new style once I realized the optimization benefits.

Now that I use single-line CSS, I don't find the need of using a compressor - there is very little that can be saved.</description>
		<content:encoded><![CDATA[<p>I began writing CSS in the single-line form, then switched to the old form when I saw the beauty of it, and am back in the new style once I realized the optimization benefits.</p>
<p>Now that I use single-line CSS, I don&#8217;t find the need of using a compressor - there is very little that can be saved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rinaldo Hasibuan</title>
		<link>http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/comment-page-1/#comment-2207</link>
		<dc:creator>Rinaldo Hasibuan</dc:creator>
		<pubDate>Mon, 23 Jun 2008 16:22:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/?p=123#comment-2207</guid>
		<description>I think the old style better, more clear</description>
		<content:encoded><![CDATA[<p>I think the old style better, more clear</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Happy Design</title>
		<link>http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/comment-page-1/#comment-2202</link>
		<dc:creator>Happy Design</dc:creator>
		<pubDate>Mon, 23 Jun 2008 08:04:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/?p=123#comment-2202</guid>
		<description>I think the "old" way is much more comfortable to work with.</description>
		<content:encoded><![CDATA[<p>I think the &#8220;old&#8221; way is much more comfortable to work with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Vervoort</title>
		<link>http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/comment-page-1/#comment-2192</link>
		<dc:creator>Stefan Vervoort</dc:creator>
		<pubDate>Sun, 22 Jun 2008 13:18:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/?p=123#comment-2192</guid>
		<description>@Thiemo - In my opinion and experience it is almost the same in the ability to navigate. Both works good, but in this way you have less scrolling to do:). Thanks for your comment.</description>
		<content:encoded><![CDATA[<p>@Thiemo - In my opinion and experience it is almost the same in the ability to navigate. Both works good, but in this way you have less scrolling to do:). Thanks for your comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thiemo Gillissen</title>
		<link>http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/comment-page-1/#comment-2179</link>
		<dc:creator>Thiemo Gillissen</dc:creator>
		<pubDate>Fri, 20 Jun 2008 18:55:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/?p=123#comment-2179</guid>
		<description>hi there!
I don't agree with you in this case. I rather write my css in multiple lines than just in one. You may be have to scroll more, but it's much easier to navigate and to see all the properties.</description>
		<content:encoded><![CDATA[<p>hi there!<br />
I don&#8217;t agree with you in this case. I rather write my css in multiple lines than just in one. You may be have to scroll more, but it&#8217;s much easier to navigate and to see all the properties.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Vervoort</title>
		<link>http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/comment-page-1/#comment-2168</link>
		<dc:creator>Stefan Vervoort</dc:creator>
		<pubDate>Fri, 20 Jun 2008 11:13:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/?p=123#comment-2168</guid>
		<description>Thanks for the comments guys. Seems like a lot of you use the old method. :)

@Ruud - That problem occurred to me as well, but that can be solved with your tab button. If you 'tab' between each element your class will become a bit bigger, but it will be organized. And you have less scrolling to do. 

@Chris - Like I told Ruud here above, you could add some tabs between the elements. It stays organized and in my opinion it is easier to edit and debug as well. It definitely speeded that process up.

@Kip - That's smart, but you should always keep your backup copy ready if something goes wrong. What CSS optimizer do you use?</description>
		<content:encoded><![CDATA[<p>Thanks for the comments guys. Seems like a lot of you use the old method. <img src='http://www.divitodesign.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>@Ruud - That problem occurred to me as well, but that can be solved with your tab button. If you &#8216;tab&#8217; between each element your class will become a bit bigger, but it will be organized. And you have less scrolling to do. </p>
<p>@Chris - Like I told Ruud here above, you could add some tabs between the elements. It stays organized and in my opinion it is easier to edit and debug as well. It definitely speeded that process up.</p>
<p>@Kip - That&#8217;s smart, but you should always keep your backup copy ready if something goes wrong. What CSS optimizer do you use?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kip</title>
		<link>http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/comment-page-1/#comment-2164</link>
		<dc:creator>Kip</dc:creator>
		<pubDate>Fri, 20 Jun 2008 03:26:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/?p=123#comment-2164</guid>
		<description>I do write my code the old way. But once I get the CSS debugged and looking right in all the enviroments I reformat it to a slightly more tighter formatting system using less lines but for time editing sake if there is a change to be made I keep an original copy of the style sheet.</description>
		<content:encoded><![CDATA[<p>I do write my code the old way. But once I get the CSS debugged and looking right in all the enviroments I reformat it to a slightly more tighter formatting system using less lines but for time editing sake if there is a change to be made I keep an original copy of the style sheet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Vincent</title>
		<link>http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/comment-page-1/#comment-2162</link>
		<dc:creator>Chris Vincent</dc:creator>
		<pubDate>Fri, 20 Jun 2008 00:22:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/?p=123#comment-2162</guid>
		<description>I usually don't stick to this method in development because it's lot more of a pain to edit than having it spread out. If you order your css like html, top items at the top, then work your way down to the bottom it's still easy enough to work with... then you can make it fancy when it goes live.</description>
		<content:encoded><![CDATA[<p>I usually don&#8217;t stick to this method in development because it&#8217;s lot more of a pain to edit than having it spread out. If you order your css like html, top items at the top, then work your way down to the bottom it&#8217;s still easy enough to work with&#8230; then you can make it fancy when it goes live.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruud Welten</title>
		<link>http://www.divitodesign.com/2008/06/ive-optimized-my-css-writing-style/comment-page-1/#comment-2159</link>
		<dc:creator>Ruud Welten</dc:creator>
		<pubDate>Thu, 19 Jun 2008 22:16:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.divitodesign.com/?p=123#comment-2159</guid>
		<description>G'day there!

I actually switched the other way around a while back ... I was using the one-line-method but in most of my sites these classes tend to get very big and that is difficult to debug as well.

I think the best way would be a compromise between the two:

p {padding: 20px; color: #666;} /* Simple line */
div#menu {
position: absolute;
left: 10px;
top: 100px;
width: 490px;
height: 20px;
padding: 5px;
border: 1px solid #aaa;} /* Bigger line */</description>
		<content:encoded><![CDATA[<p>G&#8217;day there!</p>
<p>I actually switched the other way around a while back &#8230; I was using the one-line-method but in most of my sites these classes tend to get very big and that is difficult to debug as well.</p>
<p>I think the best way would be a compromise between the two:</p>
<p>p {padding: 20px; color: #666;} /* Simple line */<br />
div#menu {<br />
position: absolute;<br />
left: 10px;<br />
top: 100px;<br />
width: 490px;<br />
height: 20px;<br />
padding: 5px;<br />
border: 1px solid #aaa;} /* Bigger line */</p>
]]></content:encoded>
	</item>
</channel>
</rss>
