Now that Codex is considered fully stable, it would be good to move over as much of the functionality within the Page Forms extension to use it as possible.
Here are the form input types that seem like they could be transferred to use Codex, along with their current implementation, and the Codex component they could use:
| Input type | Current implementation | Codex component |
|---|---|---|
| text | HTML | TextInput |
| textarea | HTML | TextArea |
| combobox | OOUI | Lookup |
| tokens | Select2 + SortableJS | ChipInput (+ SortableJS?) |
| radiobutton | HTML | Radio |
| dropdown | HTML | Select |
| checkboxes | OOUI | Checkbox |
| checkbox | OOUI | Checkbox |
| date | HTML | TextInput + Select |
| datetime | HTML | TextInput + Select |
| year | HTML | TextInput |
(Note that, for most of these input types, the "Current implementation" value should really have a "+ custom JavaScript" after it. Some of this custom JS can also be replaced by Codex, like the textarea input's autogrow handling.)
And here is a similar table for other form elements that could make use of Codex:
| Form element | Current implementation | Codex component |
|---|---|---|
| toggle (used in some helper forms) | OOUI | ToggleSwitch |
| form buttons | OOUI | Button |
| loading image | HTML | ProgressBar |
On the other hand, the following input types seem like they could not be converted, because there is not (currently) a Codex component for them:
- listbox
- tree
- datepicker, datetimepicker
- rating
- googlemaps, leaflet, openlayers
- regexp (not a true input type anyway)