{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

03-Architecture - User Interface Software Architecture 1...

Info icon This preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
1 1 User Interface Software Architecture 2 The Three Characteristics Every GUI component has three characteristics Contents (state of a button, text in a text field, etc.) Visual appearance (color, size, etc.) Behavior (reaction to events) Complex interaction between these characteristics Visual appearance depends on the look and feel Visual appearance depends on state changes State depends on events
Image of page 1

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
2 3 Contents and the Look and Feel GUI components should be implemented in such a way that they will work well no matter what “look and feel” is installed Store the “look and feel” and the “contents” in separate objects 4 The Model-View-Controller Design Pattern Model Store the contents View Display the contents Controller Handle the events (i.e., user input)
Image of page 2
3 5 The Model-View-Controller Design Pattern 6 The Model Responsible for data Maintain application state Implement state-changing behavior (i.e., change the content and to discover what the content is) Notify dependent views/controllers when changes occur Examples Button – pushed in or not; active or inactive; etc. Text field – string object Model The quick brown fox jumped over the lazy dog View The model has no user interface rown fox jumped o
Image of page 3

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
4 7 The View
Image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.