<?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: Java Swing Architecture</title>
	<atom:link href="http://www.javaswing.net/java-swing-architecture.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.javaswing.net/java-swing-architecture.html</link>
	<description>Swing, SWT and Java Desktop related Technologies</description>
	<pubDate>Tue, 06 Jan 2009 20:26:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Prom Dresses Emo Fashion Prom Dress</title>
		<link>http://www.javaswing.net/java-swing-architecture.html#comment-83</link>
		<dc:creator>Prom Dresses Emo Fashion Prom Dress</dc:creator>
		<pubDate>Sun, 17 Aug 2008 22:21:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.javaswing.net/?p=3#comment-83</guid>
		<description>&lt;strong&gt;Prom Dresses Emo Fashion Prom Dress...&lt;/strong&gt;

I didn't agree with you first, but last paragraph makes sense for me...</description>
		<content:encoded><![CDATA[<p><strong>Prom Dresses Emo Fashion Prom Dress&#8230;</strong></p>
<p>I didn&#8217;t agree with you first, but last paragraph makes sense for me&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thierry Lefort</title>
		<link>http://www.javaswing.net/java-swing-architecture.html#comment-35</link>
		<dc:creator>Thierry Lefort</dc:creator>
		<pubDate>Sat, 28 Jun 2008 10:02:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.javaswing.net/?p=3#comment-35</guid>
		<description>Here is a reference to "A Swing Architecture Overview" article from Sun :
http://java.sun.com/products/jfc/tsc/articles/architecture/

"One noteworthy point is that as an application developer, you should think of a component's view/controller responsibilities as being handled by the generic component class (such as. JButton, JTree, and so on). The component class then delegates the look-and-feel-specific aspects of those responsibilities to the UI object that is provided by the currently installed look-and-feel."</description>
		<content:encoded><![CDATA[<p>Here is a reference to &#8220;A Swing Architecture Overview&#8221; article from Sun :<br />
<a href="http://java.sun.com/products/jfc/tsc/articles/architecture/" rel="nofollow">http://java.sun.com/products/jfc/tsc/articles/architecture/</a></p>
<p>&#8220;One noteworthy point is that as an application developer, you should think of a component&#8217;s view/controller responsibilities as being handled by the generic component class (such as. JButton, JTree, and so on). The component class then delegates the look-and-feel-specific aspects of those responsibilities to the UI object that is provided by the currently installed look-and-feel.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thierry Lefort</title>
		<link>http://www.javaswing.net/java-swing-architecture.html#comment-27</link>
		<dc:creator>Thierry Lefort</dc:creator>
		<pubDate>Wed, 18 Jun 2008 07:30:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.javaswing.net/?p=3#comment-27</guid>
		<description>This a really basic vision of the swing architecture, SWING respects the MVC pattern.

- The Model part is the models no problem with that.

- The View part is the look and feel, the ComponentUI hierarchy that makes it possible to have multiple look and feel, if the UI and Controller part were mixted as you describe the L&#38;F Swing would mono L&#38;F.

- The Controller part are the Components they are the link between the UI and the Model.

Most people don't write any UI, but it is a really interesting part and should be more used. For exemple a  LinkButton is a JButton with a distinct UI presenting it as a Link, this is only a UI change between the regular button and a Link.</description>
		<content:encoded><![CDATA[<p>This a really basic vision of the swing architecture, SWING respects the MVC pattern.</p>
<p>- The Model part is the models no problem with that.</p>
<p>- The View part is the look and feel, the ComponentUI hierarchy that makes it possible to have multiple look and feel, if the UI and Controller part were mixted as you describe the L&amp;F Swing would mono L&amp;F.</p>
<p>- The Controller part are the Components they are the link between the UI and the Model.</p>
<p>Most people don&#8217;t write any UI, but it is a really interesting part and should be more used. For exemple a  LinkButton is a JButton with a distinct UI presenting it as a Link, this is only a UI change between the regular button and a Link.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
