Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
E
edx-platform
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
edx
edx-platform
Commits
78a50bd7
Commit
78a50bd7
authored
Oct 27, 2014
by
srpearce
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #5748 from edx/sylvia/docs/prob_correct
Replace index file
parents
4742687a
8f825ca6
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
30 additions
and
40 deletions
+30
-40
docs/en_us/course_authors/source/exercises_tools/index.rst
+30
-40
No files found.
docs/en_us/course_authors/source/exercises_tools/index.rst
View file @
78a50bd7
.. _
Problems and Tools
:
.. _
Exercises and Tools Index
:
############################
#####
Problem
s
############################
#####
############################
Creating Exercises and Tool
s
############################
The format for edX problems is based on the `LONCAPA XML format`_,
although the two are not quite compatible. In the edX variant, problems are
composed of four types of tags:
Use the chapters in this section to understand how to create exercises and
tools in your course.
* **inputtypes** are similar to XBlocks. They define ways for users to enter
input into the problem.
* **responsetypes** are graders. They define how inputs are mapped to grades.
* **hinters** are used to provide feedback to problems.
* Standard HTML tags are used for formatting.
For information on how to develop your course content in the Studio Outline
page, see :ref:`Developing Your Course Index`.
OLX is designed to allow mixing-and-matching of inputtypes,
responsetypes, and hinters. For example, a numerical grader could match
7+-0.1%. It would be okay to use this with any inputtype which output a number,
whether this was a text box, equation input, slider, or multiple choice
question. In practice, this doesn't always work. For example, in the former
case, a multiple choice question would not give an output in a format a
numerical grader could handle.
For information on building specific course component types, see :ref:`Creating
Course Content Index`.
In addition, in many cases, there is a 1:1 mapping between graders and inputs.
For some types of inputs (especially discipline-specific specialized ones), it
simply does not make sense to have more than one grader.
The most general grader is ``customresponse``. This uses Python code
to evaluate the input. By design, this ought to work with any inputtype,
although there are bugs mixing this with a small number of the newer
inputtypes.
Like LON-CAPA, OLX allows embedding of code to generate parameterized problems.
Unlike LON-CAPA, edX supports Python (and not Perl). Otherwise, the syntax is
approximately identical.
.. toctree::
:maxdepth: 2
create_exercises_and_tools
annotation
checkbox
chemical_equation
circuit_schematic_builder
conditional_module
custom_javascript
custom_python
drag_and_drop
dropdown
external_graders
full_screen_image
gene_explorer
google_hangouts
iframe
image_mapped_input
lti_component
math_expression_input
mathjax
molecule_editor
m
ult_choice_num_input
m
olecule_viewer
multiple_choice
mult_choice_num_input
numerical_input
problem_in_latex
open_response_assessment
periodic_table
poll
problem_with_hint
problem_in_latex
protein_builder
symbolic_response
text_input
.. include:: ../links.rst
word_cloud
custom_python
zooming_image
mathjax
\ No newline at end of file
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment