<?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: Xul, Apollo, WPF, WPF/E No more</title>
	<atom:link href="http://www.lazycoder.com/weblog/2007/03/22/xul-apollo-wpf-wpfe-no-more/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lazycoder.com/weblog/2007/03/22/xul-apollo-wpf-wpfe-no-more/</link>
	<description></description>
	<lastBuildDate>Fri, 07 Oct 2011 15:08:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: New and Notable 151 - Sam Gentile</title>
		<link>http://www.lazycoder.com/weblog/2007/03/22/xul-apollo-wpf-wpfe-no-more/comment-page-1/#comment-90293</link>
		<dc:creator>New and Notable 151 - Sam Gentile</dc:creator>
		<pubDate>Tue, 25 Sep 2007 06:44:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.lazycoder.com/weblog/index.php/archives/2007/03/22/xul-apollo-wpf-wpfe-no-more/#comment-90293</guid>
		<description>[...] was ROTFL when I read Lazycoder&#039;s rant, &quot;Save me from having to type more angle brackets. Please. I’m tired of $#@$@ angle [...]</description>
		<content:encoded><![CDATA[<p>[...] was <acronym title='Rolling on the floor, laughing'><span class='caps'>ROTFL</span></acronym> when I read Lazycoder&#39;s rant, &quot;Save me from having to type more angle brackets. Please. I’m tired of $#@$@ angle [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lazycoder &#187; Blog Archive &#187; Why use XAML?</title>
		<link>http://www.lazycoder.com/weblog/2007/03/22/xul-apollo-wpf-wpfe-no-more/comment-page-1/#comment-65348</link>
		<dc:creator>Lazycoder &#187; Blog Archive &#187; Why use XAML?</dc:creator>
		<pubDate>Thu, 10 May 2007 16:03:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.lazycoder.com/weblog/index.php/archives/2007/03/22/xul-apollo-wpf-wpfe-no-more/#comment-65348</guid>
		<description>[...] I&#039;m not a big fan of the declarative UI movement. (XUL, Apollo, XAML, and now JavaFX). The reasons given for declarative programming usually center around making the UI code human readable making a cleaner break between the UI(view) and the controller(code driving the view). But UI&#039;s are complicated things, the code or markup used is complicated also. So what&#039;s the first thing most developers do? They go find a tool that makes sure they never, ever have to deal with the complicated markup and code. So if you&#039;re never going to read the UI code, why bother making it human readable? Apples Interface Builder has known this secret for years. Interface Builder stores user interface resources in &quot;nib&quot; files. Nib files are a statically stored representation of the set of interface objects used by the application and their relationships which can be efficiently brought into memory when needed, reducing development time and making it easier to localize an application for different markets. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;m not a big fan of the declarative UI movement. (XUL, Apollo, XAML, and now JavaFX). The reasons given for declarative programming usually center around making the UI code human readable making a cleaner break between the UI(view) and the controller(code driving the view). But UI&#8217;s are complicated things, the code or markup used is complicated also. So what&#8217;s the first thing most developers do? They go find a tool that makes sure they never, ever have to deal with the complicated markup and code. So if you&#8217;re never going to read the UI code, why bother making it human readable? Apples Interface Builder has known this secret for years. Interface Builder stores user interface resources in &#8220;nib&#8221; files. Nib files are a statically stored representation of the set of interface objects used by the application and their relationships which can be efficiently brought into memory when needed, reducing development time and making it easier to localize an application for different markets. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.lazycoder.com/weblog/2007/03/22/xul-apollo-wpf-wpfe-no-more/comment-page-1/#comment-60515</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Fri, 23 Mar 2007 16:33:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.lazycoder.com/weblog/index.php/archives/2007/03/22/xul-apollo-wpf-wpfe-no-more/#comment-60515</guid>
		<description>Chris,

YES. I wrote a post a while back when I compared Interface Builder + Xcode to Visual Studio.

http://www.lazycoder.com/weblog/index.php/archives/2005/11/08/xcode-and-visual-studio-go-head-to-head/

Up until VS 2005, Visual Studio couldn&#039;t touch IB&#039;s visual designer. It&#039;s much better in Vs 2005. But I still like the &quot;freeze dried UI&quot; approach that IB uses with it&#039;s NIB files.</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>YES. I wrote a post a while back when I compared Interface Builder + Xcode to Visual Studio.</p>
<p><a href="http://www.lazycoder.com/weblog/index.php/archives/2005/11/08/xcode-and-visual-studio-go-head-to-head/" rel="nofollow">http://www.lazycoder.com/weblog/index.php/archives/2005/11/08/xcode-and-visual-studio-go-head-to-head/</a></p>
<p>Up until VS 2005, Visual Studio couldn&#8217;t touch IB&#8217;s visual designer. It&#8217;s much better in Vs 2005. But I still like the &#8220;freeze dried UI&#8221; approach that IB uses with it&#8217;s NIB files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Gentile : New and Notable 151</title>
		<link>http://www.lazycoder.com/weblog/2007/03/22/xul-apollo-wpf-wpfe-no-more/comment-page-1/#comment-60510</link>
		<dc:creator>Sam Gentile : New and Notable 151</dc:creator>
		<pubDate>Fri, 23 Mar 2007 13:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.lazycoder.com/weblog/index.php/archives/2007/03/22/xul-apollo-wpf-wpfe-no-more/#comment-60510</guid>
		<description>[...] Hanselman - A Better Way for Click Once and Firefox. Yes!!MiscI was ROTFL when I read Lazycoder&#039;s rant, &quot;Save me from having to type more angle brackets. Please. I&#8217;m tired of $#@$@ angle [...]</description>
		<content:encoded><![CDATA[<p>[...] Hanselman &#8211; A Better Way for Click Once and Firefox. Yes!!MiscI was <acronym title='Rolling on the floor, laughing'><span class='caps'>ROTFL</span></acronym> when I read Lazycoder&#39;s rant, &quot;Save me from having to type more angle brackets. Please. I&rsquo;m tired of $#@$@ angle [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hanson</title>
		<link>http://www.lazycoder.com/weblog/2007/03/22/xul-apollo-wpf-wpfe-no-more/comment-page-1/#comment-60498</link>
		<dc:creator>Chris Hanson</dc:creator>
		<pubDate>Fri, 23 Mar 2007 10:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.lazycoder.com/weblog/index.php/archives/2007/03/22/xul-apollo-wpf-wpfe-no-more/#comment-60498</guid>
		<description>Check out Cocoa on Mac OS X then?  No angle brackets, you draw your user experience.  It doesn&#039;t even generate code for it, it&#039;s all archives that are wired to your objects at runtime...</description>
		<content:encoded><![CDATA[<p>Check out Cocoa on Mac OS X then?  No angle brackets, you draw your user experience.  It doesn&#8217;t even generate code for it, it&#8217;s all archives that are wired to your objects at runtime&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maarten Daalder</title>
		<link>http://www.lazycoder.com/weblog/2007/03/22/xul-apollo-wpf-wpfe-no-more/comment-page-1/#comment-60451</link>
		<dc:creator>Maarten Daalder</dc:creator>
		<pubDate>Thu, 22 Mar 2007 20:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.lazycoder.com/weblog/index.php/archives/2007/03/22/xul-apollo-wpf-wpfe-no-more/#comment-60451</guid>
		<description>Thank you for voicing this!

I feel the same when it comes with Spring and it&#039;s dependancy injection (Java). All in XML. Though, I&#039;m scared by the ammount of xml that goes around these days. 

All hail Guice (for dependancy injection)!</description>
		<content:encoded><![CDATA[<p>Thank you for voicing this!</p>
<p>I feel the same when it comes with Spring and it&#8217;s dependancy injection (Java). All in <acronym title='eXtensible Markup Language'><span class='caps'>XML</span></acronym>. Though, I&#8217;m scared by the ammount of xml that goes around these days. </p>
<p>All hail Guice (for dependancy injection)!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

