I’m a Richardson, RU?

First of all, I found out the cat’s name was Captain Macintosh. Let me say it again so you don’t think I mistyped those 16 letters - Captain Macintosh. As I left the main facility last evening, I heard a "meow" and sure enough the Capt’n was waiting for me and provided an escort to the cabin. Lucky me … The good news is that I didn’t hear ANYTHING from the cat all night long. The bad news is that the level 10 storm rains made so much ruckus on the tin roof during the night, that I almost found myself wishing for the cat shuffling instead.

So I made it to day two, all the while struggling to maintain the structural consistency of "everything" that has been transfused into my cranium. Day 2 was just as intense. Of note, we went through Key Value Coding, handling the undo manager, bindings, responders and keyboard events, helper objects, and archiving (saving and re-loading data from files). To really finish the night off, we jumped into Core Data. I almost cried with excitement. Inside of 5 minutes I had built a model driven application, complete with undo manager access, archiving access, copy and paste, with all bindings and table mappings, and add/edit/delete functionality — all these things which had taken me tons of time to complete in previous exercises!

Nonetheless, I’d find out that (on day 3) for all Core Data is looking to be, there are some limitations. Namely, if you do anything to the MyDocument.xcdatamodel you can’t go back to manipulate any of the previous files in the application that existed before you made the changes. Also, it’s tough to deal with a rather intensive GUI. So, for tabular data based apps, it looks pretty good but it hasn’t really matured to the levels that it really becomes the de facto manner of development. All in all, I think it’s coming and I’m pretty exited about what it will be able to offer in the future.