Commit a2a0c316 authored by Carsten  Rose's avatar Carsten Rose
Browse files

Index.rst: reformat some enumarations lists

parent 6f224ef2
......@@ -1140,7 +1140,7 @@ Type: radio
* Radio Buttons will be built from one of three sources:
* a) 'sql1': E.g. *{{!SELECT type AS label FROM car }}* or *{{!SELECT type AS label, typeNr AS id FROM car}}* or *{{!SHOW tables}}*.
* 'sql1': E.g. *{{!SELECT type AS label FROM car }}* or *{{!SELECT type AS label, typeNr AS id FROM car}}* or *{{!SHOW tables}}*.
* Resultset format 'named': column 'label' and optional a column 'id'.
* Resultset format 'index':
......@@ -1148,11 +1148,12 @@ Type: radio
* One column in resultset >> first column represents *label*
* Two or more columns in resultset >> first column represents *id* and second column represents *label*.
* b) *FormElement.parameter*:
* *FormElement.parameter*:
* *itemList* = `<attribute>` E.g.: *itemList=red,blue,orange* or *itemList=1:red,2:blue:3:orange*
* c) Definition of the *enum* or *set* field (only labels, ids are not possible).
* Definition of the *enum* or *set* field (only labels, ids are not possible).
* *FormElement.maxlength* = `<value>`
......@@ -1161,6 +1162,7 @@ Type: radio
* `<value>`: '', 0, 1 - The radios will be aligned *vertical*.
* `<value>`: >1 - The readios will be aligned *horizontal*, with a linebreak every 'value' elements.
* *FormElement.parameter*:
* *emptyItemAtStart*: Existence of this item inserts an empty entry at the beginning of the selectlist.
......@@ -1168,7 +1170,8 @@ Type: radio
* *emptyHide*: Existence of this item hides the empty entry. This is useful for e.g. Enums, which have an empty
entry but the empty value should not be an option to be selected.
* No preselection:
* *No preselection*:
* If there is a default configured on a table column, such a value is selected by default. If the user should actively
choose an option, the 'preselection' can be omitted by specifying an explicit definition on the FormElement field `value`::
......@@ -1183,7 +1186,7 @@ Type: select
* Select lists will be built from one of three sources:
* a) 'sql1': E.g. *{{!SELECT type AS label FROM car }}* or *{{!SELECT type AS label, typeNr AS id FROM car}}* or *{{!SHOW tables}}*.
* 'sql1': E.g. *{{!SELECT type AS label FROM car }}* or *{{!SELECT type AS label, typeNr AS id FROM car}}* or *{{!SHOW tables}}*.
* Resultset format 'named': column 'label' and optional a column 'id'.
* Resultset format 'index':
......@@ -1191,11 +1194,11 @@ Type: select
* One column in resultset >> first column represents *label*
* Two or more columns in resultset >> first column represents *id* and second column represents *label*.
* b) *FormElement.parameter*:
* *FormElement.parameter*:
* *itemList* = `<attribute>` - E.g.: *itemList=red,blue,orange* or *itemList=1:red,2:blue:3:orange*
* c) Definition of the *enum* or *set* field (only labels, ids are not possible).
* Definition of the *enum* or *set* field (only labels, ids are not possible).
* *FormElement.size*: `<value>`
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment