You can find more information about MVVM in Internet. But here are the basics:
  1. MVVM means Model, View and View Model (view’s model).
  2. The MVVM pattern provides a clean separation between application's user interface, its presentation logic, and its business logic and data by separating each into separate classes.
  3. The view's responsibility is to define the structure and appearance of what the user sees on the screen. Ideally, the code-behind of a view contains only a constructor that calls the InitializeComponent method.
  4. The view model encapsulates the presentation logic and data for the view. There is no direct reference from the view model to the view. The view model defines public properties and commands that are used by the view to render the model.
  5. The model encapsulates business logic and data. The model should not contain any user task specific behavior or application logic.
Windows Runtime allows defining the view by using XAML and its code behind. The mapping between view model public properties and UI can be defined by using data binding mechanisms.

Our library helps you to:
  1. Define your views by using XAML only (no extra code behind).
  2. Implement view models that can be easily bound to views.
It also extends Windows Runtime XAML abilities by providing some useful behaviors. So you do not have to write code behind in most common situations.

Last edited Mar 18, 2013 at 3:54 PM by mglukhankov, version 1


No comments yet.