v3.13 – outdated
This version of the documentation is outdated. Consider upgrading your project to Spiral Framework 3.14
Keeper — Components
DataGrids
UI component for DataGrids provides UI component for DataGrids
They are located in the keeper bundle, that can be included like so:
xhtml
<use:bundle path="keeper:bundle"/>
See Usage Samples in the demo repository
Using Component
A simple data grid declaration would look like so:
xhtml
<ui:grid url="@action('users.list', inject('params', []))" namespace="main">
<grid:cell.text name="id" label="#"/>
<grid:cell.text name="firstName" label="First Name"/>
<grid:cell.text name="lastName" label="Last Name"/>
</ui:grid>
DataGrids are described in a declarative way. The code is not iterated in php/stempler phase, but later in the JavaScript phase, meaning you can't use php conditions for cell renders inside declarations. If you need a conditional renderer for cell, you are expected to write one in JavaScript.
Columns should be defined prioritizing semantics over column names. Typically most columns would match a sort key. For
example, if you have a data row with the first and the last name and a user, you might want to have a column name with firstName
and lastName joined.
xhtml
<grid:cell.link name="name" label="Name" url="@action('users.edit', ['user' => '{id}'])" sort="true">
{firstName} {lastName}
</grid:cell.link>
Wrapper (ui:grid)
xhtml
<ui:grid
url="/some/url"
method="GET"
id="my-grid"
namespace="foo"
capture-forms="['form1','form2']"
capture-filters="['filter1','filter2']"
paginate-options="[10,20,30]"
actions-title=""
actions-label="Actions"
actions-kind=""
actions-icon="cog"
actions-size="sm"
actions-class=""
actions-cell-class="">
</ui:grid>
| Parameter | Required | Default | Description |
|---|---|---|---|
| url | yes | - | Url that implements DataGrid API |
| method | no | GET | Http method to use, GET or POST |
| id | no | [auto generated] | Id of datagrid to use |
| namespace | no | [empty] | A prefix for field names that is used in the datagrid filters serialization. It's used when multiple datagrids are present on page. I.e. if namespace="foo" filter value bar=1 will end up as "foo-bar=1" in URL. It's developer's responsibility to use namespaces if multiple datagrids are present on page. Otherwise the behavior is unpredictable |
| capture-forms | no | [empty] | JSON array of strings. It attaches forms by their ids to datagrid as a filter fields source. It can be used for filters that are visually separated from datagrids, i.e. in the nav panel or sidebar. It's used internally to attach the filter defined with <ui:filter> |
| capture-filters | no | [empty] | JSON array of strings. It attaches the instances of filter toggle buttons |
| paginate-options | no | [empty] | JSON array of numbers. It options for the default paginator |
| action-* | no | [as in sample] | A set of parameters that is used to generate the Actions button and the corresponding column |
Limitation: All the filter forms should produce a flat object map without files. Nesting and/or arrays are not supported at the moment.
Filters (grid:filter)
Grid:filter component attaches the filter and/or search forms directly to the grid. Internally it works with the 'capture-forms' parameter that technically allows to attach any number of forms to the datagrid.
xhtml
<ui:grid url="@action('users.list', inject('params', []))" namespace="main">
<grid:filter search="true" immediate="300" buttons="true">
<form:input name="firstName" label="First Name" value="" size="6" required="true"/>
<form:input name="lastName" label="Last Name" value="" size="6" required="true"/>
<form:input name="email" label="Email" value="" required="true"/>
</grid:filter>
</ui:grid>
| Parameter | Required | Default | Description |
|---|---|---|---|
| search | no | false | Renders a search input in the top right corner |
| search-name | no | "search" | The name of the search field |
| fields | no | - | JSON array of strings. If you want the filter button to indicate the number of active filters correctly, list all the form fields names as a JSON array of strings. For the example above that would be fields="['firstName','lastName','email']". If it's not specified, the filter button does not indicate if the filter values are active or not |
| refresh | no | false | Renders a refresh button to trigger data refresh |
| immediate | no | - | If it's specified, the search input will have no "Submit" button and the search will be performed as user types with the debounce value equivalent to this param value in milliseconds. |
| [tag body] | no | - | Insides of tag are used as an additional filter form shown in the modal window if it's specified |
| buttons | no | false | If they're specified as true, the default "Clear" and "Apply" buttons will append to the tag body |
Note, the filter form is a separate form to the "search input" form and its reset button has effect only on the filter form.
Only Search
xhtml
<ui:grid url="@action('users.list', inject('params', []))" namespace="main">
<grid:filter search="true"/>
</ui:grid>
Search And Modal
xhtml
<ui:grid url="@action('users.list', inject('params', []))" namespace="main">
<grid:filter search="true" immediate="300" buttons="true">
<form:input name="firstName" label="First Name" value="" size="6" required="true"/>
<form:input name="lastName" label="Last Name" value="" size="6" required="true"/>
<form:input name="email" label="Email" value="" required="true"/>
</grid:filter>
</ui:grid>
Cell Types
Lots of cells allow to use templates using row fields as variables.
The used template system is handlebars templates. Typically field accepting templates have
pre-processors that convert { to {{, so if you want to output something like {{firstName}} {{lastName}}, you pass
it in as {firstName} {lastName}
Text (grid:text)
xhtml
<grid:cell.text
name="user"
label="User Name"
/>
Directly outputs a field in a cell
| Parameter | Required | Default | Description |
|---|---|---|---|
| name | yes | - | A semantic column name which is matching the field from the server data |
| label | yes | - | A column label |
| sort | no | - | Enables sorting for a column |
| sort-default | no | - | Supply "true" to make this column a defaultly sorted column. Only one column should have this |
| sort-dir | no | 'asc' | A default sort direction, 'asc' or 'desc' |
Link (grid:link)
xhtml
<grid:cell.link
name="user"
title="Edit User {firstName}"
body="{fistName}"
href="/edit/{id}"
/>
Outputs a link
| Parameter | Required | Default | Description |
|---|---|---|---|
| name | yes | - | A semantic column name which is matching the field from the server data. It should match the sorter name if the sort is used. Content is the field itself as default, but it can be customized with the 'body' parameter to output another field |
| label | yes | - | A column label |
| href | yes | - | A template to use for the link url |
| title | no | - | A template to use for the link title text |
| body | no | - | A template to use for the link body. Instead of specifying the 'body' attribute, it possible to use the tag body |
| sort | no | - | Enables sorting for a column |
| sort-default | no | - | Supply "true" to make this column a defaultly sorted column. Only one column should have this |
| sort-dir | no | 'asc' | A default sort direction, 'asc' or 'desc' |
Date (grid:date)
xhtml
<grid:cell.link
name="created"
label="Created At"
format="LLL dd, yyyy HH:mm"
sort="true"
sort-dir="desc"
sort-default="true"
/>
Outputs a date
| Parameter | Required | Default | Description |
|---|---|---|---|
| name | yes | - | A semantic column name which is matching the field from the server data. It accepts ISO dates with a timezone. |
| label | yes | - | A column label |
| format | no | LLL dd, yyyy HH:mm | A date format. See Luxon docs for available tokens |
| sort | no | - | Enables sorting for a column |
| sort-default | no | - | Supply "true" to make this column a defaultly sorted column. Only one column should have this. |
| sort-dir | no | 'asc' | A default sort direction, 'asc' or 'desc' |
Actions
A separate kind of tags that are provided are action tags. Using any of them adds the 'actions' column with a button with a drwondown list of actions. Each action's tag appends an action to that dropdown.
To customize the look of the button, use action-* parameters of ui:grid
Actions: Link
xhtml
<grid:action.link
href="edit/{id}"
template="{id}"
label="Edit"
title="Edit {firstName}"
icon="edit"
target="_blank"
/>
Outputs a link
| Parameter | Required | Default | Description |
|---|---|---|---|
| href | yes | - | A template to use for link url |
| title | no | - | A template to use for the link title text |
| target | no | _self | Specifies the target of the link |
| template | no | - | A template to use for the link body. Instead of specifying the 'template' attribute, the tag body can be used |
| label | no | - | Text to use for the link text if the template param is not used. It supports templates if it's passed as unescaped value, i.e. label = "{!! '{{variable}}' !!}" |
| icon | no | - | A name to use for the link icon if the template param is not used. It uses Font Awesome icons. It supports templates if it's passed as unescaped value, i.e. icon = "{!! '{{variable}}' !!}" |
Actions: Action
xhtml
<grid:action.action
href="edit/{id}"
template="{id}"
label="Edit"
title="Edit {firstName}"
icon="edit"
method="POST"
data="{ foo: 1}"
refresh="true"
confirm="true"
confirm-title="true"
confirm-ok="true"
confirm-cancel="true"
/>
Makes a request to server
| Parameter | Required | Default | Description |
|---|---|---|---|
| href | yes | - | A template to use for action url |
| method | no | GET | A method name to use |
| title | no | - | A template to use for the action title text |
| template | no | - | A template to use for the link body. Instead of specifying the 'template' attribute, it's possible to use the tag body |
| label | no | - | Text to use for the link text if the template param is not used. It supports templates if it's passed as unescaped value, i.e. label = "{!! '{{variable}}' !!}" |
| icon | no | - | A name to use for the link icon if the template param is not used. It uses Font Awesome icons. It supports templates if it's passed as unescaped value, i.e. icon = "{!! '{{variable}}' !!}" |
| body | no | - | JSON String to attach as a request body. It supports templates if it's passed as unescaped value, i.e. data = "{!! '{ "id": {{variable}} }' !!}" |
| refresh | no | - | A boolean value which is indicating if a success response from the server should trigger a datagrid refresh |
| condition | no | - | A field name that contains boolean variable indicating if that action should be shown. Alternatively there could be a handlebars template that should return '' for a false value or anything else for a positive value in case more complex logic is needed |
| toastError | no | - | A template for the toast message to show on an action error |
| toastSuccess | no | - | A template for the toast message to show on an action success |
| confirm | no | - | If it's specified, specify confirm-title, confirm-ok and confirm-cancel. It will show a confirm dialog before executing an action. confirm specifies handlebars template for confirm dialog body |
| confirm-title | no | - | Specifies the handlebars template for the confirm dialog title |
| confirm-ok | no | - | Specifies the handlebars template for the confirmation dialog of the positive result button text |
| confirm-cancel | no | - | Specifies the handlebars template for the confirmation dialog of the negative result button text |
Actions: Delete
xhtml
<grid:action.delete
href="edit/{id}"
/>
It's the same as 'grid:action' but with predefined confirmation texts and a danger class. Typically only href is
needed for that action type.
Template (grid:template)
xhtml
<grid:cell.template
name="user"
label="User Name"
body="<i class='fa fa-user'></i> {firstName} {lastName}"
/>
Outputs custom template
| Parameter | Required | Default | Description |
|---|---|---|---|
| name | yes | - | A semantic column name which is matching the field from the server data. It should match the sorter name if the sort is used. The content is the field itself as default, but it can be customized with the 'body' parameter to output another field |
| label | yes | - | A column label |
| body | no | - | A template to use for the body. Instead of specifying the 'body' attribute, it's possible to use the tag body |
| sort | no | - | Enables sorting for a column |
| sort-default | no | - | Supply "true" to make this column a defaultly sorted column. Only one column should have this |
| sort-dir | no | 'asc' | A default sort direction, 'asc' or 'desc' |
Fully Custom Render (grid:render)
xhtml
<grid:cell.render
name="roles"
label="Roles"
renderer="roles"
/>
It uses a custom function to render the cell
| Parameter | Required | Default | Description |
|---|---|---|---|
| name | yes | - | A Semantic column name matching the field from server the data. It should match the sorter name if the sort is used. The content is the field itself as default, but it can be customized with the 'renderer' parameter to output another field |
| label | yes | - | A column label |
| renderer | no | - | A Name of a pre-registered function that is able to render a cell |
| sort | no | - | Enables sorting for a column |
| sort-default | no | - | Supply "true" to make this column a defaultly sorted column. Only one column should have this |
| sort-dir | no | 'asc' | A default sort direction, 'asc' or 'desc' |
To define a custom function for the datagrid, add a script tag before the toolkit declarations. If you see 'renderer not found' error, most likely you've outputted the renderer too late in the code.
xhtml
<stack:push name="scripts" unique-id="datagrid-roles-renderer">
<script type="text/javascript">
window.SFToolkit_tools_datagrid = window.SFToolkit_tools_datagrid || {};
window.SFToolkit_tools_datagrid['roles'] = function () {
return function (roles) {
return roles.map(function (role) {
return '<span class="badge badge-primary mr-1">' + role.toUpperCase() + '</span>'
}).join('');
}
};
</script>
</stack:push>
The function returned by the render function should be CellRenderFunction and it accepts a lot of useful params allowing to customize the render in a really flexible way.
Advanced Usage
DataGrid is based on the JavaScript library and can be initialized with JavaScript
The JavaScript declaration allows for more flexibility, i.e. you can have multiple actions columns, batch actions and selections, custom renderers directly in the code without the need to pre-define them.
See DataGrid Source Code for more details.
xhtml
<div class="sf-table">
<div class="js-sf-datagrid">
@declare(syntax=off)
<script type="text/javascript" role="sf-options">
(function () {
return {
"id": "custom",
"url": "/keeper/users/list",
"namespace": "custom",
"method": "GET",
"ui": {
"headerCellClassName": {"actions": "text-right"},
"cellClassName": {"actions": "text-right py-2", "created": "text-nowrap"}
},
"paginator": {"limitOptions": [10, 20, 50, 100]},
"sort": "created",
"columns": [{"id": "name", "title": "Name", "sortDir": "asc"}, {"id": "actions2", "title": " "}, {
"id": "email",
"title": "Email",
"sortDir": "asc"
}, {"id": "created", "title": "Created At", "sortDir": "desc"}, {
"id": "roles",
"title": "Roles",
"sortDir": null
}, {"id": "id", "title": "ID", "sortDir": null}, {"id": "actions", "title": " "}],
"selectable": {
"type": "multiple",
"id": "id"
},
"renderers": {
"cells": {
"name": {
"name": "link",
"arguments": {
"title": "",
"body": "{{firstName}} {{lastName}}",
"href": "\/keeper\/users\/{{id}}"
}
},
"email": {
"name": "link",
"arguments": {"title": "", "body": "{{email}}", "href": "mailto:{{email}}"}
},
"created": {"name": "dateFormat", "arguments": ["LLL dd, yyyy HH:mm"]},
"roles": {"name": "roles", "arguments": []},
"id": {"name": "template", "arguments": ["{{id}}"]},
"actions": {
"name": "actions",
"arguments": {
"kind": "",
"size": "sm",
"className": "",
"icon": "cog",
"label": "Actions",
"actions": [{
"type": "href",
"url": "\/keeper\/users\/{{id}}",
"label": "Edit",
"target": null,
"icon": "edit",
"template": ""
}, {
"type": "action",
"url": "\/keeper\/users\/{{id}}",
"method": "DELETE",
"label": "Delete",
"icon": "trash",
"template": "<span class=\"text-danger\"><i class=\"fa fw fa-trash\"><\/i> Delete<\/span>",
"condition": null,
"data": [],
"refresh": true,
"confirm": {
"body": "Are you sure to delete this entry?",
"title": "Confirmation Required",
"confirm": "Delete",
"confirmKind": "danger",
"cancel": "Cancel"
},
"toastSuccess": "<i class=\"fa fa-check-circle\"><\/i> {{message}}\n ",
"toastError": "<i class=\"fa fa-exclamation\"><\/i> {{error}}\n "
}]
}
},
"actions2": {
"name": "actions",
"arguments": {
"kind": "",
"size": "sm",
"className": "",
"icon": "cog",
"label": "Actions 2",
"actions": [{
"type": "href",
"url": "\/keeper\/users\/{{id}}",
"label": "Edit",
"target": null,
"icon": "edit",
"template": ""
}, {
"type": "action",
"url": "\/keeper\/users\/{{id}}",
"method": "DELETE",
"label": "Delete",
"icon": "trash",
"template": "<span class=\"text-danger\"><i class=\"fa fw fa-trash\"><\/i> Delete<\/span>",
"condition": null,
"data": [],
"refresh": true,
"confirm": {
"body": "Are you sure to delete this entry?",
"title": "Confirmation Required",
"confirm": "Delete",
"confirmKind": "danger",
"cancel": "Cancel"
},
"toastSuccess": "<i class=\"fa fa-check-circle\"><\/i> {{message}}\n ",
"toastError": "<i class=\"fa fa-exclamation\"><\/i> {{error}}\n "
}]
}
}
},
"actions": {
"delete": {
renderAs: "<div class='btn btn-danger'>Delete</div>",
onClick: function (state, grid) {
console.log(state, grid);
}
}
}
}
};
});
</script>
@declare(syntax=on)
</div>
</div>
Forms
UI component for Forms
They are located in the toolkit bundle, that can be included like so:
xhtml
<use:bundle path="toolkit:bundle"/>
This is also automatically included when using
xhtml
<use:bundle path="keeper:bundle"/>
See Usage Samples in the demo repository
Usage
Forms are mostly regular HTML forms that have the ajax submission functionality on top
xhtml
<form:wrapper action="/" method="PUT">
<form:input name="firstName" label="First Name" value="" size="6" required="true"/>
<form:input name="lastName" label="Last Name" value="" size="6" required="true"/>
<form:input name="email" label="Email" value="" required="true"/>
<form:input type="password" name="password" label="New Password" size="6" required="true"/>
<form:input type="password" name="confirmPassword" label="Confirm Password" size="6"/>
<form:label label="User Roles" name="roles" required="true">
@foreach(['admin'=>'Admin', 'super-admin'=>'Super Admin'] as $role => $label)
<form:checkbox id="role-{{ $role }}" name="roles[]" value="{{ $role }}" label="{{$label}}"/>
@endforeach
</form:label>
<form:select
label="Select Something"
values="{{ [1 => 'First', 2 => 'Second', 3 => 'Third'] }}"
value="2"
placeholder="Select Value"
/>
<form:radio-group
name="radios"
values="{{ [1 => 'First', 2 => 'Second', 3 => 'Third'] }}"
value="2"
/>
<form:button label="Create"/>
</form:wrapper>
form:wrapper
| Parameter | Required | Default | Description |
|---|---|---|---|
| action | yes | - | action URL of the form |
| method | no | POST | a Http method to use, GET or POST |
| id | no | - | id of form if you want to hardcode it |
| class | no | - | a class to add to the wrapper |
| immediate | no | - | debounces value in ms. if it's specified, any change event will trigger a form submission |
| submit-on-reset | no | false | submits the form on "reset" event, i.e. the reset button. Useful for filters for datagrids |
| data-before-submit | no | - | the name of a callback function in the global JS scope that will be called before the form is submitted. If that callback returns false, the form will not be submitted. |
| data-after-submit | no | - | the name of a callback function in the global JS scope that will be called after the form is submitted. Note, you are expected to check the result of submitting the form yourself. |
If you need more fine-grain control over the form and its callbacks, refer to source code
form:*
Most form inputs share common properties listed here
| Parameter | Required | Default | Description |
|---|---|---|---|
| label | no | - | A Label to render before input |
| required | no | false | If true, renders red * near the label |
| wrapper-id | no | - | Id to use for the wrapper div |
| wrapper-class | no | - | A class to add to the wrapper |
| size | no | 12 | Column size for the grid system |
| error | no | - | Pre-rendered error feedback text |
| success | no | - | Pre-rendered success feedback text |
| help | no | - | Description text |
Important: Most input fields will proxy all unrecognized attributes to the corresponding input inside.
form:input
Simple form input
| Parameter | Required | Default | Description |
|---|---|---|---|
| name | yes | - | A field name |
| value | no | - | A field value |
| placeholder | no | - | A field placeholder |
| class | no | - | An additional class to render for the field |
| type | no | - | A field type attribute |
| disabled | no | - | If the field should be disabled |
xhtml
<form:input name="firstName" label="First Name" value="" size="6" required="true"/>
form:textarea
Simple form textarea
| Parameter | Required | Default | Description |
|---|---|---|---|
| name | yes | - | A field name |
| value | no | - | A field value |
| placeholder | no | - | A field placeholder |
| class | no | - | An additional class to render for the field |
| type | no | - | A field type attribute |
| disabled | no | - | If the field should be disabled |
form:select
Simple form select dropdown
| Parameter | Required | Default | Description |
|---|---|---|---|
| name | yes | - | A field name |
| value | no | - | A field value, note that when it's used with 'multiple', it should contain an array |
| values | no | - | Select options which are mapping values to labels |
| placeholder | no | - | A field placeholder. It will be rendered as a separate option with an empty value. |
| class | no | - | An additional class to render for the field |
| type | no | - | A field type attribute |
| disabled | no | - | If the field should be disabled |
xhtml
<form:select
name="single"
label="Select Something"
values="{{ [1 => 'First', 2 => 'Second', 3 => 'Third'] }}"
value="2"
placeholder="Select Value"
/>
<form:select
multiple
name="multi[]"
label="Select Something"
values="{{ [1 => 'First', 2 => 'Second', 3 => 'Third'] }}"
value="{{[1,2]}}"
placeholder="Select Value"
/>
Forms: Autocomplete
UI component for autocomplete in the forms
They are located in the toolkit bundle, that can be included like so:
xhtml
<use:bundle path="toolkit:bundle"/>
This is also automatically included when using
xhtml
<use:bundle path="keeper:bundle"/>
See Usage Samples in the demo repository
Usage
xhtml
<form:autocomplete
name="userId2"
label="Simple Autocomplete"
value="1"
>
<script role="sf-options" type="application/json">
{
"url": "/keeper/users/list",
"searchKey": "firstName",
"valueKey": "id"
}
</script>
</form:autocomplete>
Autocomplete uses the same API as DataGrids. Autocomplete by default only operates values, not labels, so in the pre-population
phase it will make a request to server to fetch the current labels. I.e. The sample above will make a request
with filter[id][]=1 body to keeper/users/list URL on load.
To handle comma separated values on backend, implement a value accessor
form:autocomplete
There are 2 blocks of parameters you can specify. The most commonly used ones can be specified directly inside xhtml tag, however more advanced parameters are defined in JSON block
Basic params
xhtml
<form:autocomplete
name="userId2"
label="Simple Autocomplete"
value="1"
url="/keeper/users/list"
></form:autocomplete>
| Parameter | Required | Default | Description |
|---|---|---|---|
| url | yes | - | Url that implements DataGrid API |
| name | yes | - | A field name to use |
| placeholder | no | - | A placeholder for the input |
| disabled | no | - | Renders the input as disabled |
| value | no | - | Provides a pre-populated value of autocomplete |
| labelValue | no | - | Provides a pre-populated label of autocomplete. If it's specified, autocomplete will not try to resolve "value" from the server. |
| preserve-id | no | - | Don't erase the selected id when a user types after autocomplete selection. It's only for single choice autocompletes |
Extended params
Extended params allow to specify templates and customize the mapping for API
xhtml
<form:autocomplete
name="userId2"
label="Simple Autocomplete"
value="1"
>
<script role="sf-options" type="application/json">
{
"url": "/keeper/users/list",
"searchKey": "firstName",
"valueKey": "id"
}
</script>
</form:autocomplete>
| Parameter | Required | Default | Description |
|---|---|---|---|
| id | no | - | Id to use for the input |
| url | yes | - | Url that implements DataGrid API |
| method | no | POST | POST or GET |
| headers | no | {} | Headers to send |
| name | yes | - | A field name to use |
| isMultiple | no | false | Allows multiple selections |
| preserveId | no | - | Don't erase the selected id when a user types after autocomplete selection, it's only for single choice autocompletes |
| data | no | - | If it's specified, it can operate as server-less autocomplete with the data pre-defined. Accepts an array of strings or IAutocompleteStaticDataItem array |
| inputTemplate | no | - | handlebars template to customize what will be displayed in the input. Accepts a row data item as variables available in the template. |
| suggestTemplate | no | - | handlebars template to customize what will be displayed in the suggestions. Accepts a row data item as variables available in the template. |
| loadingTemplate | no | - | handlebars template to customize what will be displayed during the loading. |
| valueKey | no | 'id' | A field that will be used as a value |
| searchKey | no | 'name' | A field that will be used as a label |
| dataField | no | 'data' | A field that will be used as a data list field from the response |
| separator | no | ',' | A separator that will be used for separating values in multi-select |
| debounce | no | 0 | Debounce value to throttle search events |
| exposeLabelAs | no | - | If it's specified, label will have a separate input that will also be submittted with a form |
| exposeLabelAsRequired | no | false | If it's specified, the exposed label will be rendered with the "required" attribute |
| initialDataItems | no | - | If it's specified, it will be used as a replacement for value + valueLabel. It can contain multiple values, so it can be used for pre-populating multiselect inputs. Its hould be a IAutocompleteDataItem array |
For demo of usages refer to Usage Samples
Forms: Datepicker
UI component for autocomplete in forms
They are located in the toolkit bundle, that can be included like so:
xhtml
<use:bundle path="toolkit:bundle"/>
This is also automatically included when using
xhtml
<use:bundle path="keeper:bundle"/>
See Usage Samples in the demo repository
Native date picker form:date
xhtml
<form:date
name="date"
label="Native Date Picker"
value=""
size="6"
/>
It renders a native type=date element with no additional functionality or extended browser support
JavaScript date picker form:date-js
xhtml
<form:date-js
name="date1"
label="Date"
value="2020-10-29T14:14:14+0300"
size="6"
/>
It renders a JS powered datepicker with extended functionality. Format tokens are inherited from Luxon
| Parameter | Required | Default | Description |
|---|---|---|---|
| name | yes | - | A field name to use |
| placeholder | no | - | A placeholder for the input |
| disabled | no | - | Renders the input as disabled |
| value | no | - | It provides a pre-populated value. It should match theformat used for server-client communication |
| format | no | yyyy-MM-dd'T'HH:mm:ssZZZ | The format expected from the server and the format that is used to send data to the server. It does not affect how the date looks like in the input |
| display-format | no | yyyy LLL dd | The format used to display in the datepicker input |
| enable-time | no | false | Enables time input. It's developer's responsibility to change the display format to have hours and minutes displayed. |
| force-confirm-button | no | false | Forces the display of the Apply button. It's recommended for calendars with time pickers |
| no-calendar | no | false | Removes the calendar and uses only the time picker. You may want to change the format options to send time only, as the default sends the full date |
JavaScript date range picker form:date-range-double
xhtml
<form:date-range-double
startName="date1"
endName="date1"
label="Date"
startValue="2020-10-29T14:14:14+0300"
endValue="2020-10-29T14:14:14+0300"
size="6"
/>
It renders a JS powered date range picker with extended functionality. Format tokens are inherited from Luxon
| Parameter | Required | Default | Description |
|---|---|---|---|
| startName | yes | - | A field name to use for the first input |
| startValue | no | - | Provides a pre-populated value for the first input. It should match the format use for server-client communication. |
| endName | yes | - | A field name to use for the second input |
| endValue | no | - | Provides a pre-populated value for the second input. It should match the format use for server-client communication. |
| disabled | no | - | Renders the input as disabled |
| format | no | yyyy-MM-dd'T'HH:mm:ssZZZ | The format expected from the server and the format that is used to send data to the server. It does not affect how the date looks like in the input. |
| display-format | no | yyyy LLL dd | The Format used to display in the datepicker input |
| enable-time | no | false | Enables the time input. It's developer's responsibility to change the display format to have hours and minutes displayed. |
| force-confirm-button | no | false | Forces the display of the Apply button. It's recommended for calendars with time pickers |
| no-calendar | no | false | Removes the calendar and uses only the time picker. You may want to change the format options to send time only, as the default sends the full date |
Forms: Rich Text Input
UI component for HTML
They are located in toolkit bundle, that can be included like so:
xhtml
<use:bundle path="toolkit:bundle"/>
This is also automatically included when using
xhtml
<use:bundle path="keeper:bundle"/>
See Usage Samples in demo repository
Usage
Declare TINY_MCE_KEY in .env file. Get free key here
After that include on page
xhtml
<form:tinymce
name="date"
label="Custom Options"
value="">
<script role="sf-options" type="application/json">
{
"options": {
"menubar": false,
"height": 300
}
</script>
</form:tinymce>
script tag is optional, if specified, JSON inside will be used for TinyMCE options
| Parameter | Required | Default | Description |
|---|---|---|---|
| value | no | - | HTML to render |
| name | yes | - | Field name |
Forms: QR Code
UI component for QR Codes
They are located in the toolkit bundle, that can be included like so:
xhtml
<use:bundle path="toolkit:bundle"/>
This is also automatically included when using
xhtml
<use:bundle path="keeper:bundle"/>
See Usage Samples in the demo repository
Usage
xhtml
<ui:qrcode
value="https://spiral.dev/"
type="canvas"
size="200"
bgColor="#f8f9fa"
fgColor="#49545f"
ecLevel="H"
/>
script tag is optional, if specified, JSON inside will be used
for TinyMCE options
| Parameter | Required | Default | Description |
|---|---|---|---|
| value | yes | - | Value to render |
| type | no | svg | A type of render, 'canvas' or 'svg' |
| size | no | 200 | Сode size |
| bgColor | no | white | A background color |
| fgColor | no | black | A foreground color |
| ecLevel | no | M | An error correction level |
| logoUrl | no | - | Specifies URL of the logo to render on top of the code. |
| logoHeight | no | - | Logo render height |
| logoWidth | no | - | Logo render width |
| logoX | no | - | A position to render the logo at |
| logoY | no | - | A position to render the logo at |
| logoMargin | no | - | Renders the background color space around the logo. Specify 0 to render only under the logo. Omit to render logos with transparent BG. |
xhtml
<ui:qrcode value="HK3ARG6MYFMIDDHB"/>
xhtml
<ui:qrcode
value="https://spiral.dev/"
type="canvas"
size="300"
bgColor="#f8f9fa"
fgColor="#578fca"
ecLevel="H"
logoUrl="/logo.svg"
logoHeight="50"
logoWidth="40"
logoX="130"
logoY="125"
logoMargin="0"
/>
← PREVIOUS
Views