Improve Infrastructure for Giving Hints #3
Labels
No labels
accessibility
backport to lts
bug
code
critical
cygwin
documentation
duplicate
error reporting
external
feature
feedback
good first issue
help wanted
infrastructure
invalid
investigate
language spec
logs
lti
lts only
mac
maybe
qtype:bigbox
qtype:checkoff
qtype:expression
qtype:fileupload
qtype:multiexpression
qtype:multiplechoice
qtype:number
qtype:pythoncode
qtype:pythonic
qtype:pythonliteral
qtype:richtext
qtype:smallbox
question
question types
sandbox
security
syntax highlighting
ui/ux
wontfix
wsl
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
catsoop/catsoop#3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I've had a few thoughts and received a few suggestions for ways to improve hint-giving within CAT-SOOP. In particular, it would be nice to support (at least) the following kinds of hints:
MasteringPhysics-style Hints
These kinds of hints are hidden pieces of help that a student can activate by clicking them. Viewing hints may or may or may not affect the student's grade. It would be nice if these hints could contain questions themselves.
Post-submission Hints Based on Response
Right now, there are ways to provide feedback specific to a user's submission in most question types, by setting an appropriate message function. However, that can be kind of a pain. It would be nice for CAT-SOOP to handle giving hints in some situations. Probably, we would want to have a way to give hints based on the user's input alone, and, for some questions, also based on the results of evaluating the user's input (so based on the result, not just the form of the solution; particularly relevant for code).