Django-datatable-view

This release reverts a change to the Javascript that could cause errors in some cases. A fix will be reintroduced at a later time to correct a potential issue with Chrome and Safari not updating the footer text when a filter is applied.

The ``default_structure.html`` template has received a minor update to include the use of a CSS class ``"display"`` on the table, which how the datatables.js 1.10.0 version has begun to show examples on their documentation website, which gives the table a more modern default appearance. The bootstrap template is unchanged.

A fix from michaeldjeffrey should allow the browser's locale setting to control how the number of results is rendered in the table footer.

A fix from danmac-uk has been merged that adds Django 1.7 support, because of our current use of Django's ``StrAndUnicode`` base class for the template-renderable datatable object.

Various updates were made to the example project including a fix for "None" table headers in the embedded table demo.

New issues are being tracked at the github repository and we're building our milestone goals for release 1.0. We would like to include a streamlined strategy for column filters, an updated configuration strategy, and new callbacks to simplify support for datatables new ``"DT_RowData"`` key and modifying the internals of how special field types are handled for ORM querying.

This release adds Python 3 support with the help of the [six](http://pythonhosted.org/six/) project. We've taken some time to verify that unicode handling is handled correctly for both Python 2 and 3 simultaneously.

The options provided by a DatatableView are processed and merged with incoming GET data from ajax calls, and the resulting object replaces the view's ``datatable_options`` attribute at runtime. Previous to this release, that merged object implemented an attribute API to support lookups like ``options.search`` to get the search string.

As of this release, that attribute API has been removed for the sake of simplicity. Treat ``options`` like a normal dictionary and use the keys and values it contains to read any options. The only reason the object is a subclass of the base ``dict`` itself is to provide a constructor that accepts a GET query string and normalizes and validates options. Other than the normalization phase, it is a dictionary, first and foremost.

This release fixes a bug with sorting columns backed by concrete db fields not on the local model. The sorting operation would fail to recognize the field as concrete and would fall back to text-only sorting, which produced unexpected results.

This release adds incremental support for Python 3 (not completed yet, but the occational pull request comes in to help get things ready), and fixes a Python 2.6 compatibility issue with string formatting syntax.

The history of changes on each release has also been added to the code repository, available at ``django-datatable-view/CHANGELOG.md``.

This release fixes an issue with non-local fields sometimes raising errors when requested for sorting operations over ajax.

This release fixes a mistake that was made because the author was overconfident about the jQuery-dataTables API interchangeability.

The return value of the Javascript late initialization function ``datatableview.initialize()`` should now work like this:

javascript
$(function(){
var oTable = datatableview.initialize($(".datatable"));
});


Release 0.6.1 mistakenly returned an awkward set of nested arrays, leading to a need to re-call the ``dataTable()`` constructor, defeating the purpose of the return value as a convenience.