Skip to content
Johan Henkens edited this page May 28, 2014 · 2 revisions

Things that might be nice to do:

  • Add unit tests (qunit?)
  • Add more/better documentation. Is there a preferred javascript docs-generation type documentation?
  • Split up files to better represent their classes
  • Use a 'compiled' version of the code in the web application to reduce load times (google closure compiler, https://github.com/mishoo/UglifyJS (jquery uses uglify))
    • If the code used less call by string value methods, we could probably even begin using the 'advanced' features of the compiler. Regardless, we could use them if we indicate with comments / preprocessor code that the methods are referenced by string-name.
  • Reduce/eliminate reliance on jQuery once features have been proven
Clone this wiki locally