MVP Architecture

Overview

The Model-View-Presenter (MVP) architecture is outlined in Large scale application development and MVP. At the heart of the MVP design pattern is the separation of application logic (presenter) from the UI presentation (view). It is recommended when developing GWT apps for the following reasons:

• Decouples development in a way that allows multiple developers to work simultaneously
• Allows writing lightweight and fast JRE unit tests which don't require a browser
• Allows creating different views for different devices that share the same presenter logic

The class diagram below shows the main classes and interfaces of the Todor application and their separation into the following categories, which are explained in more details below:

• Model
• View
• Presenter
• AppController

Model

The domain model classes represent entities from our problem domain. In Todor, these are documents and items. Domain model classes are lightweight POJOs which are shared between the client and the server. See Domain Model Classes for more information.

See:

• Document.java
• Item.java