Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am about to start work on a new app which is going to have thousands of lines of code.
I don’t want this code to be in just one .h and .m class files but rather split into several.
Is this even at all possible, and if so, please enlighten me as i have been struggling with this for days now.
Thanks
Sure, identify the specific roles your controller fills and see which ones make sense to break out into separate controller classes. For example you might have a controller to act as the delegate and data source of a table view or to manage one of your UIViewController’s subviews.
Whatever controller classes you define then should be subclasses of NSObject, not UIViewController. Take a look at http://blog.carbonfive.com/2011/03/09/abusing-uiviewcontrollers/ and see if you find that helpful.