I hope to create a custom view of the settings, similar to the settings application, but with more control over the user interface and access to some parameters (I need to block some settings).
Obviously, in every line of the UITableView application, there are many interface elements mixed in each line. For example, in the “Airplane Mode” setting, UISwitch is displayed, and the “Wi-Fi” parameter has a text value next to the disclosure symbol (“>”). A further complication of questions is the grouping of these settings.
I have some general questions about the approach I should take:
It seems I need to save the name of the parameter, its current value, its grouping and the type of UI elements (s) needed to change its value. I would like to use [NSUserDefault standardUserDefaults], but these settings are not displayed in the Settings app. I guess I will need to create my own persistence settings class.
Is it better to create each of these complex combinations of user interfaces in code, or to create a series of user views based on a UITableViewCell and load the corresponding data? I guess the latter.
some settings require me to load another view in order to select its value. Assuming the application is based on the Utility template, if the SettingsView manager controls the navigation stack rather than delegating the application?
.