<?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: WPF adoption</title>
	<atom:link href="http://www.componentfactory.com/blog/2008/09/wpf-adoption/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.componentfactory.com/blog/2008/09/wpf-adoption/</link>
	<description>Windows Forms Controls for .NET Smart Client Applications</description>
	<lastBuildDate>Tue, 09 Mar 2010 01:04:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Judah</title>
		<link>http://www.componentfactory.com/blog/2008/09/wpf-adoption/comment-page-1/#comment-1981</link>
		<dc:creator>Judah</dc:creator>
		<pubDate>Fri, 03 Oct 2008 04:41:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.componentfactory.com/blog/?p=358#comment-1981</guid>
		<description>I didn&#039;t say WPF databinding is perfect; rather, it&#039;s a hell of a lot better than WinForms binding.</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t say WPF databinding is perfect; rather, it&#8217;s a hell of a lot better than WinForms binding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Georgi</title>
		<link>http://www.componentfactory.com/blog/2008/09/wpf-adoption/comment-page-1/#comment-1970</link>
		<dc:creator>Georgi</dc:creator>
		<pubDate>Wed, 01 Oct 2008 16:05:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.componentfactory.com/blog/?p=358#comment-1970</guid>
		<description>Let me mention one more thing why WPF will be adopted slowly - it has outstripped the hardware an average office and home computer has. It behaves (regarding performance) nice on a system with good 3D-accelerated adapter but will lag as hell on a slower computer where software-emulated rendering is performed.

