Card Config Rendering Overview
When a regular user sees a Card in Aperta, in technical terms they're
normally pointing their browser at a Task for a given Paper. That
Task will display a tree of CardContent for the CardVersion the
task is associated with.
Each type of CardContent has a corresponding Ember component. For
instance, <CardContent id: 1, content_type: 'display-children'> will
eventually be represented on screen by the component
named card-content/display-children. Every node in the CardContent
tree will first render the card-content Ember component. This
component is responsible for doing operations that are common to every
type of content. The card-content component will look up the answer
for a piece of content (based on the content's ident), and is also
responsible for saving answers back to the server. The card-content
component itself will then render the appropriate type of component for
the content dynamically using the component
helper.
|
