The whole configuration form practice used in goe_sass_admin() is a hack. There are number of plugins that do that, but as a fair warning; that should be considered as a hack and it may break in the future.
In Textpattern 4.6.0 the preference panel will be remodeled and that will at least partially stop working. It will not save the preferences.
Anyways, there are few ways to represent preference fields in Textpattern admin-side:
By adding them to the native Preferences panel.
...or by completely doing your own panel and saving system using the widget library.
The former is easier and requires no more than registering the configuration fields. Additionally you can add extra event and input handlers too. Creating a new preference field to the Preferences panel doesn't take much. E.g.
Where the above creates a new preferences group with four options in it. The add_privs() grants permissions to the said group (permissions are checked starting from 4.6.0). The labels (translations) are picked on from the plugin's Textpack file.
The whole configuration form practice used in goe_sass_admin() is a hack. There are number of plugins that do that, but as a fair warning; that should be considered as a hack and it may break in the future.
In Textpattern 4.6.0 the preference panel will be remodeled and that will at least partially stop working. It will not save the preferences.
Anyways, there are few ways to represent preference fields in Textpattern admin-side:
The former is easier and requires no more than registering the configuration fields. Additionally you can add extra event and input handlers too. Creating a new preference field to the Preferences panel doesn't take much. E.g.
Where the above creates a new preferences group with four options in it. The add_privs() grants permissions to the said group (permissions are checked starting from 4.6.0). The labels (translations) are picked on from the plugin's Textpack file.