Forms: make it possible to set operationalState (enabled/disabled) in fconf

[bruno]

See summary.

While at it, we should probably verify the implementation of the enable/disable methods for some kinds of controls.

[mpo]

Thinking about this further:

This resembles the resently added initialValue in a number of ways

• We want these to be applied at the end of the initialization
• and I assume reset() should re-introduce this operationalState?

Given that similarity we could introduce an initialEnabled property and let it be picked up in the reset.

But maybe this suggests we reorganize things a bit into:

initial: {

value: "whatever",
enabled: false,
show: false

}

I know it breaks with the earlier introduced syntax for initialValue, but given that was not in a release yet I'ld prefer this more future-ready notation...

wdyt?

[jgou]

feature added by mpo in r1363

Some remarks:

• the initial block is a property of the control (hence should be placed in the control section in the form config. While this is the logical place considering the forms model, it might be more logical to users to place it a level higher in the config
• "disabled" attribute on the corresponding html input field is removed by the init function. By keeping and using this attribute, the above point (user convenience) loses importance.

And a minor bug: by disabling (via form config) a control, the following controls (of the same type) are also disabled. Looks like the inital object in base- and newconstructor are linked.

[jgou]

Replying to jgou:

And a minor bug: by disabling (via form config) a control, the following controls (of the same type) are also disabled. Looks like the inital object in base- and newconstructor are linked.

patched in r1366 after offline review by mpo

[mpo]

important remark though:

These 'initial' settings are part of the control, not the type.

Regarding ease of configuration we should maybe consider to provide future support to add dis-or-enabled/shown attributes in the html-template to be picked up during initElements (and then override the initial settings in fconf?)

[mpo]

Remaining work is thus:

• decide how to encode these settings into the HTML suggested: checking up on existing HTML attributes controlling these:
  • ​http://www.w3schools.com/TAGS/att_input_value.asp @value for initial.value,
  • ​http://www.w3schools.com/TAGS/att_input_disabled.asp @disabled for initial.enabled
  • ​http://www.w3schools.com/TAGS/att_input_type.asp @type='hidden' for initial.show)

• extend the current routine for implicit fconf reading to include these properties

[freya]

setting the initial options should be possible since r1477
via attributes "value", "enable", "show"

[freya]

attributes defined in HTml templates should be value="somevalue", disabled="disabled" or type="hidden" for resp initial value, enabled=false and show=false (and not enable/show as mentioned above)

since r1498 it is possible to add this initial properties via HTML while control and/or fieldType are defined via fconf

example:

var fconf = {

members: {

'name': 'string'

}

<input kauri-idref="name" kauri-role="input" value="test" disabled="disabled"/>