Shows images.
-- Images are clickable, which triggers a placeholder "results are in" to simulate other players giving their answers.
Shows a text prompt based on image type and model type. Easily extended, but very rough around the edges.
-- Can be developed to take more data; some comments in documentation touch on this.
-- The "makePrompt" function might also, simultaneously, generate the "motivation" in the future. "makePrompt" would be "makePromptAndCorrectAnswerMotivation", so to say.
Does not:
-- Show player scores. Only who was correct and got points.
-- Take actual model output parameters into account, only the "novel data" of ours which is not yet implemented.
-- Start any sort of player-answer timeout.
-- Connect to redux state, or DB state, in any meaningful way. Should be easily modifiable for this, however.
-- In any way "loop" around to the next question.
Next steps:
-- Take "real" data as input. As soon as this is available, should be easy.
-- Send user input to database.
--- Create a answer timeout that forces a "no answer" to database.
--- Currently uses placeholder data.
Shows images. -- Images are clickable, which triggers a placeholder "results are in" to simulate other players giving their answers.
Shows a text prompt based on image type and model type. Easily extended, but very rough around the edges. -- Can be developed to take more data; some comments in documentation touch on this. -- The "makePrompt" function might also, simultaneously, generate the "motivation" in the future. "makePrompt" would be "makePromptAndCorrectAnswerMotivation", so to say.
Does not: -- Show player scores. Only who was correct and got points. -- Take actual model output parameters into account, only the "novel data" of ours which is not yet implemented. -- Start any sort of player-answer timeout. -- Connect to redux state, or DB state, in any meaningful way. Should be easily modifiable for this, however. -- In any way "loop" around to the next question.
Next steps: -- Take "real" data as input. As soon as this is available, should be easy. -- Send user input to database. --- Create a answer timeout that forces a "no answer" to database.