Chapter 3 – Model-View-Controller.pptVIP

Chapter 3 – Model-View-Controller 3.1 Introduction MVC Architecture and it’s application in Swing Model-view-controller architecture uses OO design principles to modularize applications into Data components: maintain raw application data Presentation components: provide visual representation of data Input-processing components: handle input from the user Delegate-model architecture Is a variant of the MVC architecture Observer design pattern A design pattern built into the MVC architecture Objectives After we are through with the material from this chapter, you should be able to design programs using the MVC architecture You will be able to take advantage of advanced swing components that use the delegate-model architecture JList, JTable, JTree 3.2 Model-View-Controller Architecture The MVC separates application data from the graphical presentation components and input-processing logic. MVC originally appeared in Smalltalk as a method for separating user interfaces from underlying application data Model Contains application data When the model changes, it notifies the view View Generates a presentation of the data stored in the model The view updates its presentation whenever the model changes Controller Implements logic for processing user input Use user provided input to modifies model Model-View-Controller Architecture Model-View-Controller Architecture The MVC allows multiple Views and Controllers corresponding to a single Model in an application A developer can provide additional views and controllers for an application model without changing the existing components Java’s Swing components implements a variant of the MVC Combines the view and controller into a single object, called a delegate 3.2 Model-View-Controller Architecture (Cont.) Delegate-model architecture Variant of MVC Combines the view and controller into a single object - delegate The delegate provides both a graphical presentation of the model and an interface for modifying the model Example E