Building the Detail Data View
In Chapter 8, “Building on the Data Model,” you expanded the model and converted it to a
Party class in your project. As noted, there are two additional steps to take with your expanded data model:
• Modify the app to use your
Party class instead of what is already there.
• Add a text field to display the
partyName attribute of the
Party class in the detail view controller.
Once the text field is added, you’ll be able to add fields for the other data elements of
Party. That will go a long way to completing the iPhone interface. At that point, you’ll learn how to lay out the iPad interface.
These steps are somewhat different from the steps you have previously taken to build the Party Planner app. Unlike building your data model with the Core Data Model editor or designing your user interface with storyboards, you’ll have to get out your keyboard and start dealing with code—yes, typed-in code in the great tradition of programmers for over half a century.
Actually, “typed-in” is not quite accurate. Yes, there’s some typing to do, but much of the code is pasted in; other sections of code are in the template and they need a little tweaking. And even when you’re typing in code, Xcode’s Fix-It and code completion will let you press the Return key or click an option to have Xcode do the work for you.
Nevertheless, you’re now in the world of text-based code for a while, but you’ll return to the graphical user interface of storyboards to develop ...