Refactor all scripts as modules or helpers

[kittsville]

WP-Librarian's scripts are a mess. A collection of small pieces of functionality that merged and connected together with no clear structure. Pretty much all of the scripts reflect some stage in my level of experience with JavaScript, creating a diverse range of methods to achieve their purpose.

This issue aims to deal primarily with restructuring the scripts into modules, with helpers where it would be silly to wrap unconnected functions up as a module. It is inevitable though that some scripts will end up being worked on during this process to some degree. Even if just to remove some of the more feckless comments (read: 'x.doY() // Does Y to X).

[kittsville]

Currently waiting on completion of Dev Kit asset minification.

[kittsville]

Dev Kit asset minification has now been completed. Full steam ahead with this issue!

[kittsville]

Actually screw that, I'm playing Transistor.

[kittsville]

See 5d698df, b3161df, 94dcafa, 5b55d92, 636a44b

[kittsville]

See 0610470. I need to start remembering to reference issues in commits.

[kittsville]

Meanwhile, in the global JS namespace

[kittsville]

admin-core.js feels harder to read given the new 'Notifications' module. While it works great for the page-dependant scripts on the Dashboard I'm not sure if it works for the core.

I really wish I could find something out there for WordPress JS design paradigms. There's a good article on project structure and minification/use of LESS/SASS (which I do miss since Rails) but I've been unable to find anything about JS structure itself. I'm guessing most people only use JS for small things in WordPress and outside of WP they use one of the many frameworks. Sucks to be me.

[kittsville]

That gif is really distracting.

[kittsville]

While the core scripts still need refactoring WP-Librarian is overdue a release. I'm putting this issue on hold until Bowie.

[kittsville]

Actually I'll create a new issue.