gwt-mpv is an application framework for writing GWT applications. It enables you to:
*) architecture without boilerplate (10x less programmer-written LOC than hand-coded MVP)gwt-mpv has three main features:
ui.xml files to generate all of the view/display interface and view/UiBinder implementation boilerplate needed for fast, DOM-decoupled unit testsgwt-mpv does not:
Provide extensive out-of-the-box widgets or look & feel (e.g. ExtGWT).
The assumption is that your app will have it’s own design, likely driven from a designer’s mock up where you convert the initial static CSS/HTML into GWT’s CSS/UiBinder structure.
The latest release of gwt-mpv can be found in the joist maven repo:
For integrating gwt-mpv into your project, see getting started.
Following the gwt-mpv github project is the best way to stay in the loop on changes.
gwt-mpv* Yes, the project name gwt-mpv purposefully reorders the “MVP” acronym because: gwt-mvp is too generic, and the view should be the dumbest part of your app, so the “V” should come last.
Also note that Dolphin Smalltalk called it’s framework “model presenter view”.