A project to display various types of questions in various ways. This first commit is actually me planning what this will look like. The motivation is that I am creating lots of maths questions and either reusing a rather poor one-size-fits-all in maths-elo, or I am making new displays for almost every question in Maths-How2
- Should take at least one question as an argument, possibly an array
- Progress bar to know how far through question set
- score
- status -- lives lost, maybe?
There are more details on this in the readMe for making the QShow container
- Show one correct answer and upto three wrong answers.
- All options should be in the question object, so the display component is not responsible for generating them.
- The display should randomise the options so the correct answer is not always in the same position.
- There should be an option to ask for confirmation after clicking an answer, or to mark it straight away.
- Marking should be indicated by colour. Correct goes green, wrong goes red. Consider leaving only the correct answer and the user's answer visible, or raising correct answer to the top.
- If some of the wrong answers are provided as traps, then consider giving feedback in the question object.
- A list is given with a desired order required. Eg: sort these people by date of birth: Mozart, Jesus, Ghandi, Napolean
- The question object includes the type, question text and the options in the required order -- the display will rearrange these.
- Ideally: drag and drop would be the option, but click to raise may be a good start.
In the context of putting lines of code into order, this type of questions are called Parson's problems. This is one of my target topics. But I don't want to have to check questions so that they have only one correct answer or to force question objects to list all possible correct answers (can still miss some). I think it is best to have a hint option. Some questions clearly have only one right answer.
- If the hint option is enabled then objects to sort are colour coded as to whether they are in the correct place.
This will still work for me in the coding questions because I will choose to engage with the task in a manner that requires me to think about the code.
String or number -- the later should have a keypad and no input box, so the display on mobiles doesn't get spolied by the keyboard coming up. The former should not have a question that is too long, since it should be readable while the mobile keyboard is on.
This could be limited by screen size unless the answers are short. The basic idea is that some of the questions can be answered by a process of elimination by answering the ones you know, and guessing from fewer options for the Qs that are left.
- List of up to 10 questions with 10 answers
- option to skip
- if user gives wrong answer, it goes red.
- no option to immediately retry after wrong answer, just a nextQ button
- this question object includes type and a list of text questions and a list of answers
- User clicks one word then must click the other which matches according to some rule
- (optional) Pelmanism type of matching with cards that turn
- the question object will include qType, question text and an array of pairs to be matched
- User is given two or three buckets and must drag the options to the correct one.
- options can be displayed all at once or in the order in which they should be classified.
- if user gets one wrong and not all displayed, that one should go to end of list to be tried again later. Otherwise, if all displayed, let them guess again -- but then repeat the options they got wrong at the end.
- question object will include type, question text and two arrays of the same length.
- the first array lists the buckets
- the second array contains lists of what should be in each bucket
- Contain question and answer -- wrong answers for multiple choice
- question generator for maths topics, eg: times table