Thanks for the book. I think it does a nice job of describing how to implement some of the core MVVM concepts. The perspective taken in the book of walking through the demo application works well, although this means things that you might want
to think about that the application doesn't do aren't really discussed at all. That being said, it's a useful leg up for me, trying to go from MFC to MVVM in one step.
Perhaps I am being dumb, but I am having dificulty deliniating the Model from the ViewModel in this example BubbleBurst app.
I guess the model is sort of spread out across all the instances of the BubbleViewModel?
Maybe I have got completely the wrong end of the stick here, but what I would expect to see is an explicit Model class, which encapsulates the board state. This would be the place you would implement, say, load/save functionality. I guess then each instance
of BubbleViewModel would have a reference to the bubble data from the model.
This gets me to the point that is missing from the book - How do you tie the ViewModel to the Model, such than when one part of the app updates the Model, another part's ViewModel & View is notified.
I'm not really sure about the BubbleViewModel/View either. It doesn't seem terribly scalable to have a view and a model for each bubble on a grid. Would it make sense to have BubbleMatrixViewModel, and custom view which renders this?
As you can see, I'm still struggling with the concepts, so perhaps this is all mindless babble.