If there is no source set on the tab configuration, the upload
button will no longer be displayed.

Provide the tab instance to get_context_data, and use that to work out the URL to redirect forms to.

Remove outer html from the view and edit page, this is now taken care of by the tabbed page rendering.

Refactor the ViewsItems view, which covered the view and edit table, into a separate (non-view) class under tabs/view_and_edit_table.py. When ready, this will plug straight away into the new tabbed page functionality - in the mean time there is a place holder view to display the view where it used to be found.

Ensure we use the right taxonomy for the question category. The taxonomy in use is still hard-coded, as that is something we will look at later - this commit was only intended to restore functionality to the existing level.

Allow the chart count widget to have a time period. When present, apply the time period and display a legend detailing what the time period is.

-- replaced {{name}} with {{title}} on chart widget template
-- added h2 tag around bar chart table template title
-- fixed icon span class

ViewItem.get_category_options should return the options as we want them - we shouldn't have to process them later. So make sure it returns (short question, short question) as we want both the value and the text to use the short version.

Make the default empty batch command a line of dashes under the 'Actions' header. We can't really do better than that without js.

Re-introduce the per-row drop down to update each record's category as well as the mirrored buttons at the bottom of the page. This means that we have a single form that can either do a batch update, or an update of values set per row. The different action is determined by the submit button that was used - which is always named 'action'. Because we have a mirrored select drop down for the batch action, we need to know which one to take into account - so the value of the submit button indiciates which one was clicked, of the form <action>-<placement> (eg. save-top) and the name of mirrored inputs indidicate where they are located, of the form <name>-<placement> (eg. batchaction-bottom). The ViewItems class has a static method to find the active placement and rename the parameters accordingly. Some of the old code was re-introduced, though some of it was refactored (eg. what used to be get_categories, to fetch each row's selected category, has been moved to ItemTable to parallel get_selected, and is now named get_row_select_value (it's a more generic version, looking at the future when we'll update the region with the same mechanism.)

Rename select_action to select_item which makes more sense. Rename the checkbox itself select_item_id to allow other types of selectes in the future. Move the code to determing selected items into ItemTable since this is where the form is generated, and we know how it was build.

Replace the save changes button with a drop down list of actions and an update button. Actions include deleting and setting a question type on all selected items.

Refactor the 'select all checkboxes' javascript into a separate file so it can be used on other tables easily. Add a test for the select all checkboxes javascript. Remove the label from the 'delete' column (which is now a 'select all' column as we may have other actions) and move it to the first column as per balsamic mockups.

Refactor the code to handle file input type (use a custom button, and automatically submit upon file selection) so that it can be used on multiple pages. Add an upload button on the view/edit page.

-- removing hanging tabs
-- added easing to spinner and adjusted messages box to fit

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

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