What is the reason Google says MVP is recommended for building GWT apps? I really like MVC approach when View layer is directly aware of what the Model is – why do they think that’s bad idea?
Share
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.
What is the reason Google says MVP is recommended for building GWT apps? I really like MVC approach when View layer is directly aware of what the Model is – why do they think that’s bad idea?
As Google explains: “this model allows us to minimize our use of GWTTestCase, which relies on the presence of a browser, and, for the bulk of our code, write lightweight (and fast) JRE tests (which don’t require a browser)”.
Also:
What is the advantage of the MVP pattern (GWT)
MVC or MVP? Which design pattern makes the most sense?