Search

Friday, October 1, 2010

MVVM Overview (part 2 : Model,ViewModel,View, ... what)

The Model is simply your business or data layer. It's completely UI independent.So when you develop for example a WPF application,
and you would like to switch it to a silverlight application later on, you can just re-use your Model.

Your ViewModel exposes the data to your View. So it's 'custom' build to show the data for your View,
even though your ViewModel acts independently from your View, and your View is developed independently from the ViewModel.
So they are in a way 'connected'.

Your view just connects to the data with databindings. They can be one way bindings (property to source or the opposite) or two
way binding. I'll give examples of that later on, basically it means that if you change something on the screen, if it gets
changed in your properties too, or only your property/screen changes.

17 comments:

  1. Its UI independent? Didnt know that

    ReplyDelete
  2. I appreciate you visiting my blog and providing input on my most recent post.

    ReplyDelete
  3. uff can you explain this in a picture?

    smoochies n' poopies! :*

    ReplyDelete
  4. Is this for graphic settings on our monitors? Hehe
    Mesty =)

    ReplyDelete
  5. your blog has drawn my interest, like learning new things :D

    ReplyDelete
  6. Ow wow, complicated but something different =D

    Pretty nice post, you should check out my chill music post on my music blog.

    ReplyDelete
  7. I didn't really understand this at first until I read your last post. Good shit.

    ReplyDelete
  8. interesting things to read

    following and supporting!

    ReplyDelete
  9. Thanks for explaining, the MS terminology can be confusing at times. It's good that they're finally pushing the layer model

    ReplyDelete
  10. Interesting, ill give you that.

    ReplyDelete
  11. Great post!

    looking forward to reading the next one

    ReplyDelete
  12. Wow. I feel smarter just reading that.

    ReplyDelete