AMO/FlightDeck/MooTools: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(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...")
 
No edit summary
 
(One intermediate revision by the same user not shown)
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.  


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.
== File Structure  ==
 
All JavaScript files belong in the top level <tt>media</tt> directory. If the file is 3rd party, it belongs in <tt>lib</tt>, inside its own directory. If it is written by us, it should be in the directory inside <tt>media</tt> that relates to the Django app that uses it.

Latest revision as of 22:39, 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.