Im looking through Presence3, understand the LetsMakeAThread project, its pretty straight forward, detachNewThread creates a separate thread and performSelectorOnMainThread returns you to the MT, but in ThreadedFlickrTableView, whats the deal?
beginLoadingFlickrData calls a new invocation operation, which loads synchronousLoadFlickrData: which gets the data from Flickr and returns to MT via didFinishLoadingFlickrDataWithResults: which in turn creates the arrays from the FlickrData.
Then cachedImageForURL gets called from the cellForRowAtIndexPath? And so that same method calls the ImageLoadingOperation which then returns to the main thread via didFinishLoadingImageWithResult:?
Is this chronology correct? The MT gets separated or stopped 2x in this app? Once in beginLoadingFlickrData and then in cachedImageForURL? The difference being that in the former, it gets called out as simply a new method within the same file whereas in the latter it gets called as a completely new class file? I guess they did it to exemplify both cases?
Im working my way thru Lecture 9. Recapping what ive done, i created 2 Preence2 projects; first i pass data using the custom initWithpassedData: method which didnt let me use the initWithStyle for the tweets table view, and second I used the appDelegate pattern which i dont like cause its really a global variable.
So Im looking into KVOs and NSNotifications but they look kinda scary!
I started using plists for a couple of projects, found out they can be further structured to no just a simple array or a dictionary with keys and objects, but also kind of a flat db with parents and childs. Ill try using plists and later migrate to SQLite which is easier given my programing background. I also started writing to disk so i hope i can add that functionality to my projects so i can write those plists or db files on the iphone. Otherwise ill have to use an online account-structured storage to have my users log in online on a comfortable desktop interface and have the iphone get the data from the web and write it to the iphone for certain apps where i want end-user modifiable code.
Picked up cell.detailText.text and started on CoreLocation because I’m learning from Stanford and iPhone Auditors Google Dev Group as well as research on web.
I’m using this blog as an unorganized way of recording progress so it may be sketchy.
From looking at the MyTabBar app from Lecture 7 you can see that ViewControllers can be created with IB or programatically, like many other things in Xcode/IB. The important thing is that in IB its not flexible; the way i see it if you create it in IB youre pretty much stuck with the design but in Xcode you can add things based on variables you get from the user or a data source. EXAMPLE:
1. I went thru a tutorial from LittleComputers.net where we created a tabBarController with 2 tabs and later on added a NavigationController to one of the tabs. Basically i dragged a tabcontroller from the IB Library (default of 2 tabs) and a navController. I then had to create the view controller class files manually with their xibs and connect the xibs to the respective class files. But thats it, once theyre setup, i couldnt add more xib files.
2. With lecture 7, looking at the MyTabBar app i can see how easily to create a view programatically and that gives you the flexibility to create more views based on user response or dynamic data sources.