JavaScript usage guide: Difference between revisions
From MoodleDocs
No edit summary |
(→Goals) |
||
| Line 11: | Line 11: | ||
=Goals= | =Goals= | ||
* | * standardise usage of Javascript code in Moodle | ||
* | * improve performance | ||
* improve and simplify JS related APIs | * improve and simplify JS related APIs | ||
Revision as of 11:03, 27 January 2010
Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.
| Javascript usage guide | |
|---|---|
| Project state | Work in progress |
| Tracker issue | MDL-21240 |
| Discussion | n/a, developer chat only |
| Assignee | Petr Škoda (škoďák) + feedback and ideas from Sam and Dongsheng, based on previous work of Nicolas and Tim |
Moodle 2.0
Goals
- standardise usage of Javascript code in Moodle
- improve performance
- improve and simplify JS related APIs
API overview
Types of JS code in 1.9:
- JS scripts linked from page head
- JS linked and executed from page head
- inline Javascript
- global JS variables
Overview of JavaScript usage in 2.0
- all JS stored in one global M namespace
- majority of JS logic moved into page footer
- loading of javascript modules handled by YUI3 loader
- all plugins support module.js files
- most JS is initialised through $PAGE->requires->js_init_call()
- full migration to YUI3, YUI2 modules are loaded on demand only
