Comments on: Animations and View State changes with MVVM http://blog.flexforcefive.com/?p=206 RIAs via Silverlight and Flex Fri, 09 Jul 2010 09:33:01 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Bob Bartholomay http://blog.flexforcefive.com/?p=206&cpage=1#comment-814 Bob Bartholomay Thu, 14 Jan 2010 17:40:22 +0000 http://blog.flexforcefive.com/?p=206#comment-814 Chris Klug! A thousand apologies for renaming you (you've been refactored!), thanks for bringing that to my attention as well as for the StoryboardManager irself. The post has been corrected. - bob Chris Klug! A thousand apologies for renaming you (you’ve been refactored!), thanks for bringing that to my attention as well as for the StoryboardManager irself. The post has been corrected. – bob

]]> By: Chris Klug http://blog.flexforcefive.com/?p=206&cpage=1#comment-813 Chris Klug Thu, 14 Jan 2010 10:15:28 +0000 http://blog.flexforcefive.com/?p=206#comment-813 BTW...I should probably add my 2 cents as well... I do agree with James that on of the end has to know a lot about the other. In my mind the ViewModel should be adapting the model and make it usable for the view. This can involve adding or modifying information from the view as well as add functionality. The reason for having a CommandManager for Silverlight was that there was no pre-made implementation available, and most of the ones I found were based on ButtonBase. In SL4, ButtonBase will have commanding support ond make the CommandManager somewhat useless, but on the other hand, only having commanding support on ButtonBase and not for all events is kind of limiting in my mind. Rishi's nRoute looks great for a lot of things, but a lot of my projects it is too heavy and too powerfull for what I need. And I don't really need the blendability in most situations... But that's just my 2 cents... Cheers...again... BTW…I should probably add my 2 cents as well… I do agree with James that on of the end has to know a lot about the other. In my mind the ViewModel should be adapting the model and make it usable for the view. This can involve adding or modifying information from the view as well as add functionality. The reason for having a CommandManager for Silverlight was that there was no pre-made implementation available, and most of the ones I found were based on ButtonBase. In SL4, ButtonBase will have commanding support ond make the CommandManager somewhat useless, but on the other hand, only having commanding support on ButtonBase and not for all events is kind of limiting in my mind.
Rishi’s nRoute looks great for a lot of things, but a lot of my projects it is too heavy and too powerfull for what I need. And I don’t really need the blendability in most situations…
But that’s just my 2 cents…
Cheers…again…

]]> By: Chris Klug http://blog.flexforcefive.com/?p=206&cpage=1#comment-812 Chris Klug Thu, 14 Jan 2010 10:08:21 +0000 http://blog.flexforcefive.com/?p=206#comment-812 Hi Bob! Thanks for mentioning my blog post about MVVM and animations. Would be cool if you could change my name from Chris North to Chris Klug though...since that is my name... :) Cheers! Hi Bob!
Thanks for mentioning my blog post about MVVM and animations. Would be cool if you could change my name from Chris North to Chris Klug though…since that is my name… :)
Cheers!

]]> By: Rishi http://blog.flexforcefive.com/?p=206&cpage=1#comment-526 Rishi Thu, 08 Oct 2009 19:37:07 +0000 http://blog.flexforcefive.com/?p=206#comment-526 My take on this problem is a very simple, basically data changes are your signifiers that effect changes in the View from your ViewModel. And to this concept, I've written something similar to Peter Blois’s DataTriggers but they are more generalized in a sense that they allow you to use operators using Blend triggers such as ==, >=, <=, ==null etc. and match that with any trigger-action you want including one to manage animations. See http://www.orktane.com/Blog/post/2009/09/29/Introducing-nRouteToolkit-for-Silverlight-(Part-I).aspx Cheers My take on this problem is a very simple, basically data changes are your signifiers that effect changes in the View from your ViewModel. And to this concept, I’ve written something similar to Peter Blois’s DataTriggers but they are more generalized in a sense that they allow you to use operators using Blend triggers such as ==, >=, <=, ==null etc. and match that with any trigger-action you want including one to manage animations.

See http://www.orktane.com/Blog/post/2009/09/29/Introducing-nRouteToolkit-for-Silverlight-(Part-I).aspx

