Trigger happy

[amedranogil]

Originally Opened: @amedranogil (2013-09-20 11:40:40)

Feature Activation/deactivation of FormControls, FCs may be (de)activated according to a rule (TypeClass) if deactivated, Handlers will not show them to the user until the rule is validated. Handlers are informed when the rule indicates a FC has to be activated or deactivated.

Like wise the value of a FC may be described by some type of ValueRule (SPARQL? to be defined), so when an input ccontrol changes, this can trigger the value change.

For both cases the Input controls have to define which other FCs does it affect, so the triggering can be done efficiently.

Input controls can also trigger an information update to the application (autoApply). when the information is sent back to the user as submissionId the Input control URI is given.

Apply button, that sends the application the dataroot, but does not close the dialog.

to be added to FormControl:
isActivated() -- for handlers to check if the Fc is activated or not.
activation : Restriction
calcValue : CalcRule

to be added to Input
affects : List(FormControl)
autoApply : boolean

	evaluated in storeUserInput() if the result
	is going to return true, just before returing true

to be added to Form
addHandlingListener(HandlingListener)

to be called by the UI handler that has received the form object for handling

HandlingListener
activate(FC)
deactivate(FC)
valueChanged(FC) FC.getValue()
applyData(FC) submissionID = FC.getURI()

Apply <- Submit <- SubdialogTrigger

--

From: this issue has been automatically imported from our old issue tracker