On 11-May-09, at 6:21 AM, [email protected] wrote:
UITableViewController is mostly a convenience class that stubs the required protocol for UITableView when you create a new subclass using Xcode. It doesn't really matter what controller class you use if you implement the protocol and set the delegate and data source
Oh, there's other stuff that UITableViewController works out for you as well.
For starters, Apple will reject your application (at least, it rejected one of mine) if it doesn't disable an existing selection when shown. UITableView sorts that for you instead of having to check yourself.
Less trivially, if you want to edit some text in a cell at the bottom of the screen, UITableView will magically make the text field scroll up above the keyboard and put itself away afterwards. Sorting that out yourself to look good manually takes a bit of work.
And so forth. So it does behoove you to use it if appropriate. Now, if I could just get it to handle a background image nicely...
-- Alex Curylo -- [email protected] -- http://www.alexcurylo.com/ "When I met you, it was a little like meeting Jubal from _Stranger In A Strange Land_. I *think* that's a compliment..." -- Dominique _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
