SilverlightShow: Designer-friendly MVVM for XAML Windows Store applications Comments http://www.silverlightshow.net/ Silverlight articles, Silverlight tutorials, Silverlight videos, Silverlight samples SilverlightShow.net http://www.rssboard.org/rss-specification Argotic Syndication Framework 2008.0.2.0, http://www.codeplex.com/Argotic en-US estoychev@completit.com (Emil Stoychev) Re: Designer-friendly MVVM for XAML Windows Store applications <p>Interesting approach - because you've focused on making it as easy as possible for a designer to use it has ended up as quite a clean design, although perhaps not as flexible as other libraries. </p> <p>I quite like that you traverse the visual tree to find the method rather than force the designer to bind up the correct part of the VM for the action - simplicity at the expense of a marginal perf hit.</p> http://www.silverlightshow.net/items/Designer-friendly-MVVM-for-XAML-Windows-Store-applications.aspx#comment8973 MikeGoatly http://www.silverlightshow.net/items/Designer-friendly-MVVM-for-XAML-Windows-Store-applications.aspx Thu, 21 Feb 2013 10:40:15 GMT Re: Designer-friendly MVVM for XAML Windows Store applications <p>Looks good.</p> <p><strong>CallVMMethod</strong> is a bit like EventToCommand only without the need for using commands and with support for passing UI event args to a view model (which might not be the best idea if you want to reuse the view model on another platform). It feels like just handling events and calling view model methods from code behind might have better tool support and while it is a little bit more code in code behind - it is a bit more flexible without adding dependency on this helper library. It seems like making it depend on reflection might make the code less maintainable by removing the compile-time checks.</p> <p><strong>EnumToVisualState</strong> is nice since if you use visual states extensively - the visual state often depends on the view model state property. Since names of visual states are just strings - you can't really ensure compile-time checks there and it is nice to have a simple way to bind a visual state to the view model. I am only thinking it would be better if it were an attached property instead of a control.</p> http://www.silverlightshow.net/items/Designer-friendly-MVVM-for-XAML-Windows-Store-applications.aspx#comment8970 FilipSkakun http://www.silverlightshow.net/items/Designer-friendly-MVVM-for-XAML-Windows-Store-applications.aspx Wed, 20 Feb 2013 19:29:23 GMT Re: Designer-friendly MVVM for XAML Windows Store applications You can find the VSMChangerBehavior in the original article (referenced in the intro of this one), which server the same purpose. http://www.silverlightshow.net/items/Designer-friendly-MVVM-for-XAML-Windows-Store-applications.aspx#comment8948 andrasvelvart http://www.silverlightshow.net/items/Designer-friendly-MVVM-for-XAML-Windows-Store-applications.aspx Sat, 09 Feb 2013 13:01:41 GMT Re: Designer-friendly MVVM for XAML Windows Store applications Great article...nice that you have shared this helpers...I want just to ask if it is possible to see the relevant implementation in Silverlight - I am aware that there we have the triggers to help us in the first case, but what abot the hidden control...what its the equivalent? http://www.silverlightshow.net/items/Designer-friendly-MVVM-for-XAML-Windows-Store-applications.aspx#comment8947 silverlightfan http://www.silverlightshow.net/items/Designer-friendly-MVVM-for-XAML-Windows-Store-applications.aspx Sat, 09 Feb 2013 09:05:35 GMT