Design options for object and context responses for sliders

[terracoda]

Related to improvements in the slider API defined here: #929

From @terracode on slack:

Slider object and context response design seem to be a pain point for design teams. Slider interactions are often very important for the learning goals of a sim by showing either an inverse or direct relationship between a slider value change and changes in the sim.

I feel some common code options for sliders could help design teams build out the desired relationship between the object and context changes more easily. AND it would be a huge improvement to our API. I would love to have a bit of time with Jesse and Sam to work on this. There were a lot of slider in QWI that we had to work out, ...

Existing Design Documentation:

• Initial Object Responses by Interaction Type - Take the slider relevant info from here and create options for sliders
• Object Responses & Interaction Type - Take the slider relevant info from here and create options for sliders
• Design Patterns for Multi-State & Custom Interactions - Take the slider relevant info from here and create options for sliders

Design Considerations:

• Design Task for Creating Object Response - Take the slider relevant info from here and create options for sliders
• Summary of Context Responses - Take the slider relevant info from here and create options for sliders
• Exemplar - Cognitive Walkthrough GFLB - Take the lessons from this walkthrough and create GENERAL options for sliders
• Design Challenges for John Travoltage - the sliders in JT do not describe a simple relationship.

[terracoda]

Noting here that at Core Description Meeting on August 20th, it was also discussed we need a decision tree about how to determine when to use a slider and when to create a custom object.