Allow elements to be marked inactive (e.g.: for training purposes)

[giuliomoro]

in, e.g.: AB interface allows the interface to be used for training purposes. Users would not be able to change the color of the element by clicking on it.

[giuliomoro]

b90de14c86cf4cbfe3e04846bc27e43df585ebf5 (in the giulio branch) does this for AB. Note that if the user clicks on the element, the will still change and be stored int the resulting xml but this is not displayed to the user

[nickjillings]

Could you elaborate the training style you want?

I could see having a training page (perhaps more attribute fun) which will force the page to be the first page always and ignore its responses (or include them for filtering).

[giuliomoro]

I want a page like this Currently done using <page label="given"> and, e.g.: <audioelement inactive="true" label="Pressed fast">

[nickjillings]

I think this should be easy to do once #129 is complete and we can load interfaces modularly.

Otherwise a separate, fixed style example page could be designed to demonstrate and train the user. We need to design some markup for the specification to identify what audio to load and present.