The Model
The Model is where the data for the application goes, The Model can contain:
- Web Services – A Silverlight application typically needs to communicate with the web server to get the data, you can put your web service methods here.
- Rest Services – The same as web services.
- Generic Collections – Basically any data.
The View Model
The View Model consists of:
- Properties – One of something. This could be a String or an Object. Implements INotifyPropertyChanged, so that any element bound to it, is automatically notified whenever it changes.
- Collections – A collection of something. This is of type ObservableCollection, so that any element bound to it, is automatically notified whenever it changes.
- Commands – An event that can be raised. Also, one parameter of type Object can be passed. This implements ICommand.
The View
This is the part that you can make with no code using Expression Blend.
An Outline
- Model
- Get your data any way you can. Usually calls to web services.
- View Model
- Consists of:
- Properties – One of something. This could be a String or an Object. Implements INotifyPropertyChanged, so that any element bound to it, is automatically notified whenever it changes.
- Collections – A collection of something. This is of type ObservableCollection, so that any element bound to it, is automatically notified whenever it changes.
- Commands – An event that can be raised. Also, one parameter of type Object can be passed. This implements ICommand.
- Implemented using Behaviors. Mostly the InvokeCommandAction Behavior
- View
- Properties
- Bind to a text box, radio button, toggle button, MediaElement, trigger an animation or ViewState change
- Collections
- Bind to List box, TreeMenu
- Commands
- Implemented using InvokeCommandAction behavior
- Bind to a ICommand in the ViewModel
- Indicate the ICommand that you want to raise
- Pass a parameter
Wednesday, August 18, 2010
Silverlight MVVM: An (Overly) Simplified Explanation
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment