ModelViewController Design Patterns n n n The hard

Model-View-Controller

Design Patterns n n n The hard problem in O-O programming is deciding what objects to have, and what their responsibilities are Design Patterns describe the higher-level organization of solutions to common problems Design patterns are a current hot topic in O-O design 2

The MVC pattern n n MVC stands for Model-View-Controller The Model is the actual internal representation The View (or a View) is a way of looking at or displaying the model The Controller provides for user input and modification These three components are usually implemented as separate classes 3

The Model n Most programs are supposed to do work, not just be “another pretty face” n n The Model is the part that does the work--it models the actual problem being solved The Model should be independent of both the Controller and the View n n but there are some exceptions useful programs existed long before GUIs But it can provide services (methods) for them to use Independence gives flexibility, robustness 4

The Controller n n The Controller decides what the model is to do Often, the user is put in control by means of a GUI n n in this case, the GUI and the Controller are often the same The Controller and the Model can almost always be separated (what to do versus how to do it) The design of the Controller depends on the Model The Model should not depend on the Controller 5

The View n n Typically, the user has to be able to see, or view, what the program is doing The View shows what the Model is doing n n n The View is a passive observer; it should not affect the model The Model should be independent of the View, but (but it can provide access methods) The View should not display what the Controller thinks is happening 6

Combining Controller and View n n Sometimes the Controller and View are combined, especially in small programs Combining the Controller and View is appropriate if they are very interdependent The Model should still be independent Never mix Model code with GUI code! 7

Separation of concerns n n As always, you want code independence The Model should not be contaminated with control code or display code The View should represent the Model as it really is, not some remembered status The Controller should talk to the Model and View, not manipulate them n The Controller can set variables that the Model and View can read 8

The Bouncing Ball Applet n n Each click of the Step button advances the ball a small amount The step number and ball position are displayed in the status line 9

The Ball Applet: Model n n n The Ball Applet shows a ball bouncing in a window The Model controls the motion of the ball In this example, the Model must know the size of the window n n so it knows when the ball should be made to bounce The Model doesn’t need to know anything else about the GUI 10

Observer and Observable n n java. util provides an Observer interface and an Observable class An Observable is an object that can be “observed” An Observer is “notified” when an object that it is observing announces a change Here’s an analogy: n n n An Observable is like a Button An Observer is like a Listener You have to “attach” a Listener to a Button 11

Observable n n An Observable is an object that can be “observed” An Observer is “notified” when an object that it is observing announces a change n When an Observable wants the “world” to know about what it has done, it executes: n n set. Changed(); notify. Observers(); /* or */ notify. Observers(arg); n The arg can be any object The Observable doesn’t know or care “who is looking” But you have attach an Observer to the Observable with: n my. Observable. add. Observer(my. Observer); 12

Observer n n n Observer is an interface An Observer implements public void update(Observable obs, Object arg) This method is invoked whenever an Observable that it is “listening to” does an add. Notify() or add. Notify(arg) The obs argument is a reference to the observable object itself If the Observable did add. Notify(), the arg is null 13

Sample CRC index card Class Name Responsibilities . . Collaborators . . 14

Model Set initial position Move one step No collaborators. . . . but provide access methods to allow view to see what is going on 15

Model I import java. util. Observable; class Model extends Observable { final int BALL_SIZE = 20; int x. Position = 0; int y. Position = 0; int x. Limit, y. Limit; int x. Delta = 6; int y. Delta = 4; // more. . . 16

Model II void make. One. Step ( ) { x. Position += x. Delta; if (x. Position < 0) { x. Position = 0; x. Delta = -x. Delta; } // more. . . 17

Model III if (x. Position >= x. Limit) { x. Position = x. Limit; x. Delta = -x. Delta; } // still more. . . 18

Model IV y. Position += y. Delta; if (y. Position < 0 || y. Position >= y. Limit) { y. Delta = -y. Delta; y. Position += y. Delta; } set. Changed(); notify. Observers(); } // end of make. One. Step method } // end of Model class 19

Model (repeated) Model Set initial position Move one step No collaborators. . . . but provide access methods to allow view to see what is going on 20

The Ball Applet: View n n The View needs access to the ball’s state (in this case, its x-y location) For a static drawing, the View doesn’t need to know anything else 21

View Paint the ball Get necessary info from Model 22

View I import java. awt. *; import java. util. *; class View extends Canvas implements Observer { Controller controller; Model model; int step. Number = 0; // more. . . 23

View II public void paint (Graphics g) { g. set. Color (Color. red); g. fill. Oval (model. x. Position, model. y. Position, model. BALL_SIZE); controller. show. Status ("Step " + (step. Number++) + ", x = " + model. x. Position + ", y = " + model. y. Position); } // end paint method 24

View III public void update(Observable obs, Object arg) { repaint(); } } // end class 25

View (repeated) View Paint the ball Get necessary info from Model 26

The Ball Applet: Controller n n The Controller tells the Model what to do The Controller tells the View when it needs to refresh the display The Controller doesn’t need to know the inner workings of the Model The Controller doesn’t need to know the inner workings of the View 27

Controller Create Model Create View Give. View access to Model Tell Model to advance Tell View to repaint Model View 28

Controller I import java. applet. *; java. awt. event. *; java. util. *; public class Controller extends Applet { Panel button. Panel = new Panel ( ); Button step. Button = new Button ("Step"); Model model = new Model (); View view = new View (); // more. . . 29

Controller II public void init ( ) { // Lay out components set. Layout (new Border. Layout ( )); button. Panel. add (step. Button); this. add (Border. Layout. SOUTH, button. Panel); this. add (Border. Layout. CENTER, view); // more. . . 30

Controller III // Attach actions to components step. Button. add. Action. Listener(new Action. Listener ( ) { public void action. Performed (Action. Event event) { model. make. One. Step (); } }); // more. . . 31

Controller IV // Tell the View about myself (Controller) and // about the Model model. add. Observer(view); view. controller = this; } // end init method // more. . . 32

Controller V public void start ( ) { model. x. Limit = view. get. Size( ). width - model. BALL_SIZE; model. y. Limit = view. get. Size( ). height - model. BALL_SIZE; repaint ( ); } // end of start method } // end of Controller class 33

Controller (repeated) Controller Create Model Create View Give. View access to Model Tell Model to advance Tell View to repaint Model View 34

The End 35