<?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: CSS constants</title>
	<atom:link href="http://robertnyman.com/2005/09/05/css-constants/feed/" rel="self" type="application/rss+xml" />
	<link>http://robertnyman.com/2005/09/05/css-constants/</link>
	<description>Web development and Internet trends</description>
	<lastBuildDate>Sat, 20 Mar 2010 20:09:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robert Nyman</title>
		<link>http://robertnyman.com/2005/09/05/css-constants/#comment-938</link>
		<dc:creator>Robert Nyman</dc:creator>
		<pubDate>Sun, 11 Sep 2005 09:43:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/?p=155#comment-938</guid>
		<description>Henrik,

Welcome here, I hope you&#039;ll like it. You&#039;re in good hands... :-)

First, why I&#039;d call them constants is because they can&#039;t be altered in the &lt;acronym title=&quot;Cascading Style Sheets&quot;&gt;CSS&lt;/acronym&gt; file itself,  &lt;acronym title=&quot;Cascading Style Sheets&quot;&gt;CSS&lt;/acronym&gt; doesn&#039;t allow changing the value. That&#039;s why I&#039;d regard them as constants as opposed to variables.

The thing with dynamic values in the &lt;acronym title=&quot;Cascading Style Sheets&quot;&gt;CSS&lt;/acronym&gt; file is that even if the &lt;acronym title=&quot;Cascading Style Sheets&quot;&gt;CSS&lt;/acronym&gt; would be separated, it would still be dependant on the server-side generation; it would need a server round-trip to get its new values.

When it comes to becoming smaller and saving bandwidth, that would really only apply to huge web sites or in cases where the &lt;acronym title=&quot;Cascading Style Sheets&quot;&gt;CSS&lt;/acronym&gt; isn&#039;t optimally constructed using its cascading and inheritance power.

