Thank you for bringing this discussion back; I was travelling during the original one. I just wanted to mention that the way we had planned to do this in the past would have hierarchies that are a little bit different:
> course (TabbedCourseDescriptor) | + AccordionXBlock | + chapter | | | + sequential | | | + vertical | | | + html | + problem + html (XModule/XBlock representing the "Info" tab) + discussion_forum (XBlock implementing the Forum) + vertical (Custom tab with custom title and potentially multiple child XBlocks) A single platform extension could be implemented as multiple XBlocks. In the same way as forums access both the same data from the courseware as from the forums tab, a peer grading extension might have e.g. XBlocks in the courseware for submission, and a top-level tab for peer grading. We've generally tried to maintain a split where the OLX generically defines the course and course structure, while the non-OLX parts of the tarball are edX extensions (most, but not all, of which would hopefully eventually merge into the OLX). We had defined an incremental path to get there too. I could find or reconstruct it, if this were of interest. Conceptually, I'm a little concerned about having multiple XBlock hierarchies in the course. I'm also a little concerned about presuming the structure of the course in the way that the chapter/chapter/tabset hierarchy does. I'm also concerned about having a child in the navigation not be so in the hierarchy. Tabs are parallel to the accordion, not the chapters. Piotr -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/35e71e8e-74ac-490f-a3e5-69bb75fcf775%40googlegroups.com.
