Form controls
All KVision form controls are available in two variants. The first variant, with class name ending with "Input" (e.g. TextInput
), is a basic, fully-functional component ready to be used as a standalone widget. The second variant, with class name without "Input" (e.g. Text
), is a wrapper component implementing one of FormControl
interfaces and is intended primarily for use with a FormPanel
container. This variant can display a label, a validation information and has some additional CSS styling consistent with Bootstrap forms components. From the developer point of view both variants have the same properties and methods (a side of label
and rich
properties available for second variant only).
The following reference do not differentiate both variants of form controls.
All KVision form controls have the following properties:
value
- allows to get or set the value of the componentname
- defines aname
attribute of the HTML input elementsize
- allows to set the size of the form control (normal, large or small Bootstrap style)disabled
- defines whether the form control is disabled
Text fields
i.k.f.text.Text
i.k.f.text.Text
This component is rendered as a standard HTML text field and is used to get simple, textual data from the user. The type
property can be set to any of these values: TEXT
, PASSWORD
, EMAIL
, TEL
, COLOR
, SEARCH
, URL
and is bound to the type
attribute of the HTML input field. Modern browsers can render such fields with additional elements (e.g. color chooser). Other properties allow you to define a placeholder, a maximum length, autofocus or autocomplete attributes and define if the control should be read-only.
With an additional kvision-imask
module loaded and initialized you can use all text input mask options supported by Imask.js library.
i.k.f.text.Password
i.k.f.text.Password
This component is a direct subclass of i.k.form.text.Text
with type
property set to TextInputType.PASSWORD
.
i.k.f.text.TextArea
i.k.f.text.TextArea
This component is rendered as a standard HTML textarea field and is used to get longer, multi-line textual data from the user. It can be sized with cols
and rows
properties (mapped to standard HTML attributes).
Alternative way (and preferred nowadays) is to set CSS width
and height
properties.
Other properties allow you to define a placeholder, a maximum length, autofocus or hard wrap attributes and define if the control should be read-only.
i.k.f.text.RichText
i.k.f.text.RichText
The kvision-richtext module allows you to use a dedicated form control based on a modern Trix Editor component. It can be used to get rich text from the user. This component renders a text editing field with a toolbar containing basic formatting options (bold, italic, strikethrough, heading, quote, code, link and lists with indentations). The value
property contains properly formatted HTML markup. Other properties allow you to define a placeholder and autofocus attribute.
i.k.f.text.TomTypeahead
i.k.f.text.TomTypeahead
The kvision-tom-select module contains an enhanced text field with support for typeahead (autocomplete) functionality. Both local and remote data sources are supported. To use local data source pass a list of values with the options
parameter.
To use a remote data source pass a TomSelectCallbacks
object with a load
callback.
i.k.f.text.TomTypeaheadRemote
i.k.f.text.TomTypeaheadRemote
This component is contained in the kvision-tom-select-remote
module and is a special version of the Typeahead
control, tailored for use with KVision server side interfaces. You can find more information in part 3 of this guide.
Checkboxes and radiobuttons
i.k.f.check.CheckBox
i.k.f.check.CheckBox
This component can be used to display a checkbox and to get true/false data from the user. The style
property can be used to render the checkbox with one of six different styles.
You can layout your checkboxes horizontally using an inline
property.
And you can even make the checkbox look like a radiobutton.
A CheckBox
component has a convenient onClick
method to easily bind some action to the click
event.
By using indeterminate
property you can make the checkbox appear as neither selected nor deselected.
i.k.f.check.Radio
i.k.f.check.Radio
This component is similar to the CheckBox
component, but it is rendered as a radiobutton. By using the name
property, you can group some radiobuttons together, with only one control selected at a time.
The style
property can be used to render the radiobutton with one of six different styles.
You can layout your radiobuttons horizontally using an inline
property.
And you can even make the radiobutton look like a checkbox.
A Radio
component has a convenient onClick
method to easily bind some action to the click
event.
i.k.f.check.RadioGroup
i.k.f.check.RadioGroup
Although it is possible to use basic Radio
components to build and manage radiobutton groups (you would have to check which radio in a group is selected), KVision offers a dedicated RadioGroup
component, which allows you to treat a group of radiobuttons as a single component returning a String value. It can be initialized with a list of options (key to value pairs) and the selected option can be easily set or get with the value
property.
i.k.f.check.TriStateCheckBox
i.k.f.check.TriStateCheckBox
This component extends the usage of indeterminate
property of the standard CheckBox
component and allows you to easily use all three states of the checkbox - selected (value = true)
, deselected (value = false)
and indeterminate (value = null)
.
Select boxes
i.k.f.select.Select
i.k.f.select.Select
This is a simple select box component, based on standard HTML select control. It can be used when there is no need for advanced options of the Select
component. The SimpleSelect
component should be initialized with a list of options (key to values pairs).
i.k.f.select.TomSelect
i.k.f.select.TomSelect
The kvision-tom-select
module allows you to use a sophisticated form control based on Tom Select. It's a full-featured component, configurable with plenty of options. It can be used for a simple select picker with a few static options as well as a searchable, dynamic lists pulled over the network. The TomSelect
component can be initialized with a list of options (key to values pairs).
You can select many options at the same time with multiple
property. You can use tsOptions
parameter to provide additional options (e.g. limit the number of selected items). See TomSelect documentation for detailed information about available options.
Other properties allow to define a placeholder, an autofocus attribute and to automatically generate an empty option (to be able to de-select value).
TomSelect
component can also work with a remote data source - just pass a TomSelectCallbacks
object with a load
callback
i.k.f.select.TomSelectRemote
i.k.f.select.TomSelectRemote
This component is contained in the kvision-tom-select-remote
module and is a special version of TomSelect
control, tailored for use with KVision server side interfaces. You can find more information in part 3 of this guide.
Numeric
i.k.f.number.Spinner
i.k.f.number.Spinner
This is a simple integer field component, based on standard HTML input control. You can set min
and max
values (default - no limits) and set the step
value (default 1).
i.k.f.number.Range
i.k.f.number.Range
This component can be used to allow a user to select numeric value with a slider. You need to configure min
(default 0), max
(default 100) and step
(default 1) attributes.
Note: the actual appearance of the control may depend on your browser.
i.k.f.number.Numeric
i.k.f.number.Numeric
This component can be used for fixed precision decimal numbers (e.g. currency). You need do set a number of decimal digits (default 2) and the component will automatically format the number. You can set min
and max
values (default - no limits). You can also specify a decimal digit character or just use the auto-detected default.
i.k.f.number.ImaskNumeric
i.k.f.number.ImaskNumeric
With kvision-imask
module you can use the advanced numeric component, which allows you to work with all decimal numbers (with or without fixed number of decimal digits) and fully controls the characters entered by the user. By setting decimals
property to a larger value (up to 15) you can support inputs with different number of decimal digits.
If you want to support fixed decimals, set padFractionalZeros = true
- the component will automatically format the number.
You can also use decimals and thousands separator chars (both are automatically detected from the current locale).
Note: All numeric components are based on JavaScript Number
type, which is double-precision 64-bit binary format IEEE 754. The range and precision of represented numbers is limited. To prevent rounding errors KVision limits the range of supported numbers to about 14 digits.
Others
i.k.f.time.DateTime
i.k.f.time.DateTime
Both kvision-datetime
module allows you to use a sophisticated form control based on Tempus-dominus library. Is It's a full-featured component, configurable with plenty of options. It can be used to display date and/or time picker, based on the date format specified with Fecha library formatting tokens. The default format is "YYYY-MM-DD HH:mm", which means the control will display date and time picker.
Other properties allow you to set days of the week that should be disabled, visibility of "Clear", "Close" and "Today" buttons and also the increment used to build the hour view (default - 5 minutes).
You can also use minDate
, maxDate
, enabledDates
and disabledDates
properties to control which dates the user is allowed to choose.
i.k.f.upload.BootstrapUpload
i.k.f.upload.BootstrapUpload
The kvision-bootstrap-upload module allows you to use a form component based on Bootstrap fileinput, which allows the user to select and upload files. It can be used as a standard file input element, with files being sent as a multi-part form submission or as an AJAX submission and it can be also used as a client-side file selection tool to be used with FileReader API available in modern browsers. The Upload
component has a lot of options to customize its appearance and functionality - see API documentation for more details.
Standard HTML form submission
You can use the Upload
component to upload files to the server with standard multi-part form action. You should create the FormPanel
container with additional parameters (FormMethod.POST
, FormEnctype.MULTIPART
). In this mode you will be able to upload only one file at a time (unless you add more Upload
controls). You should also add a button with type SUBMIT
.
AJAX upload
To use this mode you have to create a server endpoint responsible for processing an AJAX request and returning the correctly formatted response (at least an empty JSON object {}). More information can be found on this Bootstrap fileinput page. On the client side you can use all available options including multiple file uploads. There is no need to add any form parameters or submit buttons.
In this mode you have to handle your uploaded files and the rest of your form data separately. Alternatively you can use uploadExtraData
property and add your form data directly to your AJAX request.
Client side file handling
Modern browsers support FileReader API and allow you to work with files entirely on the client side. The FormPanel<K>
class has a suspending getDataWithFileContent
extension function, which is using Kotlin coroutines to read the content of all uploaded files as BASE64 dataURL strings. It makes it very easy to use such content in other KVision components (e.g. images or any HTML formatted text).
Note: You need to set uploadUrl
parameter (e.g. to "/" value), even though it's not directly used in this mode.
Last updated