- 20 Jul, 2015 9 commits
-
-
Tim Krones committed
-
For example, ResultView should not manipulate the status area (but it should maintain meta info about result sets).
Tim Krones committed -
"question" attribute.
Tim Krones committed -
Tim Krones committed
-
Tim Krones committed
-
results have been inserted into the DOM.
Tim Krones committed -
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
- 17 Jul, 2015 4 commits
-
-
Fix issue that can occur when upgrading split mongo courses
Braden MacDonald committed -
Implement tooltips/clarifications.
Matjaz Gregoric committed -
Allow students to download a copy of their answer table.
Kelketek committed -
Jonathan Piacenti committed
-
- 16 Jul, 2015 4 commits
-
-
Jonathan Piacenti committed
-
Instructor Tool XBlock - Polish (OC-751)
Tim Krones committed -
Tim Krones committed
-
Tim Krones committed
-
- 15 Jul, 2015 22 commits
-
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Backbone.js, and Underscore.js.
Tim Krones committed -
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
Tim Krones committed
-
changes only).
Tim Krones committed -
Matjaz Gregoric committed
-
The idea is based on capa <clarification> nodes: https://github.com/edx/edx-platform/pull/6679 I decided to go with <span class="pb-clarification> instead of a custom <clarification> node because supporting clarifications inside the html child block was a requirement, but the html block is defined inside edx-platform and we aren't able to preprocess the contents of the html block from within problem-builder. Even if we were able to get a patch for html block to support <clarification> elements upstream, I wouldn't feel very comfortable with that idea since the html block is supposed to contain plain html and making it recognize and preprocess custom elements wouldn't feel right. The best way to implement this would probably be custom DOM elements (document.registerElement), but browser support is not there yet and there are no reliable polyfills.
Matjaz Gregoric committed -
Braden MacDonald committed
-
- 13 Jul, 2015 1 commit
-
-
Export bugfixes
Kelketek committed
-