Jeez, you guys are making this complicated.
The above images are used as a base.
Like CF you have settings which are text based, you make the image a button command, clicking this brings up the OSK to type in a value, or if there is something more exotic required like a browser then that will need to be coded by the plugin writer.
At the bottom you have numeric values which can be increased or decreased.
On the right you can set up boolean options using the true or false indicators.
It will be up to the skinner to do the graphics for their skin
The carwings is already done so aplugin writer as normal does their plugin, does a settings.skin for it (all they have to do is copy one that is done and change the button codes).
Settings2.skin can be added or settings3 if necessary.
A button can be added the the plugin mgr screen that selects the highlighted plugin and loads a <pluginname>.skin file.
This is what I am using in my iDrive skins and what my plugins will support.
The settings for nay plugin can all be called from one place, the plugin manager.
The skin images only have to created once.
And just a _settings.skin file has to be copied.