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 currently testing this environment and would like to ask about the best strategy loading/unloading for a multiview application.
The app i am playing around with should have the following:
Main: a normal view with 5 x buttons (Play, Leaderboard, Properties, Instructions and an “i” button for about)
The Properties is a tableView where each cell opens up a new tableView with the actual properties.
What is the best strategy from a flexibility and memory point of view to do this?
Store the extra views in their own nib-files. Load them in when needed using
+[NSBundle loadNibNamed:@"nibFileName" owner:self]. Replaceselfwith whatever object that you want the nib’s “File’s Owner” to point to. (Usually it would beself, though, since it would be the view’s controller whose job it was to create the nib; and the controller is also typically what you want as your File’s Owner.)Disclaimer: I’m basing this on my knowledge of Cocoa on the desktop, but I’m pretty sure nib-files work the same on the iPhone.