Why Pattern?
When developing client tier of application using html, there are certain limitations in using patterns because code is going to be in xml so while developing Swing/GWT/Desktop application’s GUI, we have support of Inheritance, Polymorphism and other constructs of language, so in this world, we can play around with patterns, so if we use patterns properly, reusability can make our life easier and it may get worst if not used properly.
HMVC(Hierarhcical Model View Controller) Introduced:
HMVC can be seen as extended version of MVC pattern. We can divide our GUI into different GUI objects some of which will be for navigation purpose (Menubar), some for displaying/editing data(Grid/Tree/Forms) and others may be use for just layouting purpose. So we clearly identify three major aspect of GUI objects.
- Layouting – It is taken care by View in HMVC.
- Handling user interactions – Its Controller’s responsibility.
- Server Interactions And Hold Data Being Displayed – Model handles this.
In HMVC, we assign dedicated Controller and Model for each of these objects. It is not necessary to provide each of the GUI object its own controller and model. To keep it simple, we can give dedicated controllers and models only to all the Pages, Grid, Dynamic Tree and other major navigation areas e.g. ContentPanel.
I understand why the Lord sent my family under your pastoral care thank you for being attentive to the voice of God.Wonder how many church leaders would recognize Jesus if he stood before them today, similarly to the pharisees who missed the holy visitation as the long awaited one walked among them?