Any initial clues as to how end user config will work?

I image that it will deal with stuff in the object store for the app, but how will users be able to set things? Will be it just be a string to be changed by the user, or will it allow things like a pull down list per key so the user can select the possible values? Maybe a check box for simple "on/off" settings? The ability to say that a number must be entered and not alphabetic characters?

No rush, but it might be useful info as people start planning for this feature.

Former Member over 10 years ago

Short answer:
Yes, Yes, Yes, Yes.

Long answer:
This feature has gone through a redesign since I did some work on it, so everything I know could be slightly inaccurate. However, I don't expect the features have been changed much.
Last I knew, the design had preference types of: display only (e.g. version number), lists, booleans, and form entry. The form entry types had a number of options including, but not limited to alpha, numeric, alpha/numeric, and date.

I don't have any new information regarding the release timeline for this feature.