<?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"
	>
<channel>
	<title>Comments on: Let&#8217;s Get Crackin&#8217;!</title>
	<atom:link href="http://www.fightfortheopenweb.com/2008/04/10/lets-get-crackin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fightfortheopenweb.com/2008/04/10/lets-get-crackin/</link>
	<description>If I were the Lorax, I'd speak for the Open Web</description>
	<pubDate>Fri, 21 Nov 2008 19:59:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: tav</title>
		<link>http://www.fightfortheopenweb.com/2008/04/10/lets-get-crackin/#comment-4</link>
		<dc:creator>tav</dc:creator>
		<pubDate>Fri, 11 Apr 2008 22:05:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.fightfortheopenweb.com/?p=9#comment-4</guid>
		<description>Man, we should talk!</description>
		<content:encoded><![CDATA[<p>Man, we should talk!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ</title>
		<link>http://www.fightfortheopenweb.com/2008/04/10/lets-get-crackin/#comment-3</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Thu, 10 Apr 2008 15:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.fightfortheopenweb.com/?p=9#comment-3</guid>
		<description>Thanks.  I'll be developing on these ideas more soon to expand and clarify these ideas.  The point about Erlang will take longer, so I'll save that for later, but I think I can clarify the point about layout managers.

I guess I'm showing my Swing background here, but most desktop systems have some kind of explicit layout management system.  Basically a layout manager is a way of explicitly defining how elements inside a container are automatically laid out. Right now, css allows most of the tools needed for layout management, but provides them in a way that can be awkward and difficult.  CSS3 will make some things better, like the new template layout, but having explicit layout managers could make a lot of simple things simple again.

Here's a really simple example:
&lt;code&gt;
#my-container{
layout-manager:horizontal;
}
&lt;/code&gt;

No floats, no clears, just a simple horizontal layout.  I think that css provides a lot of lower level layout functionality that I would never get rid of, I just think a higher abstraction layer would be very powerful and helpful. Just imagine:

&lt;code&gt;
form{
layout-manager:form;
}
&lt;/code&gt;

for simple pretty forms.</description>
		<content:encoded><![CDATA[<p>Thanks.  I&#8217;ll be developing on these ideas more soon to expand and clarify these ideas.  The point about Erlang will take longer, so I&#8217;ll save that for later, but I think I can clarify the point about layout managers.</p>
<p>I guess I&#8217;m showing my Swing background here, but most desktop systems have some kind of explicit layout management system.  Basically a layout manager is a way of explicitly defining how elements inside a container are automatically laid out. Right now, css allows most of the tools needed for layout management, but provides them in a way that can be awkward and difficult.  CSS3 will make some things better, like the new template layout, but having explicit layout managers could make a lot of simple things simple again.</p>
<p>Here&#8217;s a really simple example:<br />
<code><br />
#my-container{<br />
layout-manager:horizontal;<br />
}<br />
</code></p>
<p>No floats, no clears, just a simple horizontal layout.  I think that css provides a lot of lower level layout functionality that I would never get rid of, I just think a higher abstraction layer would be very powerful and helpful. Just imagine:</p>
<p><code><br />
form{<br />
layout-manager:form;<br />
}<br />
</code></p>
<p>for simple pretty forms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: charlie</title>
		<link>http://www.fightfortheopenweb.com/2008/04/10/lets-get-crackin/#comment-2</link>
		<dc:creator>charlie</dc:creator>
		<pubDate>Thu, 10 Apr 2008 14:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.fightfortheopenweb.com/?p=9#comment-2</guid>
		<description>First of all, good points.  I agree wholeheartedly about the data binding and security layers and though I am not familiar with Erlang I believe I understand.

Concerning your third point, I'm not understand I understand the layout manager idea (admittedly this is likely due to my inexperience).   I absolutely agree with your critique or current css though.  It seems like it puts such a a strain on developers to do the simplest things which could easily be alleviated with variables.  Though at what point does css stop and javascript take the reigns, or do you see this ambiguity as a strength?</description>
		<content:encoded><![CDATA[<p>First of all, good points.  I agree wholeheartedly about the data binding and security layers and though I am not familiar with Erlang I believe I understand.</p>
<p>Concerning your third point, I&#8217;m not understand I understand the layout manager idea (admittedly this is likely due to my inexperience).   I absolutely agree with your critique or current css though.  It seems like it puts such a a strain on developers to do the simplest things which could easily be alleviated with variables.  Though at what point does css stop and javascript take the reigns, or do you see this ambiguity as a strength?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
