<?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: Rounded Corners &#8211; 170 (For certain values of normal)</title>
	<atom:link href="http://labnotes.org/2007/12/06/rounded-corners-170/feed/" rel="self" type="application/rss+xml" />
	<link>http://labnotes.org/2007/12/06/rounded-corners-170/</link>
	<description></description>
	<lastBuildDate>Mon, 26 Jul 2010 17:36:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Assaf</title>
		<link>http://labnotes.org/2007/12/06/rounded-corners-170/comment-page-1/#comment-139014</link>
		<dc:creator>Assaf</dc:creator>
		<pubDate>Thu, 06 Dec 2007 22:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/12/06/rounded-corners-170/#comment-139014</guid>
		<description>dkubb, I was most scared of the label &quot;framework&quot;, but I&#039;m playing with Blueprint CSS right now (pretending it&#039;s a template, not a framework, helps).  I&#039;ll have a look at Tripoli.

Semantic is a fine line.  I think .error is better for error messages than .red, but .red does have semantics of its own.  Most often what you need is a .sidebar, but ever so often it matters which side you&#039;re on, and .left-pane makes a difference.  When in doubt I choose to err on the side of being too semantic.

I&#039;m still evaluating Blueprint CSS, I think they have just enough semantics for the common stuff (and I&#039;m adding a lot of my own styles), not so sure if the CSS-based grid is any better than using tables.


Lyle, thanks, corrected.</description>
		<content:encoded><![CDATA[<p>dkubb, I was most scared of the label &#8220;framework&#8221;, but I&#8217;m playing with Blueprint CSS right now (pretending it&#8217;s a template, not a framework, helps).  I&#8217;ll have a look at Tripoli.</p>
<p>Semantic is a fine line.  I think .error is better for error messages than .red, but .red does have semantics of its own.  Most often what you need is a .sidebar, but ever so often it matters which side you&#8217;re on, and .left-pane makes a difference.  When in doubt I choose to err on the side of being too semantic.</p>
<p>I&#8217;m still evaluating Blueprint CSS, I think they have just enough semantics for the common stuff (and I&#8217;m adding a lot of my own styles), not so sure if the CSS-based grid is any better than using tables.</p>
<p>Lyle, thanks, corrected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lyle</title>
		<link>http://labnotes.org/2007/12/06/rounded-corners-170/comment-page-1/#comment-139013</link>
		<dc:creator>Lyle</dc:creator>
		<pubDate>Thu, 06 Dec 2007 22:22:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/12/06/rounded-corners-170/#comment-139013</guid>
		<description>_Rude_ Goldberg?</description>
		<content:encoded><![CDATA[<p>_Rude_ Goldberg?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dkubb</title>
		<link>http://labnotes.org/2007/12/06/rounded-corners-170/comment-page-1/#comment-139012</link>
		<dc:creator>dkubb</dc:creator>
		<pubDate>Thu, 06 Dec 2007 22:19:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.labnotes.org/2007/12/06/rounded-corners-170/#comment-139012</guid>
		<description>While I&#039;m not the biggest fan of CSS Frameworks, I do like the Tripoli CSS package.  Its light-weight and mostly consists of Stylesheets that reset browsers and &quot;levels the playing field&quot; so browsers display content as close as possible by default.  This forces you to add rules explicitly and not rely on default browser styling -- default styles which may or may not be present on other browsers.

The problem I have with many CSS frameworks is they encourage you to use non-semantic classes in the HTML.  In my mind that&#039;s a mistake.  An non-semantic class name is worse than font tags or table based layouts since a developer *thinks* they are following web standards, and doesn&#039;t encourage further learning in the area.  At least with fonts and table based layouts its obvious to the developer (and everyone else) that the he has more learning to do.  If you&#039;re going to do it, learn to do it right.</description>
		<content:encoded><![CDATA[<p>While I&#8217;m not the biggest fan of CSS Frameworks, I do like the Tripoli CSS package.  Its light-weight and mostly consists of Stylesheets that reset browsers and &#8220;levels the playing field&#8221; so browsers display content as close as possible by default.  This forces you to add rules explicitly and not rely on default browser styling &#8212; default styles which may or may not be present on other browsers.</p>
<p>The problem I have with many CSS frameworks is they encourage you to use non-semantic classes in the HTML.  In my mind that&#8217;s a mistake.  An non-semantic class name is worse than font tags or table based layouts since a developer *thinks* they are following web standards, and doesn&#8217;t encourage further learning in the area.  At least with fonts and table based layouts its obvious to the developer (and everyone else) that the he has more learning to do.  If you&#8217;re going to do it, learn to do it right.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
