Under Construction

View Model help seperate DTO data transfer objects from the view and provide a mapping layer for data binding scenarios. MVVM introduced Command binding but Xaml Mvp is about seperating behaviour into a Presenter. This allows you to incorporate, at the very least, save operations without co-ordinating this through the view model.

Actually an interesting scenario is a CheckBox. You can data bind the IsChecked property to store the data into a ViewModel you then bind to the Checked / Unchecked event handler in the Presenter (keeping markup clean and away from the view) allowing you to respond to the behaviour of a check box (run an animation etc.)

Last edited Jan 22, 2011 at 5:27 AM by hoffmanic, version 1


No comments yet.