MVC for Desktop Application - Part 3
1 like1,377 views
This document provides an introduction to using the model-view-controller (MVC) pattern for desktop applications. It discusses how MVC has influenced desktop development and provides a brief overview of the Cocoa framework. It then walks through building a simple Cocoa application using Interface Builder to lay out the user interface, creating a controller class to link the UI and logic, and binding controller methods to user interface elements. The document notes that Cocoa achieves separation of UI and logic through resources and controllers. However, it also notes limitations of Cocoa including its dependence on Objective-C and the Mac OS X platform. It concludes by providing references on design patterns and MVC.
MVC for Desktop Application - Part 3
- 1. Introduction to MVC for Desktop ApplicationCourse C1001He Shiming2010-9
- 2. MVC in Desktop Applicationshow MVC web-apps affected desktop development
- 3. Brief Look of Cocoa Framework
- 4. A Simple Cocoa ApplicationStart inInterface BuilderLaying out form-styleinterfaceusing viewsand widgets
- 5. A Simple Cocoa ApplicationController-styleclass named“fieldController”to serve as anaction bridgebetween UI andunderlyinglogic
- 6. A Simple Cocoa ApplicationBind this controllerto UI, drag anNSObject to ourresource, and linkit to fieldControllerusinginspector
- 7. A Simple Cocoa ApplicationRight click thisobject and targetour text field
- 8. A Simple Cocoa ApplicationRelease mousebutton and assign“textField” outletto this text field
- 9. A Simple Cocoa ApplicationDrag “Set Text”button to ourfieldController
- 10. A Simple Cocoa ApplicationRelease mousebutton and assign“setText” methodto this buttonaction
- 11. A Simple Cocoa ApplicationFinally,implement“setText”infieldController
- 12. A Simple Cocoa Application
- 13. Cocoa Framework Achieved:Isolation of user interface from application logicUser interface being established from a resource (.nib from Interface Builder) file, not from code (similar to .NET)Action being responded and processed via a controller (not exactly the controller of MVC per se)Reusable user interface resource and controller logic
- 14. But Cocoa is Still Not Great Because:It’s Objective-C based, and only available on Mac OS XProgramming based largely on visual design, not codingOnce programmed, the application has great dependency on Cocoa framework itselfController has dependency on view, it cannot be written without knowing the specifics of viewNot solving parallel development problem, no good way for peer review
- 15. References Regarding Design Patternshttp://stackoverflow.com/questions/516411/raw-function-pointer-from-a-bound-method/516537http://stackoverflow.com/questions/946834/is-there-a-design-pattern-that-deals-with-callback-mechanism
- 16. References Regarding MVC and Othershttp://en.wikipedia.org/wiki/Model–View–Controllerhttp://www.oracle.com/technetwork/articles/javase/mvc-136693.htmlhttp://www.djangoproject.com/http://code.google.com/webtoolkit/