Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Would it be incorrect to make all my View Models / Presentation Models static classes so that if any other View Presenter wanted to change a view model other than its own it could easily aquire a reference to it?
If this is the wrong approach how would you achieve it?
Static ViewModels sounds like an awful idea (I consider static evil as a general principle). This would mean that you can’t have more than one instance of a ViewModel. I can think of many examples of UI where there are several instances of the same View type, but that wouldn’t be possible with static ViewModels.
If you want to enable communication across Views, Publish/Subscribe (events) are a much better option.
Remember that when we talk about ViewModels/Presentaion Models they usually expose underlying Domain Objects. If you have sevaral Views that display parts of the same Domain Object, you can have the Domain Object raise events when it changes state, and any ViewModel that display data from that Domain Object can subscribe to those events and update their controls accordingly.