How to handle Different Modules in MVP ??
-
I am designing an UI Application with WPF (XAML and C#). This application interacts with Database(sqlserver 2008) too. This app is a tool for the project. I have to implement this with CAB architecture and Model-View-Presenter(MVP). If I have functionalites like 1. Uploading data to database 2. Downloading data from database. then, My questions are : 1. What will Model, View and Presenter roles in these applications. How the interfaces between these modules happen? Is it I have to Create IModel (interface) b/w presenter and Model, IView (interface) b/w presenter and view? So, my codebehind will have only events calls (like btn_click) ?? Which module handles Database access? I know I asked lot of questions, but I have made the UI ready for the rest of the work flow . I am sorry if many questions are put in one place. I will be so glad, if I can get answers for all the things. Kindly help me. Thank you, Ramm
-
I am designing an UI Application with WPF (XAML and C#). This application interacts with Database(sqlserver 2008) too. This app is a tool for the project. I have to implement this with CAB architecture and Model-View-Presenter(MVP). If I have functionalites like 1. Uploading data to database 2. Downloading data from database. then, My questions are : 1. What will Model, View and Presenter roles in these applications. How the interfaces between these modules happen? Is it I have to Create IModel (interface) b/w presenter and Model, IView (interface) b/w presenter and view? So, my codebehind will have only events calls (like btn_click) ?? Which module handles Database access? I know I asked lot of questions, but I have made the UI ready for the rest of the work flow . I am sorry if many questions are put in one place. I will be so glad, if I can get answers for all the things. Kindly help me. Thank you, Ramm
I would suggest some background reading on the MVP/MVVM patterns as there is something of a learning curve to get this right. You may like to start with Model View Presenter, and perhaps The Model-View-ViewModel.