Basically, I see no gain when it comes to the file size or dynamic updating of the values (in that case, an &lt;a href=&quot;http://www.robertnyman.com/2005/04/08/ajax/&quot; rel=&quot;nofollow&quot;&gt;AJAX&lt;/a&gt; approach would be far better to have a real dynamic updating of &lt;acronym title=&quot;Cascading Style Sheets&quot;&gt;CSS&lt;/acronym&gt; and other values in the page).

The only benefit, if constants were natively built into &lt;acronym title=&quot;Cascading Style Sheets&quot;&gt;CSS&lt;/acronym&gt;, would be an easer overview of values used in it. But if that takes dependancy on server-side processing and of certain server-side languages and other settings needed to be used, that rules it out for me.</description>
		<content:encoded><![CDATA[<p>Henrik,</p>
<p>Welcome here, I hope you&#8217;ll like it. You&#8217;re in good hands&#8230; <img src='http://robertnyman.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>First, why I&#8217;d call them constants is because they can&#8217;t be altered in the <acronym title="Cascading Style Sheets">CSS</acronym> file itself,  <acronym title="Cascading Style Sheets">CSS</acronym> doesn&#8217;t allow changing the value. That&#8217;s why I&#8217;d regard them as constants as opposed to variables.</p>
<p>The thing with dynamic values in the <acronym title="Cascading Style Sheets">CSS</acronym> file is that even if the <acronym title="Cascading Style Sheets">CSS</acronym> would be separated, it would still be dependant on the server-side generation; it would need a server round-trip to get its new values.</p>
<p>When it comes to becoming smaller and saving bandwidth, that would really only apply to huge web sites or in cases where the <acronym title="Cascading Style Sheets">CSS</acronym> isn&#8217;t optimally constructed using its cascading and inheritance power.</p>
<p>Basically, I see no gain when it comes to the file size or dynamic updating of the values (in that case, an <a href="http://www.robertnyman.com/2005/04/08/ajax/" rel="nofollow">AJAX</a> approach would be far better to have a real dynamic updating of <acronym title="Cascading Style Sheets">CSS</acronym> and other values in the page).</p>
<p>The only benefit, if constants were natively built into <acronym title="Cascading Style Sheets">CSS</acronym>, would be an easer overview of values used in it. But if that takes dependancy on server-side processing and of certain server-side languages and other settings needed to be used, that rules it out for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik</title>
		<link>http://robertnyman.com/2005/09/05/css-constants/#comment-933</link>
		<dc:creator>Henrik</dc:creator>
		<pubDate>Fri, 09 Sep 2005 18:25:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/?p=155#comment-933</guid>
		<description>Tjena/Hi there

First post in you blog :). The blog seems alright so far...

I don&#039;t know why you call them constants, but variables in css could be useful if you want dynamic resizing of a page. You could have some sort of basic css template where you have variables written like  or similar (databinding is better coding practise in ASP.Net). Width calculation is something you&#039;d appreciate in css, so you could use variables for that.

The css is still separated from the content, so it doesn&#039;t not really relevant to the client browser if you use dynamic css or not.

I don&#039;t know who it is just like that, but some guy has today&#039;s weather as his blog header - it uses dynamic css - something that makes it smaller, saving  bandwidth and decreasing downloading times. So there are times when you want to use it.

An example would be to change the total width by changing a variable; cascading to the rest of the blocks.</description>
		<content:encoded><![CDATA[<p>Tjena/Hi there</p>
<p>First post in you blog <img src='http://robertnyman.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> . The blog seems alright so far&#8230;</p>
<p>I don&#8217;t know why you call them constants, but variables in css could be useful if you want dynamic resizing of a page. You could have some sort of basic css template where you have variables written like  or similar (databinding is better coding practise in ASP.Net). Width calculation is something you&#8217;d appreciate in css, so you could use variables for that.</p>
<p>The css is still separated from the content, so it doesn&#8217;t not really relevant to the client browser if you use dynamic css or not.</p>
<p>I don&#8217;t know who it is just like that, but some guy has today&#8217;s weather as his blog header &#8211; it uses dynamic css &#8211; something that makes it smaller, saving  bandwidth and decreasing downloading times. So there are times when you want to use it.</p>
<p>An example would be to change the total width by changing a variable; cascading to the rest of the blocks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Nyman</title>
		<link>http://robertnyman.com/2005/09/05/css-constants/#comment-895</link>
		<dc:creator>Robert Nyman</dc:creator>
		<pubDate>Mon, 05 Sep 2005 10:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/?p=155#comment-895</guid>
		<description>Krijn,

Good to hear that you share my stance. :-)</description>
		<content:encoded><![CDATA[<p>Krijn,</p>
<p>Good to hear that you share my stance. <img src='http://robertnyman.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Krijn Hoetmer</title>
		<link>http://robertnyman.com/2005/09/05/css-constants/#comment-894</link>
		<dc:creator>Krijn Hoetmer</dc:creator>
		<pubDate>Mon, 05 Sep 2005 09:50:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.robertnyman.com/?p=155#comment-894</guid>
		<description>I agree. I &lt;a href=&quot;http://ktk.xs4all.nl/stuff/css/server-side-constants/&quot; rel=&quot;nofollow&quot;&gt;played around with it&lt;/a&gt; at first, but because of some (still unfixed) &lt;a href=&quot;http://www.shauninman.com/plete/2005/08/css-ssc-quickie#comment-002246&quot; rel=&quot;nofollow&quot;&gt;issues&lt;/a&gt; I rethought the idea and came to the conclusion there&#039;s hardly any real benefit :) Letting Apache handle the caching shit is so much handier anyway. So back to oldskool CSS for me :]</description>
		<content:encoded><![CDATA[<p>I agree. I <a href="http://ktk.xs4all.nl/stuff/css/server-side-constants/" rel="nofollow">played around with it</a> at first, but because of some (still unfixed) <a href="http://www.shauninman.com/plete/2005/08/css-ssc-quickie#comment-002246" rel="nofollow">issues</a> I rethought the idea and came to the conclusion there&#8217;s hardly any real benefit <img src='http://robertnyman.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Letting Apache handle the caching shit is so much handier anyway. So back to oldskool CSS for me :]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
