In This Chapter
Taking another look at model objects
Taking advantage of reusable view controllers and models
Accessing data on the Internet
Saving and reading files
Getting the infrastructure in place for a new iPhone application is certainly a crucial part of the development process, but in the grand scheme of things, it's only the spadework that prepares the way for the really cool stuff. After all is said and done, you still need to add the content that the users will see or interact with. Content is, after all, the reason they bought this application.
Chapter 14 was all about infrastructure — and a very interesting chapter it was — but this chapter moves on from there to content views and how to implement them.
This is actually less difficult than it sounds. The real key to creating an extensible application — one where you can easily add new views — is the program architecture. Once you have a table view in place, you have the structure necessary for navigation in your application. With that navigation architecture — along with the MVC pattern I've been touting all along — creating the views, view controllers, and the model turns out to be somewhat pedestrian. You do more or less the same thing over again for each new content view. (Oh well, boring is sometimes good.)
If you've been dutifully following along in this book chapter by chapter, you probably already know the basics of creating a view and its view controller. If so, no big ...