Hi,
I have used this project as a vehicle to learn the MVVM pattern for WPF. I would be very interested and grateful to get some feedback on my approach. Especially from some of the Telerik guys (Evan, Miro, Ross).
Note, the app is by no means a finished product. It is merely a small project with the focus being on learning the pattern using the MVVM Light Toolkit and the Telerik controls.
One thing I set as a goal was to have the ViewModels completely decoupled. I did not want to include any ViewModel as a field in another ViewModel. I achieved that by using the MVVM Light Toolkit's messaging api.
As I don't have a senior resource for guidance, any feedback on my interpretation of the MVVM pattern would be greatly appreciated.
The project contains a read me file and can be downloaded here.
Cheers!
I have used this project as a vehicle to learn the MVVM pattern for WPF. I would be very interested and grateful to get some feedback on my approach. Especially from some of the Telerik guys (Evan, Miro, Ross).
Note, the app is by no means a finished product. It is merely a small project with the focus being on learning the pattern using the MVVM Light Toolkit and the Telerik controls.
One thing I set as a goal was to have the ViewModels completely decoupled. I did not want to include any ViewModel as a field in another ViewModel. I achieved that by using the MVVM Light Toolkit's messaging api.
As I don't have a senior resource for guidance, any feedback on my interpretation of the MVVM pattern would be greatly appreciated.
The project contains a read me file and can be downloaded here.
Cheers!
2 Answers, 1 is accepted
0
Evan Hutnick
Top achievements
Rank 1
Rank 1
answered on 29 Apr 2011, 06:13 PM
Hey David,
It definitely looks like you are on the right track with your approach in this project.
You pretty much hit on some of the targets with the MVVM pattern - bite-size chunks of code (great for testing), decoupled views and viewmodels, and using messaging to ensure that when one view/control needs to publish out info, another part of the project is listening and can respond, regardless of who the publisher and listener are.
If you keep on this approach you shouldn't run into any issues with the controls and your code should be easy to maintain and test, which are both great added bonuses of this pattern.
Do let us know if you run into any issues with the controls, we're always happy to help our customers to build good software. :)
-Evan
It definitely looks like you are on the right track with your approach in this project.
You pretty much hit on some of the targets with the MVVM pattern - bite-size chunks of code (great for testing), decoupled views and viewmodels, and using messaging to ensure that when one view/control needs to publish out info, another part of the project is listening and can respond, regardless of who the publisher and listener are.
If you keep on this approach you shouldn't run into any issues with the controls and your code should be easy to maintain and test, which are both great added bonuses of this pattern.
Do let us know if you run into any issues with the controls, we're always happy to help our customers to build good software. :)
-Evan
0
David
Top achievements
Rank 1
Rank 1
answered on 30 Apr 2011, 08:38 AM
Hi Evan,
Thank you so much for taking the time to look at my application.
I very much appreciate it.
And I'm very glad to hear that I am on the right track. I put a lot of work into trying to understand the pattern and a hands-on implementation is always the best way to learn.
I'll call out if I run into any issues or come up with any interesting questions.
Cheers
Dave
Thank you so much for taking the time to look at my application.
I very much appreciate it.
And I'm very glad to hear that I am on the right track. I put a lot of work into trying to understand the pattern and a hands-on implementation is always the best way to learn.
I'll call out if I run into any issues or come up with any interesting questions.
Cheers
Dave