* Cheking the database *
- Get a context - Create an entity - Create a predicate - Create a request - Set up the entity and predicate in the request - Execute the request
So, at this point I would have an array of ManagedObjects with the attributes according to the predicate
* Insert new data * (no duplication check) - Get a context - Create a ManagedObject based in entity - Set attributes for ManagedObject - Save
http://developer.apple.com/macosx/coredata.html http://cocoadevcentral.com/articles/000086.php#2 http://developer.apple.com/IPhone/library/documentation/DataManagement/Conceptual/iPhoneCoreData01/Articles/01_StartingOut.html#//apple_ref/doc/uid/TP40008305-CH105-SW1
The New Project assistant has consolidated the templates for similar project types. For example, there is now a single Cocoa Application template, and you choose Document-based and/or Core Data-based variants with checkboxe
Alright, after a good bit of time, I have made some good progress. I now fully understand the way view controllers work. I am up to lecture 9 in the Stanford series. I finished Paparazzi 1 and feel pretty good about it. Here are some notes from Lecture 7 that will definitely be helpful later on:
Lecture 7 - Spring 2010 17 minutes - Code for pushViewController and pop @ 18 Don't use Application Delegate to hold “data” You should pass the data as input parameters and then use protocols. Set first view controller as the next ones delegate. That way the second one lets the first one know about changes that are made! At 37 , he goes through passing data and changing labels on views. Want to store stuff off of view because views load lazily. Set a NSString to hold data and then, under viewDidLoad, change the label to whatever that NSString is. textLabel.text = label; (38:48) Then under pushViewController on first controller, where you change the title of the next, also change the NSString. Look at sample code to see how delegation works between views. Every view controller has a navigation item for customizing; displayed when view is on top of stack. [View Controller → Navigation Item → Left Bar Button Item, Title View, Right Bar Button Item] At 45 - Text Bar Button Item - code to handle top left button on navigation menu At 50 - Shortening the name shown in back button. Tab Bar Controller - Little Controller buttons on bottom Code for Tab Bar Controller at 1 hour 1:07 - How to nest Navigation Controllers Code
I tried just keeping track of where important code snippets were displayed and explained.
Here is a screenshot of the new xcode and my paparazzi project in it:
And here is a screenshot of my paparazzi project:
The important thing to notice are that I use various navigation controllers.
Lecture 8 was all about using table views and slide views. And lecture 9 deals with data. I am excited to go ahead and jump into the use of data to start to work on making a “real” application and not just a lousy static one!
Things to remember: Sewanee iPhone App?
A new semester has arrived! And with is, a new set of videos and projects from the Stanford iPhone class. This past week I started to pick up where I left off. Which was somewhere around the beginning of Assignment 4. It looks as though everything has stayed pretty much the same for the first three assignments. They name of Assignment 4 has changed and I think a few of the details have been changed. When I stopped working on this assignment last semester I was a bit lost on the whole Views concept. However, this week I re-watched the last lecture, and then watched the next lecture and a half. I am beginning to get the hang of how views work. I think I understand it conceptually and am [ ] that close to implementing it correctly. Two things I wanted to note were: 1. Around the one hour mark of Lecture 6 for 2009 is where Evan gives examples of how to implement your Views and ViewControllers. 2. The entirety of lecture seven describes how to “gather” many ViewControllers and use Apple produced code to put them together.