<?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: 5 Ways to Instantly Write Better CSS</title>
	<atom:link href="http://teddy-o-ted.com/blog/2009/02/25/5-ways-write-better-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://teddy-o-ted.com/blog/2009/02/25/5-ways-write-better-css/</link>
	<description>Design of a minimalist, content of a maximalist</description>
	<lastBuildDate>Mon, 06 Feb 2012 12:52:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: teddY</title>
		<link>http://teddy-o-ted.com/blog/2009/02/25/5-ways-write-better-css/#comment-64619</link>
		<dc:creator>teddY</dc:creator>
		<pubDate>Sun, 01 Mar 2009 16:41:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.teddy-o-ted.com/?p=3176#comment-64619</guid>
		<description>@abdusfauzi: Hah, same here! Sometimes I get a pain in my wrist because I&#039;ve been resting it on the wrong thing (e.g. edge of the table instead of some supportive pillow which I am yet to get one). Sheeesh. I&#039;m worried about getting carpel tunnel syndrome! Haha.</description>
		<content:encoded><![CDATA[<p>@abdusfauzi: Hah, same here! Sometimes I get a pain in my wrist because I&#8217;ve been resting it on the wrong thing (e.g. edge of the table instead of some supportive pillow which I am yet to get one). Sheeesh. I&#8217;m worried about getting carpel tunnel syndrome! Haha.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: abdusfauzi</title>
		<link>http://teddy-o-ted.com/blog/2009/02/25/5-ways-write-better-css/#comment-64618</link>
		<dc:creator>abdusfauzi</dc:creator>
		<pubDate>Sun, 01 Mar 2009 14:08:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.teddy-o-ted.com/?p=3176#comment-64618</guid>
		<description>a comprehensive post teddY.
for me, i&#039;m using multi lines for every class or IDs. So far, it looks good, but i figure out that, this is one of the reason im having severe injury on my right hand wrist and arm. hahaha. too much scrolling i think. hehe.

&lt;abbr&gt;&lt;em&gt;Check out abdusfauziâ€™s latest blog post Â» &lt;a href=&quot;http://feedproxy.google.com/~r/abdusfauzi/~3/Zk-8X6j_hd4/&quot; rel=&quot;nofollow&quot;&gt;A Very Quick Post : Dedicated to AisyahKama&lt;/a&gt;&lt;/em&gt;&lt;/abbr&gt;</description>
		<content:encoded><![CDATA[<p>a comprehensive post teddY.<br />
for me, i&#8217;m using multi lines for every class or IDs. So far, it looks good, but i figure out that, this is one of the reason im having severe injury on my right hand wrist and arm. hahaha. too much scrolling i think. hehe.</p>
<p><abbr><em>Check out abdusfauziâ€™s latest blog post Â» <a href="http://feedproxy.google.com/~r/abdusfauzi/~3/Zk-8X6j_hd4/" rel="nofollow">A Very Quick Post : Dedicated to AisyahKama</a></em></abbr></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: teddY</title>
		<link>http://teddy-o-ted.com/blog/2009/02/25/5-ways-write-better-css/#comment-64563</link>
		<dc:creator>teddY</dc:creator>
		<pubDate>Thu, 26 Feb 2009 05:12:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.teddy-o-ted.com/?p=3176#comment-64563</guid>
		<description>@NoktahHitam: Thank you! I believe in breaking down the selectors into their respective placement on the page - such as header, footer, content and etc. I do have a more complicated organization for the content part because I&#039;m taking care of the  typography, image alignment, coding, comments and etc.

Single liner are very neat, and pleasing to the eyes as well. Just like what you&#039;ve said, it eliminates the need to scroll madly in search for a certain selector, and if you&#039;re familiar enough with your style sheet (of course you are) it&#039;s easy to locate them without much scrolling.

In the past I design my layouts based on the abstract concept I had in mind at that particular moment, resulting in rather inconsistent appearance and constant editing of previously decided styles (something like being flicker-minded). It was only until the few recent layouts that I pen what I want on paper, and then do some research on CSS frameworks (like &lt;a href=&quot;http://960.gs/&quot; title=&quot;960 grid system&quot; rel=&quot;nofollow&quot;&gt;960 grid system&lt;/a&gt;, &lt;a href=&quot;http://www.blueprintcss.org/&quot; title=&quot;Blueprint CSS&quot; rel=&quot;nofollow&quot;&gt;Blueprint CSS&lt;/a&gt; and etc).

I am yet to develop a habit of creating a Photoshop mockup of what I want though. I did all the calculation on paper and then directly export the ideas into notepad (handcoding is more fun!) and then do the graphics later :P</description>
		<content:encoded><![CDATA[<p>@NoktahHitam: Thank you! I believe in breaking down the selectors into their respective placement on the page &#8211; such as header, footer, content and etc. I do have a more complicated organization for the content part because I&#8217;m taking care of the  typography, image alignment, coding, comments and etc.</p>
<p>Single liner are very neat, and pleasing to the eyes as well. Just like what you&#8217;ve said, it eliminates the need to scroll madly in search for a certain selector, and if you&#8217;re familiar enough with your style sheet (of course you are) it&#8217;s easy to locate them without much scrolling.</p>
<p>In the past I design my layouts based on the abstract concept I had in mind at that particular moment, resulting in rather inconsistent appearance and constant editing of previously decided styles (something like being flicker-minded). It was only until the few recent layouts that I pen what I want on paper, and then do some research on CSS frameworks (like <a href="http://960.gs/" title="960 grid system" rel="nofollow">960 grid system</a>, <a href="http://www.blueprintcss.org/" title="Blueprint CSS" rel="nofollow">Blueprint CSS</a> and etc).</p>
<p>I am yet to develop a habit of creating a Photoshop mockup of what I want though. I did all the calculation on paper and then directly export the ideas into notepad (handcoding is more fun!) and then do the graphics later :P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: teddY</title>
		<link>http://teddy-o-ted.com/blog/2009/02/25/5-ways-write-better-css/#comment-64562</link>
		<dc:creator>teddY</dc:creator>
		<pubDate>Thu, 26 Feb 2009 05:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.teddy-o-ted.com/?p=3176#comment-64562</guid>
		<description>@Jeff Starr: Thank YOU for sharing the CSS resets back then, Jeff ;) They&#039;re one of the reason why I&#039;ve decided to embrace CSS more - in the past, my efforts to design were trumped by the different default styles each browser applies to the elements.

I don&#039;t really think alphabetizing is important (since usually they won&#039;t extend beyond 10~15 lines for each selector) but it&#039;s the perfectionist inside me that instructs me to do it that way. Heh.

Your style of organization is interesting! So each of your selectors will take on this &#039;sloped&#039; look. Cool!

You&#039;re welcome about the linking! It has changed me experience with designing so much that I am ought to share it.</description>
		<content:encoded><![CDATA[<p>@Jeff Starr: Thank YOU for sharing the CSS resets back then, Jeff ;) They&#8217;re one of the reason why I&#8217;ve decided to embrace CSS more &#8211; in the past, my efforts to design were trumped by the different default styles each browser applies to the elements.</p>
<p>I don&#8217;t really think alphabetizing is important (since usually they won&#8217;t extend beyond 10~15 lines for each selector) but it&#8217;s the perfectionist inside me that instructs me to do it that way. Heh.</p>
<p>Your style of organization is interesting! So each of your selectors will take on this &#8216;sloped&#8217; look. Cool!</p>
<p>You&#8217;re welcome about the linking! It has changed me experience with designing so much that I am ought to share it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NoktahHitam</title>
		<link>http://teddy-o-ted.com/blog/2009/02/25/5-ways-write-better-css/#comment-64560</link>
		<dc:creator>NoktahHitam</dc:creator>
		<pubDate>Thu, 26 Feb 2009 02:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.teddy-o-ted.com/?p=3176#comment-64560</guid>
		<description>Nicely written Teddy.

I don&#039;t think Alphabetize would work wonders. For me the break down is Header, Content and Footer. Key CSS like font style will always be at the top.

Personally, my favorite is a single liner. Some call it the Pro&#039;s way, but I personally think it depends on the coder. I don&#039;t like scrolling a million miles south. Afterall, beauty lays in the eye of the beholder, that includes perfection as well ;)

If Travis warns about touching CSS before Markup, let me warn something else.

*Dont you dare touch those keyboard if you haven&#039;t drawn anything on a paper!*

&lt;abbr&gt;&lt;em&gt;Check out NoktahHitamâ€™s latest blog post Â» &lt;a href=&quot;http://feedproxy.google.com/~r/NoktahHitam/~3/5ih3ufsjayY/utusan-does-it-again-twist-twist-twist.html&quot; rel=&quot;nofollow&quot;&gt;Utusan Does It Again, Twist-Twist-Twist&lt;/a&gt;&lt;/em&gt;&lt;/abbr&gt;</description>
		<content:encoded><![CDATA[<p>Nicely written Teddy.</p>
<p>I don&#8217;t think Alphabetize would work wonders. For me the break down is Header, Content and Footer. Key CSS like font style will always be at the top.</p>
<p>Personally, my favorite is a single liner. Some call it the Pro&#8217;s way, but I personally think it depends on the coder. I don&#8217;t like scrolling a million miles south. Afterall, beauty lays in the eye of the beholder, that includes perfection as well ;)</p>
<p>If Travis warns about touching CSS before Markup, let me warn something else.</p>
<p>*Dont you dare touch those keyboard if you haven&#8217;t drawn anything on a paper!*</p>
<p><abbr><em>Check out NoktahHitamâ€™s latest blog post Â» <a href="http://feedproxy.google.com/~r/NoktahHitam/~3/5ih3ufsjayY/utusan-does-it-again-twist-twist-twist.html" rel="nofollow">Utusan Does It Again, Twist-Twist-Twist</a></em></abbr></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Starr</title>
		<link>http://teddy-o-ted.com/blog/2009/02/25/5-ways-write-better-css/#comment-64555</link>
		<dc:creator>Jeff Starr</dc:creator>
		<pubDate>Wed, 25 Feb 2009 21:44:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.teddy-o-ted.com/?p=3176#comment-64555</guid>
		<description>These are excellent tips, teddY -- thanks for sharing. I like to keep things neat and tidy, but have yet to discover the joys of declarative alphabetizing. Instead, I prefer to organize my declaration blocks according to the number of characters contained on each line, such that the result looks like a nicely formatted chunk of code with consistent right text edges. I have been ridiculed for doing it this way, but I don&#039;t care because I think it looks clean, crisp, and complete. Anyway, just wanted to thank you for sharing these great reminders with us. And thanks also for mentioning my article on CSS Resets -- much appreciated! :)

&lt;abbr&gt;&lt;em&gt;Check out Jeff Starrâ€™s latest blog post Â» &lt;a href=&quot;http://perishablepress.com/press/2009/01/19/time-for-a-new-design/&quot; rel=&quot;nofollow&quot;&gt;Time for a New Design?&lt;/a&gt;&lt;/em&gt;&lt;/abbr&gt;</description>
		<content:encoded><![CDATA[<p>These are excellent tips, teddY &#8212; thanks for sharing. I like to keep things neat and tidy, but have yet to discover the joys of declarative alphabetizing. Instead, I prefer to organize my declaration blocks according to the number of characters contained on each line, such that the result looks like a nicely formatted chunk of code with consistent right text edges. I have been ridiculed for doing it this way, but I don&#8217;t care because I think it looks clean, crisp, and complete. Anyway, just wanted to thank you for sharing these great reminders with us. And thanks also for mentioning my article on CSS Resets &#8212; much appreciated! :)</p>
<p><abbr><em>Check out Jeff Starrâ€™s latest blog post Â» <a href="http://perishablepress.com/press/2009/01/19/time-for-a-new-design/" rel="nofollow">Time for a New Design?</a></em></abbr></p>
]]></content:encoded>
	</item>
</channel>
</rss>

