Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

reportbuilder/Work outline: Difference between revisions

From MoodleDocs
No edit summary
mNo edit summary
Line 47: Line 47:
** Assign 20 (submissions, summary, final grades)
** Assign 20 (submissions, summary, final grades)
** Site log (exists in Totara, but need to upgrade to new log system)
** Site log (exists in Totara, but need to upgrade to new log system)
** Quiz (Maybe not quiz, it would be difficult getting him to accept all of this additional code) Not quiz.
** Quiz
** Forum
** Forum
** Make sure theses sources are indexed for performance
** Make sure theses sources are indexed for performance
* Finish Report Builder documentation 40
* Finish Report Builder documentation 40
* Move add button to the next row so that it’s clear that you already are adding a field 5
* Move add button to the next row so that it’s clear that you already are adding a field 5

Revision as of 06:37, 26 May 2014

  • Move report builder into report directory. 20
  • Update Unit tests 20 (Then keep them updated and passing throughout development)
  • Disable javascript calls (currently jquery). 13
  • Create YUI/Moodle Table (Talk to Frontend) 20
  • Use automatic class loading. 20
  • Clean up formatting.
    • Doc blocks. 20
    • Comments. 13
    • multiple parameters on one line. 20
  • Fix existing classes
    • Work out what is commented out and why (git diff ~/git/totara/mod/scorm/rb_sources/rb_source_scorm.php mod/scorm/rb_sources/rb_source_scorm.php)
    • Fix warnings
  • Replace calls to custom totara functions. 100
    • totara_set_notification()
    • file_postupdate_standard_editor() needs to be replaced (reportbuilder/general.php)
    • totara_feature_visable()
    • totara_get_manager()
    • Other yet undiscovered functions…
  • Remove irrelevant totara data from:
    • main plugin 20
    • child classes 20
  • Possibly split up report forms - Not sure that they will get through all in one file. 40
  • Investigate in detail the file totara/reportbuilder/db/install.php. This changes the database structure which I am sure that integrators would have some hard questions about. 20
  • reportbuilder/embedded/ all files need to be reviewed to determine if they are useful / relevant. 20
  • reportbuilder/filters/ remove jquery from hierarchy.php if not the whole file. 13
  • Totara_report_manager block needs to be included (or some other way for students and teachers needs to be found to access the reports). 40
  • Fix capitilisations. 13
  • Move language strings to plugin files 40
  • Fix navigation tree for viewing reports. 20
  • Cron functions probably need updating to use new cron system. 40
  • Replace add_to_log calls to event classes. 40
    • update report
    • view report
    • dailyreport
    • delete
    • $type . ‘ report’ - reportbuilder/index.php line 56 (deletion of report)
    • new report
    • export report
  • accessibility check. 20
  • reportbuilder/showhide.php remove jquery and replace with yui. 100
  • Review all code 50+ files, thousands of lines of code. 100
  • Add behat tests 20
  • Port over sources from Totara 40
    • Remove totara specific fields (diff between the database schemas in Totara and Moodle to see what fields to remove)
    • Remove totara specific functions
  • Add more classes to useful areas of Moodle (More than just SCORM). 100
    • Assign 20 (submissions, summary, final grades)
    • Site log (exists in Totara, but need to upgrade to new log system)
    • Quiz
    • Forum
    • Make sure theses sources are indexed for performance
  • Finish Report Builder documentation 40
  • Move add button to the next row so that it’s clear that you already are adding a field 5