Buttons can be initialised very easily though the buttons object which can be given as an array of the buttons that you wish to display. The B option in the dom parameter will instruct DataTables where the buttons should be placed in the document - in this case, at the top left (CSS also plays a part).

Fundamentally, each button is described by an object - this object is read by Buttons and displayed as appropriate. There are a number of parameters that Buttons will automatically look for in the button description object such as buttons.buttons.text and buttons.buttons.action which are the two fundamental parameters (button text and the action to take when activated).

This example also shows button definition objects being used to describe buttons. In this case we use the buttons.buttons.className option to specify a custom class name for the button. A little bit of CSS is used to style the buttons - the class names and CSS can of course be adjusted to suit whatever styling requirements you have. RedOrangeGreen

Keyboard navigation is essential for fast navigation of a table operations and also for good accessibility. Buttons provides the ability to give each button a key binding - i.e. a key combination that when pressed will activate the button's action.

The key binding can be given as a single character if you wish to listen for an unmodified key press, or as an object if you wish it to only be activated when a modifier key such as shift, alt, etc, is pressed.

As of Buttons 1.1, basic options for displaying a collection inside a collection is possible simply by using a collection button in the buttons array for another collection. This Inception like behavior basically means that multi-level collections are possible.

Buttons' ability to have new instances constructed arbitrarily gives it the ability to have multiple button instances created for a single DataTable. This can be useful if you wish to display button groups with different functionality (file export, editing, etc).

Buttons' ability to have new instances constructed arbitrarily gives it the ability to have multiple button instances created for a single DataTable. This can be useful if you wish to display button groups with different functionality (file export, editing, etc).