GWT Atchitecture anyone?
This video begins the subject of GWT design choices. The video touches on a few thing like the :
- HandlerManager class in GWT 1.6
- MVP and testing the presenter
This was found on this post – http://stackoverflow.com/questions/1234389/whats-your-recommendation-for-architecting-gwt-applications-mvc-mvp-or-custom
Since I am mainly just familiar with MVC , lets get into MVP…
From this Model-View-Presenter post, it illustrates their are two flavors of the MVP:
a) Dolphin Smalltalk’s MVP – http://martinfowler.com/eaaDev/SupervisingPresenter.html
b) Passive View – http://martinfowler.com/eaaDev/PassiveScreen.html
View – widgets, responds to user actions, turns to the presenter to handle these user actions
Presenter – presentation logic, tightly coupled with the view, commands the model, changes presentation according to the application rules.
Model – business objects , doesn’t know anything about View/Presenter.
“in MVC there is controller for every widget, and every widget on the screen surface is called view. In MVP on the other hand, due to the elimination of the controller, there is no sentiment for a single widget and the screen itself is called view.”
Another interesting thing is the post on difference between a toolkit vs framework
- gxt mvc
- gwt tiger