<?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: Nagging Thoughts About CSS Frameworks</title>
	<atom:link href="http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/</link>
	<description>AJAX Development, News, Techniques &#38; More</description>
	<lastBuildDate>Tue, 24 Jan 2012 01:39:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Don Albrecht</title>
		<link>http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/comment-page-1/#comment-42</link>
		<dc:creator>Don Albrecht</dc:creator>
		<pubDate>Thu, 25 Oct 2007 14:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/#comment-42</guid>
		<description>I agree completely,  I&#039;ve done the &quot;replace and route with PHP&quot; before and it works reasonably well when you have excellent control of the entire server side lifecycle of the page.  Unfortunately, that approach can be a bear to maintain.

I guess the saving grace is the relative maturity of many templating systems which can handle the heavy lifting of the layout styling in an easily and even handle delivery of unique layouts for the various mobile platforms. (Ok that&#039;s pushing it for most of them but probably the best solution in the near &amp; mid term).</description>
		<content:encoded><![CDATA[<p>I agree completely,  I&#8217;ve done the &#8220;replace and route with PHP&#8221; before and it works reasonably well when you have excellent control of the entire server side lifecycle of the page.  Unfortunately, that approach can be a bear to maintain.</p>
<p>I guess the saving grace is the relative maturity of many templating systems which can handle the heavy lifting of the layout styling in an easily and even handle delivery of unique layouts for the various mobile platforms. (Ok that&#8217;s pushing it for most of them but probably the best solution in the near &#038; mid term).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Gilmore</title>
		<link>http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/comment-page-1/#comment-41</link>
		<dc:creator>Jay Gilmore</dc:creator>
		<pubDate>Thu, 25 Oct 2007 14:29:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/#comment-41</guid>
		<description>Don, 

I too wish for your &quot;...ability to specify a given div (left column) as having an entirely different span on different grids given two presentation mediums...&quot;

The problem is that like the limited user agent support mobile devices have for the handheld value in the link element, using php or some other method to do UA detection is full of flaws. This goes well beyond CSS frameworks and is the result of the virtual &quot;Wild West&quot; of handheld browsers with support of UA screening like the iPhone or embedded Opera but some others using WAP and the like mean that it can&#039;t be all handled by the sheet. Some amount of control with the delivery needs to be done on the server and there will always be the need for the devices to have UA overrides to ensure that the web is not completely broken on special devices with unique or atypical displays. 

It would be wonderful conditionals could apply in CSS but that would then mean it becomes another scripting language that would then need to be parsed and rendered and I don&#039;t think that will ever happen. 

I have seen people successfully use PHP and ASP to interact with CSS by using replace teqhniques and I think that a smart combination of server routing and server-side scripting might be able to achieve the results you seek but it is a long way from easy and certainly makes one realize that it is not just Content and its Presentation but Delivery as well that becomes a major part of the equation. 

Kinda makes you want to make raw/static HTML sometimes.

All the best,

Jay</description>
		<content:encoded><![CDATA[<p>Don, </p>
<p>I too wish for your &#8220;&#8230;ability to specify a given div (left column) as having an entirely different span on different grids given two presentation mediums&#8230;&#8221;</p>
<p>The problem is that like the limited user agent support mobile devices have for the handheld value in the link element, using php or some other method to do UA detection is full of flaws. This goes well beyond CSS frameworks and is the result of the virtual &#8220;Wild West&#8221; of handheld browsers with support of UA screening like the iPhone or embedded Opera but some others using WAP and the like mean that it can&#8217;t be all handled by the sheet. Some amount of control with the delivery needs to be done on the server and there will always be the need for the devices to have UA overrides to ensure that the web is not completely broken on special devices with unique or atypical displays. </p>
<p>It would be wonderful conditionals could apply in CSS but that would then mean it becomes another scripting language that would then need to be parsed and rendered and I don&#8217;t think that will ever happen. </p>
<p>I have seen people successfully use PHP and ASP to interact with CSS by using replace teqhniques and I think that a smart combination of server routing and server-side scripting might be able to achieve the results you seek but it is a long way from easy and certainly makes one realize that it is not just Content and its Presentation but Delivery as well that becomes a major part of the equation. </p>
<p>Kinda makes you want to make raw/static HTML sometimes.</p>
<p>All the best,</p>
<p>Jay</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Albrecht</title>
		<link>http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/comment-page-1/#comment-40</link>
		<dc:creator>Don Albrecht</dc:creator>
		<pubDate>Thu, 25 Oct 2007 13:55:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/#comment-40</guid>
		<description>Thank you for providing such a well reasoned insight, it helped me better solidfy my own thoughts on the issue.</description>
		<content:encoded><![CDATA[<p>Thank you for providing such a well reasoned insight, it helped me better solidfy my own thoughts on the issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Albrecht</title>
		<link>http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/comment-page-1/#comment-39</link>
		<dc:creator>Don Albrecht</dc:creator>
		<pubDate>Thu, 25 Oct 2007 13:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/#comment-39</guid>
		<description>Furthering your point about the Grid Generator.  I think potentially much more powerful if more difficult strategy might be rethinking your layout / nesting divs in such a way that the page fails into a better layout for mobile devices when presented with lacking screen real estate. (mobile stylesheets still aren&#039;t reliably applied to pages.  This could probably be achieved by a combination of a different grid and custom styleshee

What I&#039;m really hoping for would be some way to achieve an extra layer of abstraction.  Basically the ability to specify a given div (left column) as having an entirely different span on different grids given two presentation mediums (screen / mobile) for example.</description>
		<content:encoded><![CDATA[<p>Furthering your point about the Grid Generator.  I think potentially much more powerful if more difficult strategy might be rethinking your layout / nesting divs in such a way that the page fails into a better layout for mobile devices when presented with lacking screen real estate. (mobile stylesheets still aren&#8217;t reliably applied to pages.  This could probably be achieved by a combination of a different grid and custom styleshee</p>
<p>What I&#8217;m really hoping for would be some way to achieve an extra layer of abstraction.  Basically the ability to specify a given div (left column) as having an entirely different span on different grids given two presentation mediums (screen / mobile) for example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Gilmore</title>
		<link>http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/comment-page-1/#comment-38</link>
		<dc:creator>Jay Gilmore</dc:creator>
		<pubDate>Thu, 25 Oct 2007 13:01:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.ajaxbestiary.com/2007/10/24/nagging-thoughts-about-css-frameworks/#comment-38</guid>
		<description>Don, 

 Many will agree that using a framework such as BlueprintCSS with its span-12 classes is not separation between presentation and content and to use such a framework requires compromise  with that ideal BUT it is not unsemantic as semantics doesn&#039;t dictate the exclusion of other descriptors along with those that describe the content within a containing element. I argue that given the nature of group development and workflows that it adds some meaning albeit only to the designers and developers but meaning. 

On your very valid point about issues of display issues with various platforms such as mobile device or some other output that the presentational classes won&#039;t work or could work against you and in that case one would have to consider that in the initial structure of the document or document template. That being said you could use the Blueprint Grid Generator to create a grid.css file with identical classes but with different widths for them. There are various other approaches that one could take ranging from additional stylesheets, server side manipulation or media type declaration in the stylesheet links. 

It may be the case that you can&#039;t use a [ready made] framework for anything more that as a scaffold for your particular design and may just need to do it the old fashioned way and write a style sheet.</description>
		<content:encoded><![CDATA[<p>Don, </p>
<p> Many will agree that using a framework such as BlueprintCSS with its span-12 classes is not separation between presentation and content and to use such a framework requires compromise  with that ideal BUT it is not unsemantic as semantics doesn&#8217;t dictate the exclusion of other descriptors along with those that describe the content within a containing element. I argue that given the nature of group development and workflows that it adds some meaning albeit only to the designers and developers but meaning. </p>
<p>On your very valid point about issues of display issues with various platforms such as mobile device or some other output that the presentational classes won&#8217;t work or could work against you and in that case one would have to consider that in the initial structure of the document or document template. That being said you could use the Blueprint Grid Generator to create a grid.css file with identical classes but with different widths for them. There are various other approaches that one could take ranging from additional stylesheets, server side manipulation or media type declaration in the stylesheet links. </p>
<p>It may be the case that you can&#8217;t use a [ready made] framework for anything more that as a scaffold for your particular design and may just need to do it the old fashioned way and write a style sheet.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

