Do you really mean two table view controllers...or two table views?
That’s a really important question. Depending on how your data is structured, it might make more sense to have two separate table view controllers and embed them within your overall view controller.
Alternatively, if the data is tightly coupled than having one view controller managing two table views might make sense. If you do that then I recommend that you avoid the “test which table view you’re dealing with” approach on each delegate / data source callback, but instead have helper objects that take care of that and then wire those helpers up in code. Your helpers can then expose a nicer delegate interface back to your view controller.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"
WWDC runs Mon, 5 Jun through to Fri, 9 Jun. During that time all of DTS will be at the conference, helping folks out face-to-face. http://developer.apple.com/wwdc/