Let me mention that I do love the way WPF is implemented - it strictly follows W3C DOM 2 specifications (http://www.dmoz.org/Computers/Programming/Internet/W3C_DOM/Specifications/). There is a true Model-View-Controller architecture which makes the GUI layer as detached from the underlying OS as possible.</description>
		<content:encoded><![CDATA[<p>Let me mention one more thing why WPF will be adopted slowly &#8211; it has outstripped the hardware an average office and home computer has. It behaves (regarding performance) nice on a system with good 3D-accelerated adapter but will lag as hell on a slower computer where software-emulated rendering is performed.</p>
<p>Let me mention that I do love the way WPF is implemented &#8211; it strictly follows W3C DOM 2 specifications (<a href="http://www.dmoz.org/Computers/Programming/Internet/W3C_DOM/Specifications/" rel="nofollow">http://www.dmoz.org/Computers/Programming/Internet/W3C_DOM/Specifications/</a>). There is a true Model-View-Controller architecture which makes the GUI layer as detached from the underlying OS as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keigan</title>
		<link>http://www.componentfactory.com/blog/2008/09/wpf-adoption/comment-page-1/#comment-1969</link>
		<dc:creator>Keigan</dc:creator>
		<pubDate>Wed, 01 Oct 2008 15:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.componentfactory.com/blog/?p=358#comment-1969</guid>
		<description>I happen to be equally comfortable in photoshop and illustrator as I am in VS (admittedly without an IDE I would be lost) so I love being able to do pretty much anything I want in WPF.  That really is what it offers… a tangible way to make beautiful UI possible.  It creates that connection.  

I also recognize that I am rare.  Most of the developers I work with either can’t or have no real desire to make things visually compelling. I also don&#039;t think most coders have access to a designer, at least one who gives a damn about what the coder is doing.  That said, it is going to take more than just showing people the art of the possible… it will take time and (I think more importantly) better tools to get any widespread acceptance.</description>
		<content:encoded><![CDATA[<p>I happen to be equally comfortable in photoshop and illustrator as I am in VS (admittedly without an IDE I would be lost) so I love being able to do pretty much anything I want in WPF.  That really is what it offers… a tangible way to make beautiful UI possible.  It creates that connection.  </p>
<p>I also recognize that I am rare.  Most of the developers I work with either can’t or have no real desire to make things visually compelling. I also don&#8217;t think most coders have access to a designer, at least one who gives a damn about what the coder is doing.  That said, it is going to take more than just showing people the art of the possible… it will take time and (I think more importantly) better tools to get any widespread acceptance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Death of Windows Forms - Part 2 &#171; Castalian</title>
		<link>http://www.componentfactory.com/blog/2008/09/wpf-adoption/comment-page-1/#comment-1964</link>
		<dc:creator>The Death of Windows Forms - Part 2 &#171; Castalian</dc:creator>
		<pubDate>Wed, 01 Oct 2008 08:29:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.componentfactory.com/blog/?p=358#comment-1964</guid>
		<description>[...] The proprietor of said company (Philip Wright) has now chosen to construct a disquisition into WPF adoption. I have chosen to go a little further into reasons Philip states as [...]</description>
		<content:encoded><![CDATA[<p>[...] The proprietor of said company (Philip Wright) has now chosen to construct a disquisition into WPF adoption. I have chosen to go a little further into reasons Philip states as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vesuvius</title>
		<link>http://www.componentfactory.com/blog/2008/09/wpf-adoption/comment-page-1/#comment-1962</link>
		<dc:creator>vesuvius</dc:creator>
		<pubDate>Wed, 01 Oct 2008 06:57:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.componentfactory.com/blog/?p=358#comment-1962</guid>
		<description>I&#039;m afraid Judah, it is you that is off the mark. WPF databinding is phenomenal, but it is also not without it&#039;s drawbacks. Try create a menu and toolbar, with all the images and event handlers and you will soon find that you are writing boilerplate XAML where in winforms it takes 2 minutes.

I will write an answer to this post in my blog and link to it later (longish article not self promotion - oh well, I care about this subject).

 I would also recommend you read http://castalian.wordpress.com/2008/01/07/the-death-of-windows-forms-part-1/ and http://castalian.wordpress.com/2008/02/19/windows-forms-still-ahead-of-wpf-in-lob-applications/

I am just about to start writing part 2 to the death of windows forms.</description>
		<content:encoded><![CDATA[<p>I&#8217;m afraid Judah, it is you that is off the mark. WPF databinding is phenomenal, but it is also not without it&#8217;s drawbacks. Try create a menu and toolbar, with all the images and event handlers and you will soon find that you are writing boilerplate XAML where in winforms it takes 2 minutes.</p>
<p>I will write an answer to this post in my blog and link to it later (longish article not self promotion &#8211; oh well, I care about this subject).</p>
<p> I would also recommend you read <a href="http://castalian.wordpress.com/2008/01/07/the-death-of-windows-forms-part-1/" rel="nofollow">http://castalian.wordpress.com/2008/01/07/the-death-of-windows-forms-part-1/</a> and <a href="http://castalian.wordpress.com/2008/02/19/windows-forms-still-ahead-of-wpf-in-lob-applications/" rel="nofollow">http://castalian.wordpress.com/2008/02/19/windows-forms-still-ahead-of-wpf-in-lob-applications/</a></p>
<p>I am just about to start writing part 2 to the death of windows forms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Judah</title>
		<link>http://www.componentfactory.com/blog/2008/09/wpf-adoption/comment-page-1/#comment-1960</link>
		<dc:creator>Judah</dc:creator>
		<pubDate>Tue, 30 Sep 2008 16:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.componentfactory.com/blog/?p=358#comment-1960</guid>
		<description>James is wrong; there is a business need to move to WPF: less code to write. WinForms support for databinding, for example, is so basic it&#039;s almost useless. We have to write tons of boilerplate code like:

checkBoxClickHandler(..)
{
    if(checkBox.Checked) 
   {
        textBox.Text = &quot;checked&quot;;
        label1.Enabled = true;
        ....
   }
}

Ugly, boring stuff that is time consuming to produce and painful to maintain.

WPF databinding takes care of all this. Less code to write, fewer bugs.

Phil&#039;s prediction is realistic: in a couple years, it will overtake WinForms.

Which begs the question, Phil, are you planning on becoming a WPF component vendor in a few years, or stick it out with WinForms?</description>
		<content:encoded><![CDATA[<p>James is wrong; there is a business need to move to WPF: less code to write. WinForms support for databinding, for example, is so basic it&#8217;s almost useless. We have to write tons of boilerplate code like:</p>
<p>checkBoxClickHandler(..)<br />
{<br />
    if(checkBox.Checked)<br />
   {<br />
        textBox.Text = &#8220;checked&#8221;;<br />
        label1.Enabled = true;<br />
        &#8230;.<br />
   }<br />
}</p>
<p>Ugly, boring stuff that is time consuming to produce and painful to maintain.</p>
<p>WPF databinding takes care of all this. Less code to write, fewer bugs.</p>
<p>Phil&#8217;s prediction is realistic: in a couple years, it will overtake WinForms.</p>
<p>Which begs the question, Phil, are you planning on becoming a WPF component vendor in a few years, or stick it out with WinForms?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan Smart</title>
		<link>http://www.componentfactory.com/blog/2008/09/wpf-adoption/comment-page-1/#comment-1958</link>
		<dc:creator>Duncan Smart</dc:creator>
		<pubDate>Tue, 30 Sep 2008 10:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.componentfactory.com/blog/?p=358#comment-1958</guid>
		<description>I think the .NET 3.x install process is a joke. It should take users a few minutes at most to get .NET client stuff installed, but (seemingly) because of Windows Installer, these things take an age (OK, 20 mins) with copious amounts of disk thrashing. If the install experience were more like Silverlight or Adobe AIR even, then we might be getting somewhere.</description>
		<content:encoded><![CDATA[<p>I think the .NET 3.x install process is a joke. It should take users a few minutes at most to get .NET client stuff installed, but (seemingly) because of Windows Installer, these things take an age (OK, 20 mins) with copious amounts of disk thrashing. If the install experience were more like Silverlight or Adobe AIR even, then we might be getting somewhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.componentfactory.com/blog/2008/09/wpf-adoption/comment-page-1/#comment-1956</link>
		<dc:creator>James</dc:creator>
		<pubDate>Tue, 30 Sep 2008 09:55:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.componentfactory.com/blog/?p=358#comment-1956</guid>
		<description>The problem is that their is no business need to move to WPF. If I convert my app to WPF then I gain zero sales and lose money that could have been earned by doing something else.

In this economic climate, fiddling with unproven and unnecessary technology that provides no tangible benefits to customers is never going to happen.</description>
		<content:encoded><![CDATA[<p>The problem is that their is no business need to move to WPF. If I convert my app to WPF then I gain zero sales and lose money that could have been earned by doing something else.</p>
<p>In this economic climate, fiddling with unproven and unnecessary technology that provides no tangible benefits to customers is never going to happen.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
