Implementation plan

This information is more up-to-date in the Moodle Tracker.

  • New reorder tab
    • Does this need a new cabability? I guess not.
  • New Quiz edit tab
    • Virtually adding empty random question categories in a quiz: functionality not supported by current data structures. Note that this is a virtual operation: before the category actually contains questions, the actual Quiz application logic needs not know about it (?).
    • Moving questions up&down
    • Adding single questions
    • Scoring questions and exam
    • Deleting questions from exam & categories
    • Possibly, moving questions between categories (not sure yet if this needs to be supported in the Quiz editing screen)
    • Presentation of different question types: At this point, only question name and actual question text will be presented, but it must be taken into account that in future versions it will be useful to list, for example, the different choices of a multiple choice question.
    • New question bank contents -side
      • Consider if it should also replace Question bank’s own UI; probably not, but some UI enhancements should probably taken  there, too to retain consistency
      • Question bank hideability: making the question bank persist in the position the user last left it by storing the information in the session/db (does the category selection persist?)
      • As soon as the YUI resize component comes out of beta, we can use that to allow users to have the question bank window the size they want.
      • Storing the state
      • Retrieving it both server-side and in javascript (no dependence on js)
  • HTML/CSS design; work to get UI elements into the Moodle theming system or, when feasible, use what is already there.
  • Find the best implementation methods for some simple javascript magic (Moodle pretty much mandates YUI): tooltips, greybox dialogs (which would contain what current moodle full-page confirmation dialogs)
  • Add help icons in appropriate places; add labels to icons where testing shows it is required; write further relevant documentation to Docs
  • Clean up any inline javascript, CSS & HTML; move to appropriate libraries and themes; research what is the optimal approach with these
  • Localize all strings