Fugenx Technologies Private Limited

More documents

Recommendations

Info

Model View Controller � Model : The Model subsystem is composed of the objects that provide the unique capabilities and information storage for an application. Models contain all of the rules for processing application data.The Model is the key subsystem that makes an application valuable. It’s critically important that the Model subsystem is able to stand alone without dependencies on either theView or Controller subsystems. � View : The View subsystem presents information gathered from the Model and provides a way for users to interact with information.The key to understanding Views is to recognize that there are invariably a multitude of Views.For example, there may be a graphical user interface View, a printed report View, a command line View, a Web-based View, and a scripting language View that all interact with the same Model. � Controller : The purpose of the Controller is to decouple the Model from the Views. User interaction with a View results in requests made to the Controller subsystem, which in turn may request changes to information in the Model.The Controller also handles data translation and formatting for presentation to the user © 2011, FuGenX <strong>Technologies</strong> Confidential 2 2
Model View controller - Example � The controller identifies which Model objects need to be updated based on the new value.The Controller sends messages to the Model objects to request the updates. In step 3, the Model objects react to the messages about updates.The Model objects might constrain the updated values to fall within application defined limits or perform other validation. Application logic is applied to the updated values, and other Model objects may be updated as a side effect.The Model then notifies the Controller that the Model has changed. Finally, in step 4, the Controller sends messages to View objects so that they reflect the changes that occurred in the Model.There may be many parts of theView that are updated. Slider © 2011, FuGenX <strong>Technologies</strong> Confidential 3 3
Page 1: FuGenX Technologies Private Limited
Page 5 and 6: NSObject � NSObject is a base cla
Page 7 and 8: NSObject Methods � init - Initial
Page 9 and 10: Over-riding Base Class Methods �
Page 11 and 12: Two Stage Creation � The Two-Stag
Page 13 and 14: Two - Stage Creation Due to so many
Page 15 and 16: Two - Stage Creation Zones Memory z
Page 17 and 18: Two - Stage creation � Regardless
Page 19 and 20: Default Template Methods Template M
Page 21 and 22: Template Method When You Should Cal
Page 23 and 24: NSObject Template Methods Template
Page 25 and 26: Dynamic Creation The basis of this
Page 27 and 28: Category We use the Category patter
Page 29 and 30: Category @implementation NSMutableA
Page 31 and 32: Singleton � The Singleton pattern
Page 33 and 34: Singleton Creating and Accessing a
Page 35 and 36: Singleton A basic implementation of
Page 37 and 38: + (id)new { return [self alloc]; }
Page 39 and 40: Deallocation Singleton + (void)atte
Page 41 and 42: Delegates � A delegate is an obje
Page 43 and 44: Delegates © 2011, FuGenX Technolog
Page 45 and 46: Delegates Slider © 2011, FuGenX Te
Page 47 and 48: @implementation Controller Delegate
Page 49 and 50: Delegates @protocol ModelDelegate
Page 51 and 52: Delegates @protocol SliderDelegate
Page 53:
Thank You © 2011, FuGenX Technolog
show all

Fugenx Technologies Private Limited

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?