[FBU iOS] Tip Calculator - Attempted Settings

[angierao]

/cc @codepathreview @codepath

I submitted the required part previously. I tried following the delegate pattern CodePath tutorial to add Settings, but it didn't end up working. I couldn't test it because the Settings button wouldn't show up on the Navigation Bar in the simulation. I would love to hear back about what I was missing. Thanks!

[sumade]

Hi Angeline,

First thing - you had three navigation controllers in your storyboard, when you need only one. Deleting the first two, and then setting the remaining one as the "Is Initial View Controller" allowed the Settings button to appear.

Second, you don't need to programmatically segue between view controllers. I can see why you did it, but it's not necessary. You can just add a "Settings" button in the storyboard to your ViewController, and then ctrl-click to create a "push" segue from the button to the "Settings" view controller. This will automatically embed navigation between the settings and main screens. You then need to add an implementation of prepareForSegue to share data between the navigation controllers.

We'll discuss this more next week, but good job trying to push yourself.

This prework is a preview of our weekly project process. Generally, weekly projects take between 5-10 hours to complete the required features and an additional 5-10 hours to complete the optional features. In general, we've seen that the more hours you log, the quicker you improve your proficiency with iOS. In particular, the optional extensions on each project are often the most valuable learnings since they dive deeper into common iOS use cases. We'll also be providing light code feedback for each submitted project once the program begins.

The purpose of this project was to begin to explore Xcode and to get a broad overview of iOS development using Swift. For example, in this project, we explored the following concepts:

• Code styling in Swift. You can find some code styling guides here:
  • Ray Wenderlich Swift Style Guide
  • Github Swift Style Guide
• Views are created in Storyboard, Interface Builder, or programmatically, but they have the same goal: instantiate, initialize, and layout view objects. We use IBOutlets to give names to view objects, similar to giving unique ids to divs in HTML.
• We registered for touch events, which can be done programmatically or via IBActions.
• View controllers have a set of methods that are called when it loads, appears, or disappears. These are called view controller lifecycle methods.
• Do your views look good on iPhone 4, 5, and 6? Do your views look good on both iOS 6 vs iOS 7/8? We will cover in class how to use Auto Layout to robustly design your views for different screen sizes and OS versions.
• After this assignment, you should understand the purpose of IBOutlets and IBActions as well as the basics of designing views and programmatically interacting with the views from the controller.