<?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: Call to designers: Single-line or multi-line CSS?</title>
	<atom:link href="http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css</link>
	<description>web standards, usability &#38; other girly stuff</description>
	<lastBuildDate>Thu, 04 Mar 2010 06:13:46 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: &#187; Introducing: Compact Multi-line CSS! - sugarenia.com : Web Standards, Accessibility &#38; other Girly Stuff</title>
		<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/comment-page-1#comment-126881</link>
		<dc:creator>&#187; Introducing: Compact Multi-line CSS! - sugarenia.com : Web Standards, Accessibility &#38; other Girly Stuff</dc:creator>
		<pubDate>Fri, 29 May 2009 21:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/?p=506#comment-126881</guid>
		<description>[...] CSS for relatively large projects is the way you structure it. We&#8217;ve already discussed single-line or multi-line in this blog, plus the way you define sections and so-called variables in your CSS are already [...]</description>
		<content:encoded><![CDATA[<p>[...] CSS for relatively large projects is the way you structure it. We&#8217;ve already discussed single-line or multi-line in this blog, plus the way you define sections and so-called variables in your CSS are already [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel</title>
		<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/comment-page-1#comment-98117</link>
		<dc:creator>Joel</dc:creator>
		<pubDate>Fri, 10 Oct 2008 19:59:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/?p=506#comment-98117</guid>
		<description>I just wrote a tool that converts between the two formats:
http://www.newmediacampaigns.com/page/single-line-vs-multi-line-css-a-tool-to-end-the-debate</description>
		<content:encoded><![CDATA[<p>I just wrote a tool that converts between the two formats:<br />
<a href="http://www.newmediacampaigns.com/page/single-line-vs-multi-line-css-a-tool-to-end-the-debate" rel="nofollow">http://www.newmediacampaigns.com/page/single-line-vs-multi-line-css-a-tool-to-end-the-debate</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lexx</title>
		<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/comment-page-1#comment-94933</link>
		<dc:creator>lexx</dc:creator>
		<pubDate>Sun, 21 Sep 2008 23:20:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/?p=506#comment-94933</guid>
		<description>Single-line FTW!!!

Why use multiple lines? You ll have to scroll forever.

With Single-line CSS, I have everything in front of me.(24&quot; Wide monitor) Fast, tidy and Easy!</description>
		<content:encoded><![CDATA[<p>Single-line FTW!!!</p>
<p>Why use multiple lines? You ll have to scroll forever.</p>
<p>With Single-line CSS, I have everything in front of me.(24&#8243; Wide monitor) Fast, tidy and Easy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KCorax</title>
		<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/comment-page-1#comment-94117</link>
		<dc:creator>KCorax</dc:creator>
		<pubDate>Wed, 17 Sep 2008 11:53:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/?p=506#comment-94117</guid>
		<description>@sugar My point is that you can write your CSS however you want without worrying for waste of bytes. Just flip that flag in Apache somewhere.
Aah it could all be solved if we had an xml representation for CSS.</description>
		<content:encoded><![CDATA[<p>@sugar My point is that you can write your CSS however you want without worrying for waste of bytes. Just flip that flag in Apache somewhere.<br />
Aah it could all be solved if we had an xml representation for CSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sugar</title>
		<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/comment-page-1#comment-94112</link>
		<dc:creator>Sugar</dc:creator>
		<pubDate>Wed, 17 Sep 2008 11:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/?p=506#comment-94112</guid>
		<description>@KCorax

And your point is?</description>
		<content:encoded><![CDATA[<p>@KCorax</p>
<p>And your point is?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KCorax</title>
		<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/comment-page-1#comment-94104</link>
		<dc:creator>KCorax</dc:creator>
		<pubDate>Wed, 17 Sep 2008 10:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/?p=506#comment-94104</guid>
		<description>@sugar Sure that&#039;s what I&#039;m talking about. But for most platforms, either by hand or using some server mod, when the user tries to access a .css or .js file that gets compressed on demand. Look here for example this http://ub0.cc/3Y/0c in my blog isn&#039;t really compressed. It&#039;s a huge file with comments and so on. Compression is done on demand when a client requests it and cached for some hours at a time.</description>
		<content:encoded><![CDATA[<p>@sugar Sure that&#8217;s what I&#8217;m talking about. But for most platforms, either by hand or using some server mod, when the user tries to access a .css or .js file that gets compressed on demand. Look here for example this <a href="http://ub0.cc/3Y/0c" rel="nofollow">http://ub0.cc/3Y/0c</a> in my blog isn&#8217;t really compressed. It&#8217;s a huge file with comments and so on. Compression is done on demand when a client requests it and cached for some hours at a time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sugar</title>
		<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/comment-page-1#comment-94090</link>
		<dc:creator>Sugar</dc:creator>
		<pubDate>Wed, 17 Sep 2008 06:49:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/?p=506#comment-94090</guid>
		<description>@KCorax

We&#039;re talking development here, not deploy.

Most often than not, CSS is not monolithic - it usually evolves with the project and needs quite a lot of editing.

And most web designers code their CSS by hand, anyway, not in some obscure CSS-generating app.</description>
		<content:encoded><![CDATA[<p>@KCorax</p>
<p>We&#8217;re talking development here, not deploy.</p>
<p>Most often than not, CSS is not monolithic &#8211; it usually evolves with the project and needs quite a lot of editing.</p>
<p>And most web designers code their CSS by hand, anyway, not in some obscure CSS-generating app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KCorax</title>
		<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/comment-page-1#comment-94066</link>
		<dc:creator>KCorax</dc:creator>
		<pubDate>Wed, 17 Sep 2008 01:53:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/?p=506#comment-94066</guid>
		<description>Why stress yourself ? Most web app platforms and frameworks compress both css and javascript before sending it. Works this way for .net jsp most python stuff and RoR (not certain about the last one)</description>
		<content:encoded><![CDATA[<p>Why stress yourself ? Most web app platforms and frameworks compress both css and javascript before sending it. Works this way for .net jsp most python stuff and RoR (not certain about the last one)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lunatik</title>
		<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/comment-page-1#comment-93988</link>
		<dc:creator>lunatik</dc:creator>
		<pubDate>Tue, 16 Sep 2008 16:06:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/?p=506#comment-93988</guid>
		<description>single line ! :)
it&#039;s just css , not some wierd c++ algos lol.
1) I just hate to use the scroll bar each time i want to modify a property.
2)multi line is a waste of bytes, of time , and contributing to global warming.

but i agree that multi line is propably easier when someone is starting web design.

++</description>
		<content:encoded><![CDATA[<p>single line ! <img src='http://blog.sugarenia.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
it&#8217;s just css , not some wierd c++ algos lol.<br />
1) I just hate to use the scroll bar each time i want to modify a property.<br />
2)multi line is a waste of bytes, of time , and contributing to global warming.</p>
<p>but i agree that multi line is propably easier when someone is starting web design.</p>
<p>++</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Konstantinos Kouratoras</title>
		<link>http://blog.sugarenia.com/archives/web-design/call-to-designers-single-line-or-multi-line-css/comment-page-1#comment-93384</link>
		<dc:creator>Konstantinos Kouratoras</dc:creator>
		<pubDate>Thu, 11 Sep 2008 11:45:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sugarenia.com/?p=506#comment-93384</guid>
		<description>Multiline of course, It&#039;s more readable. And if the code is readable, no comments are needed!</description>
		<content:encoded><![CDATA[<p>Multiline of course, It&#8217;s more readable. And if the code is readable, no comments are needed!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
