Lazy User Interface Part II

In order to make the application testable, proper separation is required. I will be using MVP pattern to separate out the tiers. MVP is a derivitive of MVC, the only difference is the View only communicates with the Presenter, and the Model only knows about the Presenter, not the View. I personally like MVP better because I think it is a little cleaner when the Model does not know about the View.

Since I have been shopping around for a house, I decided to make this superficial real estate application. The actual structure of the application and the data it holds are irrelevant, that is why they are over simplified. The import thing here is the interactions between objects to make the code testable. I might update the UI to make it more "realistic" later if it requires it.

Before we start, let me explain the basic layout of the UI. There are three views, and one presenter per view. The view on the left is the NavigationView. The purpose of it is to load fictitious data into the top right view which is the RealtorView. When the user selects a realtor from the RealtorView it will show all the customers associated with that particular realtor. For those who noticed the title of the article, Lazy User Interface is refering to making the view as lazy as possible by delegating everything to its presenter. I will start coding the lazy UI in the next post.