|
Parameters | Accepted Values | Description | Default | Since |
---|---|---|---|---|
answer |
text | Used inline to specify the right answer to the question and propose an input field. | 9.0 | |
incorrect |
text | Incorrect answer to suggest. Several incorrect answers can be suggested (separated by "+") | 9.0 |
The below example will display the sentence with 3 text boxes where the exercise plugins are included inline. The plugin that does not expect an answer will be used to display the controls to check the score. There can be multiple exercise blocks within a single page.
This week-end {exercise answer=we're} going to go {exercise answer=where} we {exercise answer=were} best served. {exercise}
Instead of displaying text boxes, drop-down will be displayed. The last section indicates the other options to display additionally to the right answer specified in-line. The order will be randomized. The last question also specifies justifications that will be provided after the correction is made.
This code:
This week-end {exercise answer=we're} going to go {exercise answer=where} we {exercise answer=were} best served. {EXERCISE()} --- Comments can be written after the triple-dash. where were --- were we're --- where: Not a location we're: Cannot be replaced by 'we are' {EXERCISE}
Would produce (screenshot):
As produced from the code:
This week-end ___________ going to go ___________
we ___________ best served.
Alternatively, the options can be provided in-line instead of in the end block. This may be helpful to keep the information in-context, but sacrifices some readability in the text:
This week-end {exercise answer=we're incorrect="where + were"} going to go {exercise answer=where incorrect="were + we're"} we {exercise answer=were incorrect="where (Not a location) + we're (Cannot be replaced by 'we are')"} best served. {exercise}
Produces:
This week-end ___________ going to
go ___________ we ___________ best served.