Fetch the table data using the API, and use the existing view item table to render the content of the widget.

Use django_assets to manage our assets and ensure we can minify js/css, compile less files, and merge all js/css into a single file. For this to work in production, all assets must be statically defined in his/assets.py. To ensure the correct js/css is included, views can invoke hid.assets.require_assets which will raise an exception if the asset is missing. This also has the advantage of making clear which part of the code depends on a given asset. The admin command in django_asset library's latest release does not work with the latest Django - so we use a version pulled from git. See https://github.com/miracle2k/django-assets/issues/52

Move font files under /media/fonts so they can be accessed at the expected place once the css is compiled into one file (font awesome accesses the fonts relative to the css location - so from /css/ to ../fonts/)

Disable mysql foreign key checks on staging, production and jenkins as well. See http://stackoverflow.com/questions/6178816/django-cannot-add-or-update-a-child-row-a-foreign-key-constraint-fails

Conflicts:
	django/website/dashboard/templates/dashboard/basic-text-widget.html
	django/website/local_settings.py.dev

Revert change to local_settings.py.dev regarding foreign key checks (mistakenly added with other styling changes)

Change from using an i tag for icons (which is what sb admin and bootstrap used to do) to using span tags for icons (which is more correct, and what bootstrap3 ended up doing as well)

Implement simple table widget. The data is currently stored in the widget settings, but this should be connected to the data api as and when needed

-- changing icon on basic-text-widget
-- adding active state bg-color to sidebar

Conflicts:
	django/website/transport/items.py

Escaping single quotes in json embed tag is actually un-necessary (and breaks the data) since the single quotes are replaced with html entities.

Remove untested djangojs url directive, which is not needed and does not work (mistakenly added following instructions)

InnoDb table and foreign key checks don't work well together in Django. See http://stackoverflow.com/questions/6178816/django-cannot-add-or-update-a-child-row-a-foreign-key-constraint-fails

I think this should really use ItemSerializer

Tidy up transport delete items

Make the url generation work proerly (though I'm fairly sure we don't
actually need the url as an argument to delete) and remove
debug print statement *blush*