We have covered the MVC architecture concept in Chapter 2, Getting Started, already, but let's do a quick overview one more time.

The Model represents the data we want to manipulate. It is a representation of the tables we have in the database. A Model instance represents a single data row of a table. The Store will be responsible for loading the collection of models from the server. A Store is usually bound to a View. A View is the component with which the user is seeing the screen (we have created a few so far; for example, a GridPanel provides a visual representation of data found in a Store.). And the Controller is what keeps everything together. The Controller will capture the events from the View and will execute some logic based on it. The Controller can also redirect the logic to the Model or the Store, making all the pieces communicate with each other, behaving like a mediator.

In the previous chapters, we used the MVVM architecture. We saw an example...