Refactoring of Cloze-Question-Editing UI

1 Requirements

This is an element from the T&A Maintainer Funding Wishlist, transferred due to a potential funding. Implementation details need to be settled prior to a funding availability can be communicated.
 
Original text:
Refactoring of Cloze-Question-Editing UI
The cloze-question currently sends a whole bunch of requests to ILIAS during its proper creation. We would like to overhaul this in favor of a client side solution, so the roundtrips to the server to create gaps can be saved. This will allow for smoother creation of these questions and also helps to get rid of some "out of band"-request handling. We would prefer to have the same "pattern" in edit -> save request over all question, allowing for further abstraction of these processes. (This change needs JF approval since it affects the UI and we will see to it if this matter becomes "active" through regular means, e.g. an own feature wiki page.)

The proposed dropping of support for non-javascript clients as per Streamlining Javascript Usage in Tests allows richer UIs. The current situation is, that many tasks which are commonly done these days in the client using javascript, are passed to the server, causing a roundtrip. Aside from this causing unnecessary traffic, there are a number of problems, especially with complex question types - like "rearrangements" of dynamic elements.
 
We propose:
- To implement the answer-element-creation using a javascript solution, so the question can be configured in one step.
 
This proposal is only valid in conjunction with the proposed changes described at Refactoring of the Cloze Question type. We do not want to make this change unless we have working material / question text separated.

2 Status

• Scheduled for: Release 5.0
• Funding: Universität Erlangen-Nürnberg
• Maintainer: Björn Heyser
• Implementation of the feature is done by Databay AG AG, Björn Heyser bheyser_at_databay_dot_de, Maximilian Becker mbecker_at_databay_dot_de
• Contract settled: Yes
• Tested by / status: Fred Neumann, fred.neumann@fau.de / testing completed

3 Additional Information

Contact the following persons if you want to know more about this feature, its implementation or funding:

• Information about concept: Databay AG AG Maximilian Becker mbecker_at_databay_dot_de
  
• Information about funding: Databay AG AG Maximilian Becker mbecker_at_databay_dot_de
• Information about implementation: Databay AG AG Maximilian Becker mbecker_at_databay_dot_de

4 Discussion

JF 25 Nov 2013: We appreciate this feature and schedule it for 4.5.

JF 13 Oct 2014: We finally accept the implementation if

• buttons are migrated to bootstrap ui
• the gap overlay is fixed (suggestion: ILIAS modal component)
• we introduce a general CSS class for "invalid" input fields (defining a background color)
• style of invalid fields should be changed as soon as the content changes not "on blur".

JF 5 Jan 2015: We finally accept the implementation if

• the gap overlay contains an "OK" button that closes the overlay (and updates the input fields) - other ways to close the overlay ("x" and clicks outside of the overlay) should not update the input fields
• input fields with missing/invalid values should use the standard alert DIVs used in forms (e.g. if no question text is provided and question is saved). The fields themselves should not get any visual effects.

5 Implementation

25 June 2014: Implemented and ready for acceptance.

6 Testing

4 Sept. 2014 Fred Neumann: tested  (see related Refactoring of the Cloze Question type).