Everybody is doing it these days. You have a UITableView that displays data and you want a way to tell the user to refresh it. Pulling down to refresh is the new paradigm, but it’s not exactly clear how to do that in iOS. That’s what this tutorial is all about. We’ll modify the Simple Task app we just finished, but you should easily be able apply this to any app.
Where we left off our app last time, we’d hooked up Core Data using a separate store object and had the ability to create new task objects. But we couldn’t rename or delete the tasks, and they weren’t being saved between application launches. Of course that’s not very useful, so we’ll rectify that in the final part of this tutorial.
Breaking into Core Data can be quite a pain when you’re first starting our with iOS development. The complexity from simple archiving can be quite a jump and difficult to get your head around. This tutorial will help to overcome that hurdle.
After my last post about the NSOutlineView, I thought I might take a little time to explain some of the concepts behind the way the Cocoa framework works. What was probably the most difficult concept for me to get my head around when working in PHP was the idea of design/programming patterns and in particular that model-view-controller (MVC) pattern.
Things have been a bit hectic at work lately and I couldn’t really devote as much time to programming as I would like. That said, I have managed to spend a bit of time taking a detour and learning a some game development.