Currently, the template views forcedChoice, sentenceChoice and imageSelection all take two options to select from. We should ideally generalize this to allow an arbitrary number of choice options.
with also an optional field grid_layout which takes the numbers of rows and columns of a table to be filled in with the options. Here [3,2] would give us three rows and two column. The optional field fill_by would specify whether to fill the grid row- or column-wise. The above would yield an display like this:
Currently, the template views
forcedChoice
,sentenceChoice
andimageSelection
all take two options to select from. We should ideally generalize this to allow an arbitrary number of choice options.Instead of providing options like this:
We could have:
with also an optional field
grid_layout
which takes the numbers of rows and columns of a table to be filled in with the options. Here[3,2]
would give us three rows and two column. The optional fieldfill_by
would specify whether to fill the grid row- or column-wise. The above would yield an display like this:1 2 3 4 5 6