Cheers

]]> By: Jeremy Likness http://blog.flexforcefive.com/?p=206&cpage=1#comment-511 Jeremy Likness Wed, 07 Oct 2009 14:41:08 +0000 http://blog.flexforcefive.com/?p=206#comment-511 I addressed the issue in a similar way, but by eliminating participating by the view model. It's a little different scenario: I wanted to trigger animations based on UI events such as selection changing. The solution is posted here: http://csharperimage.jeremylikness.com/2009/10/silverlight-behaviors-and-triggers.html I addressed the issue in a similar way, but by eliminating participating by the view model. It’s a little different scenario: I wanted to trigger animations based on UI events such as selection changing. The solution is posted here:

http://csharperimage.jeremylikness.com/2009/10/silverlight-behaviors-and-triggers.html

]]> By: Tweets that mention Binary Bob’s Blog » Animations and View State changes with MVVM -- Topsy.com http://blog.flexforcefive.com/?p=206&cpage=1#comment-459 Tweets that mention Binary Bob’s Blog » Animations and View State changes with MVVM -- Topsy.com Tue, 29 Sep 2009 14:03:19 +0000 http://blog.flexforcefive.com/?p=206#comment-459 [...] This post was mentioned on Twitter by SilverlightDC and codenenterp. codenenterp said: RT @brian_henderson: RT @brandontruong: Binary Bob’s Blog » Animations and View State changes with MVVM http://blog.flexforcefive.com/?p=206 [...] [...] This post was mentioned on Twitter by SilverlightDC and codenenterp. codenenterp said: RT @brian_henderson: RT @brandontruong: Binary Bob’s Blog » Animations and View State changes with MVVM http://blog.flexforcefive.com/?p=206 [...]

]]> By: Bob Bartholomay http://blog.flexforcefive.com/?p=206&cpage=1#comment-456 Bob Bartholomay Mon, 28 Sep 2009 19:19:59 +0000 http://blog.flexforcefive.com/?p=206#comment-456 Thanks for your thoughtful comments James. Semantics get in the way sometimes but I think we all agree about the separation between the View and VM being important and that Commanding is the ticket for communication between them. There's a very interesting <a href="http://forums.silverlight.net/forums/p/127825/293386.aspx#293386" rel="nofollow">discussion on MVVM</a> in the Silverlight forums that you'll probably enjoy. - bob Thanks for your thoughtful comments James. Semantics get in the way sometimes but I think we all agree about the separation between the View and VM being important and that Commanding is the ticket for communication between them. There’s a very interesting discussion on MVVM in the Silverlight forums that you’ll probably enjoy. – bob

]]> By: James Ashley http://blog.flexforcefive.com/?p=206&cpage=1#comment-451 James Ashley Mon, 28 Sep 2009 00:17:46 +0000 http://blog.flexforcefive.com/?p=206#comment-451 Bob, I like your solution. I don't think it is the case that the View knows nothing about the view-model, however. It actually has to know a lot about the fields provided on the view-model and the structure of the vm (or, conversely, the v-m has to know a lot about the view). In other words, they are fairly tightly coupled. Where it helps in SOC is that we take presentation logic that would otherwise be in the view and separate it out into its own class. Concerns such as presentation logic and state are separated out into the vm, while the view is concerned with data presentation, colors, layout and animations. At least that's my take on it. -James Bob,

I like your solution. I don’t think it is the case that the View knows nothing about the view-model, however. It actually has to know a lot about the fields provided on the view-model and the structure of the vm (or, conversely, the v-m has to know a lot about the view). In other words, they are fairly tightly coupled.

Where it helps in SOC is that we take presentation logic that would otherwise be in the view and separate it out into its own class. Concerns such as presentation logic and state are separated out into the vm, while the view is concerned with data presentation, colors, layout and animations.

At least that’s my take on it.

-James

]]> By: Links (9/24/2009) « Steve Pietrek – Everything SharePoint http://blog.flexforcefive.com/?p=206&cpage=1#comment-413 Links (9/24/2009) « Steve Pietrek – Everything SharePoint Fri, 25 Sep 2009 00:18:46 +0000 http://blog.flexforcefive.com/?p=206#comment-413 [...] Animations and View State changes with MVVM [...] [...] Animations and View State changes with MVVM [...]

]]>