AMO/FlightDeck/MooTools: Difference between revisions
< AMO | FlightDeck
Jump to navigation
Jump to search
Seanmonstar (talk | contribs) (Created page with "All client side JavaScript must work with MooTools 1.3 without the compatiblity layer. This means all code written, and all libraries added. If you're used to writing 1.2 and don...") |
Seanmonstar (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
== MooTools 1.3 == | |||
All client side JavaScript must work with MooTools 1.3 without the compatiblity layer. This means all code written, and all libraries added. If you're used to writing 1.2 and don't know what has been deprecated, this [https://github.com/mootools/mootools-core/wiki/Upgrade-from-1.2-to-1.3 wiki page] shows everything removed and what it should now be. | All client side JavaScript must work with MooTools 1.3 without the compatiblity layer. This means all code written, and all libraries added. If you're used to writing 1.2 and don't know what has been deprecated, this [https://github.com/mootools/mootools-core/wiki/Upgrade-from-1.2-to-1.3 wiki page] shows everything removed and what it should now be. | ||
== File Structure == | |||
All JavaScript files belong in the top level `media` directory. If the file is 3rd party, it belongs in `lib`, inside its own directory. If it is written by us, it should be in the directory inside `media` that relates to the Django app that uses it. | All JavaScript files belong in the top level `media` directory. If the file is 3rd party, it belongs in `lib`, inside its own directory. If it is written by us, it should be in the directory inside `media` that relates to the Django app that uses it. | ||
Revision as of 22:34, 11 January 2011
MooTools 1.3
All client side JavaScript must work with MooTools 1.3 without the compatiblity layer. This means all code written, and all libraries added. If you're used to writing 1.2 and don't know what has been deprecated, this wiki page shows everything removed and what it should now be.
File Structure
All JavaScript files belong in the top level `media` directory. If the file is 3rd party, it belongs in `lib`, inside its own directory. If it is written by us, it should be in the directory inside `media` that relates to the Django app that uses it.