We stick to the "new-table" way of specifying options.

The grid object may be needed by thirdparty code, for example
to refresh the canvas.

The cell renderers may add js at page onload. This js may require that
the dom is populated which occures once the slickgrid renderer is
called (at onload). We have to synchromously execute these js after
the dom is populated by slickgrid.

we put the whole SlickGrid sources in a dedicated directory, so
updating SlickGrid will be easier.

NOTE: the original source has been modified

The content of the `.name` attribute of the header is set by CW as
html content (see views.py). The `.name` is uses as the rendered table
header by slick.grid.js using `.html(...)` which render well the html
content.

But slick.columnpicker.js adds the `.name` of the header in the menu
using `.text(...)` which does not interprets the html.

The cset make the code more consistent.

We use the columnpicker plugin from slickgrid which add a right click
menu allowing the user to choose the displayed columns.

We use already existing table view class attribute `enable_sorting`.

Note that the original class does not seem to remove the tooltip about
column sorting if `enable_sorting` is `False`.

This view is very simple (no pagination, no column ordering).
Although it allows other table's view cutomization (headers, cellvids,
etc.).

The idea of this code is to override table view's code in order to
build grid content instead of writing HTML, then call the javascript
SlikGrid constructor.