¡@
2014/10/15 ¤U¤È 10:05:43
iphone Programming Glossary: couplingCommunication between view controllers http://stackoverflow.com/questions/1880033/communication-between-view-controllers iPhone development course which advocate the User being simply assigned and not retained in that situation loose coupling . I have also seen arguments for a form of delegation where an assigned id object would be used on the second controller..
Why does Core Data initialization fail when I attempt to do it at these points? http://stackoverflow.com/questions/2022432/why-does-core-data-initialization-fail-when-i-attempt-to-do-it-at-these-points delegate self.managedObjectContext appDelegate managedObjectContext retain This is bad form. It introduces coupling into your design. Use dependency injection just like the example. It makes your app more flexible. Because from the app..
How can I pass information between 2 different View Controllers? http://stackoverflow.com/questions/2646881/how-can-i-pass-information-between-2-different-view-controllers
Discuss on MVC implementation on iPhone http://stackoverflow.com/questions/3845951/discuss-on-mvc-implementation-on-iphone a method of the view interface The advantage of not letting the controller directly work on view UI elements is a low coupling and therefore it is possible to test the view easier. The view can be launched and tested on isolation or with a mock controller..
Difference between protocol and delegates? http://stackoverflow.com/questions/5431413/difference-between-protocol-and-delegates regardless of what class it is. This is a great way of avoiding the inheritance design pattern and avoids tight coupling. Delegates are a use of the language feature of protocols. The delegation design pattern is a way of designing your code.. protocol so it knows that it can call the implemented methods at given times. This design pattern is a great way of decoupling the classes because it makes it really easy to exchange one delegate instance for another all the programmer has to do is..
What's the best way to communicate between view controllers? http://stackoverflow.com/questions/569940/whats-the-best-way-to-communicate-between-view-controllers to be communicated Define input parameters for your view controller For communicating back up the hierarchy use loose coupling Define a generic interface for observers like delegation This slide is then followed by what appears to be a place holder..
Example or explanation of Core Data Migration with multiple passes? http://stackoverflow.com/questions/5995231/example-or-explanation-of-core-data-migration-with-multiple-passes our new object newObject setValue dateFormatter stringFromDate date forKey @ printedDate dateFormatter release do the coupling of old and new manager associateSourceInstance sInstance withDestinationInstance newObject forEntityMapping mapping return..
Alternative to global variables in app delegate http://stackoverflow.com/questions/7635008/alternative-to-global-variables-in-app-delegate sharing some information in the models. with a global in your sample you are crossing many implementations which adds coupling increases dependency etc.. so if you can take this approach and localize the execution state you're off to a good start...
How to pass object on modal view's dismissal http://stackoverflow.com/questions/7962519/how-to-pass-object-on-modal-views-dismissal a protocol and use a delegate to pass information backwards in your view controller hierarchy. This avoids the tight coupling which is happening in your example when you link back to self.parentViewController.navigationController . What happens if..
http://stackoverflow.com/questions/8032652/is-it-ok-to-use-of-a-notification-to-communication-back-to-the-main-thread-of-an NSNotificationCenter defaultCenter postNotificationName @ SOMENAME object self Unfortunately this introduces a subtle coupling between the sender and receiver in that you are modifying the sender to accommodate the receiver. An even better solution..
|