<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: CSS3: what it means, and what it doesn&#8217;t</title>
	<link>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/</link>
	<description>thoughts on &#124; comments about &#124; examples of  } web design trends.</description>
	<pubDate>Fri, 25 Jul 2008 10:55:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3031</link>
		<author>Johan</author>
		<pubDate>Sun, 20 Aug 2006 16:30:36 +0000</pubDate>
		<guid>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3031</guid>
					<description>Who knows CSS3, I bet not that much webdesigners.

CSS2.x is used in most cases to build pro websites and the like. Some browsers like Opera and other swifty updated browsers implement some of them CSS3 gems. 

Some reading: 

&lt;a href='http://www.456bereastreet.com/archive/200601/css_3_selectors_explained/' rel="nofollow"&gt;css3 selectors explained&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Who knows CSS3, I bet not that much webdesigners.</p>
<p>CSS2.x is used in most cases to build pro websites and the like. Some browsers like Opera and other swifty updated browsers implement some of them CSS3 gems. </p>
<p>Some reading: </p>
<p><a href='http://www.456bereastreet.com/archive/200601/css_3_selectors_explained/' rel="nofollow">css3 selectors explained</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andrew Faulkner</title>
		<link>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3032</link>
		<author>Andrew Faulkner</author>
		<pubDate>Sun, 20 Aug 2006 16:58:54 +0000</pubDate>
		<guid>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3032</guid>
					<description>I'd guess that CSS3 would simply remove some of the 'donkey work' from web design (you know - making gradients or complicated border imagery) and let us save some precious time which we could use elsewhere in the design.

It won't be the next big thing in my view - I agree with Phil on this one.

What I'd be interested in is how CSS3 handles columns. I've spent many an hour pondering over column structure within a document. If columns are built in then I could rejoice! ;)</description>
		<content:encoded><![CDATA[<p>I&#8217;d guess that CSS3 would simply remove some of the &#8216;donkey work&#8217; from web design (you know - making gradients or complicated border imagery) and let us save some precious time which we could use elsewhere in the design.</p>
<p>It won&#8217;t be the next big thing in my view - I agree with Phil on this one.</p>
<p>What I&#8217;d be interested in is how CSS3 handles columns. I&#8217;ve spent many an hour pondering over column structure within a document. If columns are built in then I could rejoice! ;)</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3033</link>
		<author>Johan</author>
		<pubDate>Sun, 20 Aug 2006 17:04:03 +0000</pubDate>
		<guid>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3033</guid>
					<description>Additional links about CSS3

CSS3 columnar layouts seems interesting:

&lt;a href='http://www.quirksmode.org/css/multicolumn.html' rel="nofollow"&gt;3 columnar layouts&lt;/a&gt;
&lt;a href='http://www.quirksmode.org/css/box.html' rel="nofollow"&gt;box sizing&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Additional links about CSS3</p>
<p>CSS3 columnar layouts seems interesting:</p>
<p><a href='http://www.quirksmode.org/css/multicolumn.html' rel="nofollow">3 columnar layouts</a><br />
<a href='http://www.quirksmode.org/css/box.html' rel="nofollow">box sizing</a></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3034</link>
		<author>Johan</author>
		<pubDate>Sun, 20 Aug 2006 17:26:08 +0000</pubDate>
		<guid>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3034</guid>
					<description>I am repeating myself or cloning?

The CSS3 interesting parts are not web standardized CSS gems that are not working cross-browser. So it depends really for what browsers you are coding for and know what you are doing. 
Dean Edwards has a JS function named &lt;a href="http://dean.edwards.name/my/cssQuery/" rel="nofollow"&gt;cssQuery&lt;/a&gt; which allows to add support for some CSS3 selectors.</description>
		<content:encoded><![CDATA[<p>I am repeating myself or cloning?</p>
<p>The CSS3 interesting parts are not web standardized CSS gems that are not working cross-browser. So it depends really for what browsers you are coding for and know what you are doing.<br />
Dean Edwards has a JS function named <a href="http://dean.edwards.name/my/cssQuery/" rel="nofollow">cssQuery</a> which allows to add support for some CSS3 selectors.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: P.J. Onori</title>
		<link>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3038</link>
		<author>P.J. Onori</author>
		<pubDate>Sun, 20 Aug 2006 21:28:08 +0000</pubDate>
		<guid>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3038</guid>
					<description>One thing we also need to take into account is that new browser penetration is going to determine how much we can actually use CSS3 to its full extent. Sure, we could make a CSS2 version of the site to go along with a CSS3 version, but I have not worked on a site project yet that has the deadline and budget to allow such luxuries. 

I think CSS3 may make our lives easier a couple years from now, but I just don't see it being used on a large scale until then.</description>
		<content:encoded><![CDATA[<p>One thing we also need to take into account is that new browser penetration is going to determine how much we can actually use CSS3 to its full extent. Sure, we could make a CSS2 version of the site to go along with a CSS3 version, but I have not worked on a site project yet that has the deadline and budget to allow such luxuries. </p>
<p>I think CSS3 may make our lives easier a couple years from now, but I just don&#8217;t see it being used on a large scale until then.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Andrew Faulkner</title>
		<link>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3050</link>
		<author>Andrew Faulkner</author>
		<pubDate>Mon, 21 Aug 2006 12:21:14 +0000</pubDate>
		<guid>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3050</guid>
					<description>P.J,

My take on this would be to have a single rendering engine. The browsers would compete over the bells and whistles around the webpage. But that's another article...</description>
		<content:encoded><![CDATA[<p>P.J,</p>
<p>My take on this would be to have a single rendering engine. The browsers would compete over the bells and whistles around the webpage. But that&#8217;s another article&#8230;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: P.J. Onori</title>
		<link>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3072</link>
		<author>P.J. Onori</author>
		<pubDate>Tue, 22 Aug 2006 18:47:37 +0000</pubDate>
		<guid>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3072</guid>
					<description>Yeah, that would definitely be the best solution. Unfortunately, I think we're far away from something like that happening.</description>
		<content:encoded><![CDATA[<p>Yeah, that would definitely be the best solution. Unfortunately, I think we&#8217;re far away from something like that happening.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Emil Stenström</title>
		<link>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3182</link>
		<author>Emil Stenström</author>
		<pubDate>Sun, 27 Aug 2006 16:23:44 +0000</pubDate>
		<guid>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-3182</guid>
					<description>I belive that the most useful changes to CSS is inside the CSS2.1 specification. With things like display: table and min/max-width/height we can do really effective stuff. CSS3 has some nice stuff in the Advanced layout module, could become interesting I think.</description>
		<content:encoded><![CDATA[<p>I belive that the most useful changes to CSS is inside the CSS2.1 specification. With things like display: table and min/max-width/height we can do really effective stuff. CSS3 has some nice stuff in the Advanced layout module, could become interesting I think.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Max Design - standards based web design, development and training &#187; Some links for light reading (24/8/06)</title>
		<link>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-12030</link>
		<author>Max Design - standards based web design, development and training &#187; Some links for light reading (24/8/06)</author>
		<pubDate>Sun, 19 Nov 2006 01:31:53 +0000</pubDate>
		<guid>http://fadtastic.net/2006/08/20/css3-what-it-means-and-what-it-doesnt/#comment-12030</guid>
					<description>[...] CSS3: what it means, and what it doesn&#8217;t [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] CSS3: what it means, and what it doesn&#8217;t [&#8230;]</p>
]]></content:encoded>
				</item>
</channel>
</rss>
