<?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: I Like the Silverlight 2.0 Control Templating Model (better than WPF&#8217;s)</title>
	<atom:link href="http://blog.nerdplusart.com/archives/i-like-the-silverlight-20-control-templating-model-better-than-wpfs/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.nerdplusart.com/archives/i-like-the-silverlight-20-control-templating-model-better-than-wpfs</link>
	<description>inspiration for xaml nerds</description>
	<lastBuildDate>Fri, 16 Jul 2010 20:02:18 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Liquidboy</title>
		<link>http://blog.nerdplusart.com/archives/i-like-the-silverlight-20-control-templating-model-better-than-wpfs/comment-page-1#comment-584</link>
		<dc:creator>Liquidboy</dc:creator>
		<pubDate>Wed, 30 Jul 2008 01:58:40 +0000</pubDate>
		<guid isPermaLink="false">http://notstatic.com/archives/141#comment-584</guid>
		<description>here!here! Give Silverlight a break, it&#039;s made some seriously great decisions in it&#039;s control/parts model and VSM ... I&#039;ve been using Design / Blend &amp; VS2008 religiously since they came out and I can honestly say that it works great for me.

I&#039;m more a designer these days than a developer. Blend is evolving BUT completely agree with you that it&#039;s not very easy to use when trying to template a datagrid (the hardest of all controls). 

Triggers im not too strong on, if it&#039;s sole purpose is for designers to be able to wire up the UI to the VSM so that they don&#039;t need a developer then I&#039;m definetely against that. As you&#039;ve mentioned above one of the main reasons for triggers are a way to describe in XAML the connections between UI and VS (Visual State), this is a good justification for including triggers in Silverlight BUT what concerns me is that we may get to a state where people will code half there UI-VS connections in Triggers and the other half in code NOW THAT WILL BE A DANGEROUS THING!!

I think we need to really look at why people use triggers in WPF and under what conditions they choose code over triggers. Only when we really understand the benefits of triggers and once we have a good story to sell to developers then we should include it in Silverlight. 

ps. the same thing can be said for people that wire up events in XAML versus those that wire them up in code. Which way is better ?? There is no perfect answer for this situation BUT i do know that there is alot of dirty/lazy coders out there that do both whenever they feel like it. Don&#039;t let the same thing happen with triggers!!!!</description>
		<content:encoded><![CDATA[<p>here!here! Give Silverlight a break, it&#8217;s made some seriously great decisions in it&#8217;s control/parts model and VSM &#8230; I&#8217;ve been using Design / Blend &amp; VS2008 religiously since they came out and I can honestly say that it works great for me.</p>
<p>I&#8217;m more a designer these days than a developer. Blend is evolving BUT completely agree with you that it&#8217;s not very easy to use when trying to template a datagrid (the hardest of all controls). </p>
<p>Triggers im not too strong on, if it&#8217;s sole purpose is for designers to be able to wire up the UI to the VSM so that they don&#8217;t need a developer then I&#8217;m definetely against that. As you&#8217;ve mentioned above one of the main reasons for triggers are a way to describe in XAML the connections between UI and VS (Visual State), this is a good justification for including triggers in Silverlight BUT what concerns me is that we may get to a state where people will code half there UI-VS connections in Triggers and the other half in code NOW THAT WILL BE A DANGEROUS THING!!</p>
<p>I think we need to really look at why people use triggers in WPF and under what conditions they choose code over triggers. Only when we really understand the benefits of triggers and once we have a good story to sell to developers then we should include it in Silverlight. </p>
<p>ps. the same thing can be said for people that wire up events in XAML versus those that wire them up in code. Which way is better ?? There is no perfect answer for this situation BUT i do know that there is alot of dirty/lazy coders out there that do both whenever they feel like it. Don&#8217;t let the same thing happen with triggers!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nerdplusart.com &#124; A Survey of Silverlight 3D</title>
		<link>http://blog.nerdplusart.com/archives/i-like-the-silverlight-20-control-templating-model-better-than-wpfs/comment-page-1#comment-578</link>
		<dc:creator>nerdplusart.com &#124; A Survey of Silverlight 3D</dc:creator>
		<pubDate>Mon, 28 Jul 2008 06:07:31 +0000</pubDate>
		<guid isPermaLink="false">http://notstatic.com/archives/141#comment-578</guid>
		<description>[...] Okay, so you&#8217;d be a little right in thinking that but, come on, it&#8217;s only one and a half versions old.&#160; Let&#8217;s cut Silverlight some slack and hope that we get some official support soon (but not before Triggers). [...]</description>
		<content:encoded><![CDATA[<p>[...] Okay, so you&#8217;d be a little right in thinking that but, come on, it&#8217;s only one and a half versions old.&nbsp; Let&#8217;s cut Silverlight some slack and hope that we get some official support soon (but not before Triggers). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flatlander</title>
		<link>http://blog.nerdplusart.com/archives/i-like-the-silverlight-20-control-templating-model-better-than-wpfs/comment-page-1#comment-529</link>
		<dc:creator>Flatlander</dc:creator>
		<pubDate>Wed, 11 Jun 2008 08:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://notstatic.com/archives/141#comment-529</guid>
		<description>&lt;strong&gt;Why the Silverlight VisualStateManager is wrong...&lt;/strong&gt;

Silverlight has a control templating system similar to that of Windows Presentation Foundation. However, Silverlight and WPF take different approaches to updating the user interface as the user interacts with it. WPF uses triggers: the creator of a tem...</description>
		<content:encoded><![CDATA[<p><strong>Why the Silverlight VisualStateManager is wrong&#8230;</strong></p>
<p>Silverlight has a control templating system similar to that of Windows Presentation Foundation. However, Silverlight and WPF take different approaches to updating the user interface as the user interacts with it. WPF uses triggers: the creator of a tem&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: notstatic.com</title>
		<link>http://blog.nerdplusart.com/archives/i-like-the-silverlight-20-control-templating-model-better-than-wpfs/comment-page-1#comment-530</link>
		<dc:creator>notstatic.com</dc:creator>
		<pubDate>Sat, 03 May 2008 01:39:17 +0000</pubDate>
		<guid isPermaLink="false">http://notstatic.com/archives/141#comment-530</guid>
		<description>[...] took some flack for my (arguably polemic) thoughts on the Silverlight control templating model so I was happy to see the second to last paragraph of this post where John shares some of my views [...]</description>
		<content:encoded><![CDATA[<p>[...] took some flack for my (arguably polemic) thoughts on the Silverlight control templating model so I was happy to see the second to last paragraph of this post where John shares some of my views [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marlon Grech</title>
		<link>http://blog.nerdplusart.com/archives/i-like-the-silverlight-20-control-templating-model-better-than-wpfs/comment-page-1#comment-525</link>
		<dc:creator>Marlon Grech</dc:creator>
		<pubDate>Thu, 27 Mar 2008 19:25:04 +0000</pubDate>
		<guid isPermaLink="false">http://notstatic.com/archives/141#comment-525</guid>
		<description>I love you blog but Sorry, I cannot agree with you on this one. By choosing this model SL will break the Developer + Designer workflow. The designer will be too dependent on the Developer and the Developer will have to swear and change the controls just because the Designer decided to change something... lookless controls were a tried and tested SUCCESS. Why do we want to change that in SL and try to re invent something else!</description>
		<content:encoded><![CDATA[<p>I love you blog but Sorry, I cannot agree with you on this one. By choosing this model SL will break the Developer + Designer workflow. The designer will be too dependent on the Developer and the Developer will have to swear and change the controls just because the Designer decided to change something&#8230; lookless controls were a tried and tested SUCCESS. Why do we want to change that in SL and try to re invent something else!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I don&#8217;t like the Silverlight 2.0 Control Templating Model (a flip side to Robby&#8217;s comparison between WPF and Silverlight model.) :: designerslove.net</title>
		<link>http://blog.nerdplusart.com/archives/i-like-the-silverlight-20-control-templating-model-better-than-wpfs/comment-page-1#comment-526</link>
		<dc:creator>I don&#8217;t like the Silverlight 2.0 Control Templating Model (a flip side to Robby&#8217;s comparison between WPF and Silverlight model.) :: designerslove.net</dc:creator>
		<pubDate>Mon, 24 Mar 2008 23:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://notstatic.com/archives/141#comment-526</guid>
		<description>[...] Just read Robby&#8217;s excellent post about silverlight templating model. [...]</description>
		<content:encoded><![CDATA[<p>[...] Just read Robby&#8217;s excellent post about silverlight templating model. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Control Templates - Silverlight 2.0 vs WPF - theWPFintegrator</title>
		<link>http://blog.nerdplusart.com/archives/i-like-the-silverlight-20-control-templating-model-better-than-wpfs/comment-page-1#comment-528</link>
		<dc:creator>Control Templates - Silverlight 2.0 vs WPF - theWPFintegrator</dc:creator>
		<pubDate>Mon, 24 Mar 2008 23:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://notstatic.com/archives/141#comment-528</guid>
		<description>[...] just read a great post by Robby on why he likes the control template model in Silverlight 2.0 better than the one in WPF. I [...]</description>
		<content:encoded><![CDATA[<p>[...] just read a great post by Robby on why he likes the control template model in Silverlight 2.0 better than the one in WPF. I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremiah Morrill</title>
		<link>http://blog.nerdplusart.com/archives/i-like-the-silverlight-20-control-templating-model-better-than-wpfs/comment-page-1#comment-527</link>
		<dc:creator>Jeremiah Morrill</dc:creator>
		<pubDate>Mon, 24 Mar 2008 22:03:31 +0000</pubDate>
		<guid isPermaLink="false">http://notstatic.com/archives/141#comment-527</guid>
		<description>Wow the first positive remark I&#039;ve read about SL control templating.  I have not developed an opinion on it just yet, but I think Dr. WPF and yourself have conflicting perspectives on the subject.

So...Both as gentlemen of honor, I suggest you two have a duel.  I believe it worked out well for Alexander Hamilton.  ;)

-Jer</description>
		<content:encoded><![CDATA[<p>Wow the first positive remark I&#8217;ve read about SL control templating.  I have not developed an opinion on it just yet, but I think Dr. WPF and yourself have conflicting perspectives on the subject.</p>
<p>So&#8230;Both as gentlemen of honor, I suggest you two have a duel.  I believe it worked out well for Alexander Hamilton.  <img src='http://blog.nerdplusart.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>-Jer</p>
]]></content:encoded>
	</item>
</channel>
</rss>
