<?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: On UI Layout</title>
	<atom:link href="http://blog.3plus4.org/2008/05/25/on-ui-layout/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.3plus4.org/2008/05/25/on-ui-layout/</link>
	<description>The neighbourhood of 7</description>
	<lastBuildDate>Wed, 12 May 2010 16:29:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Jo Vermeulen</title>
		<link>http://blog.3plus4.org/2008/05/25/on-ui-layout/comment-page-1/#comment-1284</link>
		<dc:creator>Jo Vermeulen</dc:creator>
		<pubDate>Mon, 23 Jun 2008 13:45:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.3plus4.org/2008/05/25/on-ui-layout/#comment-1284</guid>
		<description>I worked with constraint-based layouts for my Master&#039;s thesis, and ported the Cassowary algorithm to C# for this (&lt;a href=&quot;http://jozilla.net/software/cassowary_net&quot; rel=&quot;nofollow&quot;&gt;Cassowary.net&lt;/a&gt;). I agree that you can realize many layouts with constraints, but I also noticed that flow layouts are a notable exception :-)

The coolest technique so far in automatic layout and beyond in my opinion is &lt;a href=&quot;http://www.cs.washington.edu/ai/supple/&quot; rel=&quot;nofollow&quot;&gt;SUPPLE&lt;/a&gt; by Krzysztof Gajos. It uses an optimization algorithm to generate user interfaces for different users and devices. A list of papers on SUPPLE can be found at &lt;a href=&quot;http://www.cs.washington.edu/homes/kgajos/&quot; rel=&quot;nofollow&quot;&gt;Krzysztof&#039;s page&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I worked with constraint-based layouts for my Master&#8217;s thesis, and ported the Cassowary algorithm to C# for this (<a href="http://jozilla.net/software/cassowary_net" rel="nofollow">Cassowary.net</a>). I agree that you can realize many layouts with constraints, but I also noticed that flow layouts are a notable exception :-)</p>
<p>The coolest technique so far in automatic layout and beyond in my opinion is <a href="http://www.cs.washington.edu/ai/supple/" rel="nofollow">SUPPLE</a> by Krzysztof Gajos. It uses an optimization algorithm to generate user interfaces for different users and devices. A list of papers on SUPPLE can be found at <a href="http://www.cs.washington.edu/homes/kgajos/" rel="nofollow">Krzysztof&#8217;s page</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Judson</title>
		<link>http://blog.3plus4.org/2008/05/25/on-ui-layout/comment-page-1/#comment-1278</link>
		<dc:creator>Ross Judson</dc:creator>
		<pubDate>Tue, 10 Jun 2008 19:31:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.3plus4.org/2008/05/25/on-ui-layout/#comment-1278</guid>
		<description>I&#039;ve had good results using Choco to do layouts of swing components. With it you can do everything that you thought you could with SpringLayout, but discovered you couldn&#039;t after SpringLayout sneaks up behind you and hits you in the head.  

Generalizing Choco into a proper layout manager is somewhat tricky, but something I&#039;m hoping I&#039;ll get to.

There are higher level concepts involved as well. There are geometric roles (parent container, child) and conceptual roles (focus objects, primary and second information, etc). In the best case we provide a small number of orthogonal concepts with well-known intents, and generate the necessary interface in context, much like styling HTML. 

A table view and a force-directed layout of graphical nodes are not really very far apart.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had good results using Choco to do layouts of swing components. With it you can do everything that you thought you could with SpringLayout, but discovered you couldn&#8217;t after SpringLayout sneaks up behind you and hits you in the head.  </p>
<p>Generalizing Choco into a proper layout manager is somewhat tricky, but something I&#8217;m hoping I&#8217;ll get to.</p>
<p>There are higher level concepts involved as well. There are geometric roles (parent container, child) and conceptual roles (focus objects, primary and second information, etc). In the best case we provide a small number of orthogonal concepts with well-known intents, and generate the necessary interface in context, much like styling HTML. </p>
<p>A table view and a force-directed layout of graphical nodes are not really very far apart.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: []</title>
		<link>http://blog.3plus4.org/2008/05/25/on-ui-layout/comment-page-1/#comment-1273</link>
		<dc:creator>[]</dc:creator>
		<pubDate>Mon, 26 May 2008 14:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.3plus4.org/2008/05/25/on-ui-layout/#comment-1273</guid>
		<description>What&#039;s the Brazil Design?</description>
		<content:encoded><![CDATA[<p>What&#8217;s the Brazil Design?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
