I started playing with various fields, and have found that sometimes it is useful to have additional field types:
textarea - for large text content, like description, tagline, title, data-uri encoded image, svg etc. In conjunction with autosize it is even better than usual type='text'. As an option - replace default text input with textarea and autosize. API won’t change, for the end user there will be no difference, but UX will be smoother.
radio - an alternative for select. It may work better for small sets, as it shows all possible options at once, which makes interaction easier and faster.
custom - renders custom user HTML. That could be dividers, section titles, custom inputs, like vecN inputs, unit inputs (number + unit select), reset button, file input etc. It is quite easy to implement, and covers the rest of possible use-cases. Also that allows for extending control-panel with additional fields from other packages.
dy
commented
8 years ago
Hi!
I started playing with various fields, and have found that sometimes it is useful to have additional field types:
textarea- for large text content, like description, tagline, title, data-uri encoded image, svg etc. In conjunction with autosize it is even better than usualtype='text'. As an option - replace defaulttextinput with textarea and autosize. API won’t change, for the end user there will be no difference, but UX will be smoother.radio- an alternative forselect. It may work better for small sets, as it shows all possible options at once, which makes interaction easier and faster.custom- renders custom user HTML. That could be dividers, section titles, custom inputs, likevecNinputs, unit inputs (number + unit select),resetbutton,fileinput etc. It is quite easy to implement, and covers the rest of possible use-cases. Also that allows for extending control-panel with additional fields from other packages.Any thoughts?