iPhone Core Data 1 - Intro
Why Stack Overflow recommends it
Stack Overflow users link it when answering beginner iOS questions about storing data with Core Data and showing it in table views.
Recommended by 3 people across 4 different months, 2012 to 2013.
What it is
A 13-minute iOS tutorial from iElmoTutorials, the first in a series, introducing Core Data on iPhone. It walks through entering data and fetching results, and later parts cover loading entities into table views and detail views.
What people said
Strong rec Bad_APPZ · 2012-11 · Stack Overflow · on “How to display a Core Data entity in UITableView”
if you are interested in adding table view cell, and editing/deleting them. You should definitely take a look at this tutorial [this video] i used this tutorial twice, and it got me up to speed with core data very fast! He is a great teacher! Its a 4 part series, he teaches you how to load entities on different views etc!
Recommends Alex Moyer · 2013-02 · Stack Overflow · on “Store and Manage Data for Simple App”
Take a look into core data. It seems very difficult once you get started. But once you get into it, it gets pretty straightforward from there. Check out this tutorial [this video] he helped me get going. Hth
Recommends LAMBORGHINI · 2013-05 · Stack Overflow · on “How to show a viewController for each cell created by user?”
Allow the user to add cells to the table view : Here [LINK] Then in the didSelectRowAtIndexPath method, when the user selects a row, load the same view each time. MyDetailView , but depending on which row was pressed, populate the detail view with certain data. Go watch this [this video] youtube tutorial it shows how to do this, and save it with core data. Good luck :) EDIT -(void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath{ UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"Storyboard" bundle:nil]; DetailView * detail = (DetailView *) [storyboard instantiateViewControllerWithIdentifier:@"myDetailView"]; [tableView deselectRowAtIndexPath:indexPat
Recommends LAMBORGHINI · 2013-06 · Stack Overflow · on “Is having 22 segues to 1 Viewcontroller a bad thing when I use static and grouped cells?”
It depends on what you want. If you want to display certain data depending on which UITableViewCell was pressed, all you have to do is have a table view on view 1, on view two, have some blank UILabels (or whatever you would like to use to present the data), And load the data into the UI objects (UILabels, etc) depending on which cell was pressed. A very good tutorial of this is located here [this video] . This tutorial shows how to do this as well as saving the data, you might not need to save any data, so take away what you can about loading data into views from table view cells. Yes, what you are doing is kind of a bad practice, although it totally depends on what you want to do. HTH :)