2016-06-06, 06:23 AM
At the moment we have the current setting field (aka. optionscode) supported:
I could reproduce implement a date and time option using the select but it wouldn't feel well with day, month, year, hour, minutes, seconds 1 per row as it would require that to make it.
It would simplify things for us and it could be saved with proper field types to SQL which saves a lot of time in the later for MySQL queries and the sort and also simplifies it at creating plugins.
- text : A regular text box
- numeric : A numeric field
- textarea : A larger text box
- yesno : A boolean yes/no control
- onoff : A boolean on/off control
- select : A select box (in the format select followed by = with one per newline)
- forumselect : A built-in radio + select box to select forums
- forumselectsingle : A built-in select box to select only one forum
- groupselect : A built-in radio + select box to select groups
- groupselectsingle : A built-in select box to to select only one user group
- radio : A set of radio buttons (in the format select followed by = with one per newline)
- checkbox : A boolean checkbox field
- language : A language selection box
- adminlanguage : An ACP language select
- cpstyle : A theme selector
- php : A php code
- Date
- Date and Time
- monetary (a double type field for currency like values, in MySQL it would be something like double 9.2 for example, separated by a dot)
I could reproduce implement a date and time option using the select but it wouldn't feel well with day, month, year, hour, minutes, seconds 1 per row as it would require that to make it.
It would simplify things for us and it could be saved with proper field types to SQL which saves a lot of time in the later for MySQL queries and the sort and also simplifies it at creating plugins.