新的一年，志向高远

颓废了半年的csdn博客要重新开写了！现在每天都可以学到很多东西，但不归纳总结很快就会忘记。

 

所以，我做出了艰难的决定：从现在开始每周至少两篇博客！

 

现在我正在学习objective-c，cocoa的框架是基于控制反转的，非常有利于企业级项目开发。今天网上看到这么一段对于cocoa框架的工作流程描述很清晰：

 

A key feature of many object-oriented systems (such as Cocoa) is "inversion of control", which basically means that the framework is running everything, and any code you write is under its control.

So, unlike PHP, you don't really write the code that executes at startup. What you do is define methods for the app delegate, controllers, views, and other objects, and let the framework invoke those methods as it needs to do so. You will never really see the overall "flow of control" throughout the program; you will only see it as control flows into your pieces of the program.

This can be confusing at first, as you try to figure out how to trick the framework into calling your code at the times and in the order you expect, but in the long run it actually makes things easier, as you can trust the framework to take care of a lot of things for you.

In a Cocoa app, a lot of the logic of the app will actually be in view controllers, rather than in the app delegate. The app delegate generally handles startup and shutdown responsibilities, but other objects do most of the work between startup and shutdown. So don't try to squeeze everything into the app delegate.

 

原地址：http://stackoverflow.com/questions/3464030/relationship-between-appdelegate-and-main-m