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.
Let’s assume I have dragable nodes in an WPF MVVM application. I need to load and save the position of a node as well as its logic. The simplest approach would be to save the position along with the logic in one xml file through a repository. However, that would mean I have view information in the model and view model.
Is there a best practice approach regarding this scenario, maybe one that I have not considered so far?
If your application cares about the positioning of the UI elements it displays to the user, then I ‘d say that the data defining this positioning is a very legitimate part of your Models.
Don’t confuse the ideal of decoupling the UI from your Models and ViewModels with real business requirements. For example, in an application like Visio you could say that the exact placement of objects in the page is a “view-only detail”, and what matters is only the properties of the object and the connections between them. However, from the user’s perspective, the placement of objects in the workspace very much matters. In other words, it is part of your data model.