Files
edx-platform/openedx/core/lib/xblock_builtin
Tim Krones 3649f8181d Have DiscussionXBlock take care of loading JS and CSS files it depends on.
* Add openedx.core.lib.xblock_builtin.get_css_dependencies and get_js_dependencies,
  which respect PIPELINE_ENABLED setting when determining dependencies.
* Move new discussion-related Sass files into discussion subdirectory.
* Use "load_unicode" instead of "render_template" to load JS to add to fragment for DiscussionXBlock.
* Remove unused "course" parameter from context for DiscussionXBlock.student_view.
* Add RTL stylesheet for DiscussionXBlock, and enable the block to load correct stylesheet.
* Load MathJax only once, and include code for configuring MathJax in discussion bundle.
* Make sure username renders correctly in DiscussionXBlock response header.
* Move WYSIWYIG Markdown editor styles to _build-discussion.scss.
* Remove unnecessary import of discussion/utilities/v1-compatibility from _build-discussion.scss.
* Keep courseware-chromeless.html in sync with courseware.html.
* Load CSS for discussions on Teams tab.  This makes it possible to remove CSS for discussions from Sass files for "Course" tab.
* Load js/src/tooltip_manager.js, jquery.autocomplete.js and jquery.autocomplete.css on "Course" tab.
2016-10-12 01:22:42 +10:30
..

Open edX: Built-in XBlocks
--------------------------

This area is meant for exceptional and hopefully temporary cases where an
XBlock is integral to the functionality of the Open edX platform.

This is not a pattern we wish for normal XBlocks to follow; they should live in
their own repo.

Discussion XBlock
=================

This XBlock was converted from an XModule, and will hopefully be pulled out of
edx-platform into its own repo at some point.  From discussions, it's not too
difficult to move the server-side code , but the client-side code is used by
the discussion board tab and the team discussion, so for now, must remain in
edx-platform.