Creating a settings page is quite easy, by means of creating the plist in the Settings.bundle. I have a need to create a similar type of view in my app, not exactly for settings information, but for some other information that I want the user to be able to specify in a similar UI to Settings pages. To get a view that looks like that in the Settings app it looks like what I would need to do is create a UITableView controller and then set up sections in the table view for each grouping of data, and then rows for the data etc. In other words, the Settings app appears to take the data in the plist table and then create a table view and controller, serializing the data in and out of storage for you.
Doing this by hand -- i.e., creating a table view controller and table view etc, and making it appear like a Settings page -- is actually straightforward enough, but before I plunge down that road I wanted to make sure there wasn't an easier way using plists or something a la the Settings approach. Keep in mind though that what is different here though is that I don't want the data straight into/out of the Settings database, instead I will need to have my code called as editing begins and ends in some of these fields and I will do my own saving in a different way.
So, am I right in that this calls for some table view controller coding, or is there an easier plist-based approach somehow?
Doing this by hand -- i.e., creating a table view controller and table view etc, and making it appear like a Settings page -- is actually straightforward enough, but before I plunge down that road I wanted to make sure there wasn't an easier way using plists or something a la the Settings approach. Keep in mind though that what is different here though is that I don't want the data straight into/out of the Settings database, instead I will need to have my code called as editing begins and ends in some of these fields and I will do my own saving in a different way.
So, am I right in that this calls for some table view controller coding, or is there an easier plist-based approach somehow?