<?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: Time for some CSS debate</title>
	<atom:link href="http://www.paulrhayes.com/2009-03/time-for-some-css-debate/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.paulrhayes.com/2009-03/time-for-some-css-debate/</link>
	<description>The web musings and experiments of.</description>
	<lastBuildDate>Sat, 04 Feb 2012 10:09:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Teppo Koivula</title>
		<link>http://www.paulrhayes.com/2009-03/time-for-some-css-debate/comment-page-1/#comment-1415</link>
		<dc:creator>Teppo Koivula</dc:creator>
		<pubDate>Sun, 13 Nov 2011 18:00:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.fofronline.com/?p=41#comment-1415</guid>
		<description>Lately JavaScript has started shifting from being a big part of every frontend developers toolbox towards becoming just a tool for so-called serious programmers. I&#039;m not saying it&#039;s not suitable for backend stuff too, but in my opinion it&#039;s greatest strength still lies in it&#039;s ability to run client side and create responsive / active UI&#039;s.

Considering that, there&#039;s hardly any solid need for CSS (which is and has always been essentially a tool for styling content) to take it&#039;s place. Seems to me that we&#039;re trying to reinvent the wheel here.

I&#039;m also a bit worried about how much focus all this CSS transition / transform talk could be taking away from actually cultivating it&#039;s initial purpose. CSS is nowhere near perfection as a styling tool yet, so why don&#039;t we take it a few steps further in that area before expanding to others?

(These are, naturally, just my opinions. And you all know what they say about opinions.)</description>
		<content:encoded><![CDATA[<p>Lately JavaScript has started shifting from being a big part of every frontend developers toolbox towards becoming just a tool for so-called serious programmers. I’m not saying it’s not suitable for backend stuff too, but in my opinion it’s greatest strength still lies in it’s ability to run client side and create responsive / active UI’s.</p>
<p>Considering that, there’s hardly any solid need for CSS (which is and has always been essentially a tool for styling content) to take it’s place. Seems to me that we’re trying to reinvent the wheel here.</p>
<p>I’m also a bit worried about how much focus all this CSS transition / transform talk could be taking away from actually cultivating it’s initial purpose. CSS is nowhere near perfection as a styling tool yet, so why don’t we take it a few steps further in that area before expanding to others?</p>
<p>(These are, naturally, just my opinions. And you all know what they say about opinions.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Owen</title>
		<link>http://www.paulrhayes.com/2009-03/time-for-some-css-debate/comment-page-1/#comment-1084</link>
		<dc:creator>Dan Owen</dc:creator>
		<pubDate>Wed, 13 Apr 2011 20:45:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.fofronline.com/?p=41#comment-1084</guid>
		<description>Your CSS Modal is an excellent example of why it makes a lot of sense to offload as much jQuery as possible into CSS. Let front-end designers handle more of the load and let the JS programmers take on the more serious stuff. Everyone (especially including the customer) will benefit.</description>
		<content:encoded><![CDATA[<p>Your CSS Modal is an excellent example of why it makes a lot of sense to offload as much jQuery as possible into CSS. Let front-end designers handle more of the load and let the JS programmers take on the more serious stuff. Everyone (especially including the customer) will benefit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodney Reid</title>
		<link>http://www.paulrhayes.com/2009-03/time-for-some-css-debate/comment-page-1/#comment-43</link>
		<dc:creator>Rodney Reid</dc:creator>
		<pubDate>Sat, 09 May 2009 07:36:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.fofronline.com/?p=41#comment-43</guid>
		<description>The form ate the greater/less thans, but I hope I got my point across!</description>
		<content:encoded><![CDATA[<p>The form ate the greater/less thans, but I hope I got my point across!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodney Reid</title>
		<link>http://www.paulrhayes.com/2009-03/time-for-some-css-debate/comment-page-1/#comment-42</link>
		<dc:creator>Rodney Reid</dc:creator>
		<pubDate>Sat, 09 May 2009 07:35:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.fofronline.com/?p=41#comment-42</guid>
		<description>I think CSS animations are a natural extension of styling.

How should you express animations in a formal way?

With JavaScript?    It&#039;s been done for well over a decade.   A thousand ways, and no end in sight.

The concept of codeless animation on the web isn&#039;t new.

SMIL2 (HTML+TIME) in IE 5.5+ (summer 1999) was a good start, but the more I used it back when it came out, the more I wanted to just style some element animation without copying a dozen attributes every time.


Which looks more natural?


.clickme {background-color: #000; }
.clickme:hover { transition: background-color 1s linear #00f; }

Click here

or

Click here

 $(&#039;.clickme&#039;).style.backgroundColor.animate(&quot;#000&quot;, &quot;#0F0&quot;, &quot;hover&quot;, 0, 100);


(apologies for the pidgin jQuery and css anim - it would look something like that though)


One more thing - if tied to JS, you cannot guarantee when an animation starts/stops, how it&#039;s supposed to degrade when there&#039;s 1000 animated elements.   Stopping on a JS error somewhere else, etc.

We already have the mess of that!</description>
		<content:encoded><![CDATA[<p>I think CSS animations are a natural extension of styling.</p>
<p>How should you express animations in a formal way?</p>
<p>With JavaScript?    It’s been done for well over a decade.   A thousand ways, and no end in sight.</p>
<p>The concept of codeless animation on the web isn’t new.</p>
<p>SMIL2 (HTML+TIME) in IE 5.5+ (summer 1999) was a good start, but the more I used it back when it came out, the more I wanted to just style some element animation without copying a dozen attributes every time.</p>
<p>Which looks more natural?</p>
<p>.clickme {background-color: #000; }<br />
.clickme:hover { transition: background-color 1s linear #00f; }</p>
<p>Click here</p>
<p>or</p>
<p>Click here</p>
<p> $(‘.clickme’).style.backgroundColor.animate(“#000″, “#0F0”, “hover”, 0, 100);</p>
<p>(apologies for the pidgin jQuery and css anim — it would look something like that though)</p>
<p>One more thing — if tied to JS, you cannot guarantee when an animation starts/stops, how it’s supposed to degrade when there’s 1000 animated elements.   Stopping on a JS error somewhere else, etc.</p>
<p>We already have the mess of that!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: merlinvicki</title>
		<link>http://www.paulrhayes.com/2009-03/time-for-some-css-debate/comment-page-1/#comment-41</link>
		<dc:creator>merlinvicki</dc:creator>
		<pubDate>Fri, 08 May 2009 19:37:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.fofronline.com/?p=41#comment-41</guid>
		<description>nice debate. IMHO CSS is meant to style the page. With some basic effects like :hover CSS is a light/clean help but it should not extend to major handling of elements.</description>
		<content:encoded><![CDATA[<p>nice debate. IMHO CSS is meant to style the page. With some basic effects like :hover CSS is a light/clean help but it should not extend to major handling of elements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver Kohll</title>
		<link>http://www.paulrhayes.com/2009-03/time-for-some-css-debate/comment-page-1/#comment-40</link>
		<dc:creator>Oliver Kohll</dc:creator>
		<pubDate>Mon, 30 Mar 2009 16:53:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.fofronline.com/?p=41#comment-40</guid>
		<description>Sorry, just some spelling: &#039;wreak&#039; should be &#039;reek&#039;.</description>
		<content:encoded><![CDATA[<p>Sorry, just some spelling: ‘wreak’ should be ‘reek’.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

