diff --git a/.datatables-commit-sync b/.datatables-commit-sync index 79d2dfe0..d5c76989 100644 --- a/.datatables-commit-sync +++ b/.datatables-commit-sync @@ -1 +1 @@ -45da091f3432b78e135e090c22b4ef03fdb760a0 +7af80a12efe4be1d7426868b736c93afc8dc0ded diff --git a/examples/advanced_init/dom_toolbar.html b/examples/advanced_init/dom_toolbar.html index 356afc38..0503dc22 100644 --- a/examples/advanced_init/dom_toolbar.html +++ b/examples/advanced_init/dom_toolbar.html @@ -44,18 +44,19 @@ $(document).ready(function() {

DataTables inserts DOM elements around the table to control DataTables features, and you can make - use of this mechanism as well to insert your own custom elements. In this example a div - with a class of 'toolbar' is created using domDT, with which HTML is - inserted to create the toolbar. You could put whatever HTML you want into the toolbar and add event - handlers etc.

+ use of this mechanism as well to insert your own custom elements. In this example a div with a class of 'toolbar' is created using domDT, with which HTML is inserted to create + the toolbar. You could put whatever HTML you want into the toolbar and add event handlers etc.

For more complex features, or for creating reusable plug-ins, DataTables also has a feature plug-in API available, which can be used to create plug-ins which are used in a table by a single character reference in the domDT option (like the built in option of - f refers to 'filtering input', you could have an F option which creates your - own filtering input control, custom to your app).

+ f refers to 'filtering input', you could have an + F option which creates your own filtering input control, + custom to your app).

TableTools is a feature plug-in for DataTables which adds buttons into a toolbar for a table, which controls such as copy to clipboard, diff --git a/examples/ajax/custom_data_property.html b/examples/ajax/custom_data_property.html index bab36478..e56f857f 100644 --- a/examples/ajax/custom_data_property.html +++ b/examples/ajax/custom_data_property.html @@ -58,8 +58,9 @@ $(document).ready(function() {

The example below shows ajax.dataSrcDT being used as - a string to get the data from a different source property, in this case demo but it could - be any value, included a nested property by using standard dotted Javascript object notation.

+ a string to get the data from a different source property, in this case demo but it could be any value, included a nested property by using standard dotted + Javascript object notation.

diff --git a/examples/ajax/defer_render.html b/examples/ajax/defer_render.html index 1f6bcaed..0c675fd9 100644 --- a/examples/ajax/defer_render.html +++ b/examples/ajax/defer_render.html @@ -39,11 +39,12 @@ $(document).ready(function() { deferRenderDT option.

-

When deferred rendering is enabled, rather than having DataTables create all TR and - TD nodes required for the table when the data is loaded, DataTables will only create the - nodes required for each individual row at the time of that row being drawn on the page (these nodes are - then retained in case they are needed again so they aren't created multiple times). This can give a - significant performance increase, since a lot less work is done at initialisation time.

+

When deferred rendering is enabled, rather than having DataTables create all TR and TD nodes required for the + table when the data is loaded, DataTables will only create the nodes required for each individual row + at the time of that row being drawn on the page (these nodes are then retained in case they are needed + again so they aren't created multiple times). This can give a significant performance increase, since a + lot less work is done at initialisation time.

The example below shows DataTables with deferred rendering enabled. For this small example you'll likely notice no difference, but larger tables can benefit significantly from simply enabling this diff --git a/examples/api/api_in_init.html b/examples/api/api_in_init.html index b49380a3..b209b707 100644 --- a/examples/api/api_in_init.html +++ b/examples/api/api_in_init.html @@ -49,7 +49,7 @@ $(document).ready(function() { then use that variable in the callback. However, all of DataTables' callback functions are executed in the scope of the DataTable instance, so you can use the Javascript special variable this to access the API (this.api() will give an API instance) as this is the - table node.

+ table node.

In this example you will be able to see that the $()DT method can be used to get nodes from the document regardless of paging, ordering etc. This example shows $()DT being used to get all input elements - from the table.

+ "DataTables API method">$()DT being used to get all input elements from the table.

In the example a simple alert() is used to show the information from the form, but an Ajax call to the server with the form data could easily be performed.

diff --git a/examples/api/multi_filter_select.html b/examples/api/multi_filter_select.html index 3b78e41f..7b5e182a 100644 --- a/examples/api/multi_filter_select.html +++ b/examples/api/multi_filter_select.html @@ -48,17 +48,19 @@ $(document).ready(function() {

This example is almost identical to text based individual column example and provides the same - functionality, but in this case using select input controls.

+ functionality, but in this case using select input + controls.

-

After the table is initialised, the API is used to build the select inputs through the - use of the After the table is initialised, the API is used to build the select inputs through the use of the column().data()DT method to get the data for each column in turn. The helper methods unique()DT and sort()DT are also used to reduce the data for set input - to unique and ordered elements. Finally the change event from the select - input is used to trigger a column search using the change event from the select input is used to trigger a column search using the column().search()DT method.

diff --git a/examples/basic_init/alt_pagination.html b/examples/basic_init/alt_pagination.html index 0b9f28a0..36a002fe 100644 --- a/examples/basic_init/alt_pagination.html +++ b/examples/basic_init/alt_pagination.html @@ -42,11 +42,13 @@ $(document).ready(function() {

There are four built-in options for which pagination controls DataTables should show:

The language strings of 'First', 'Previous' etc can be optionally through the internationalisation @@ -59,7 +61,8 @@ $(document).ready(function() { plug-ins. Furthermore, how the buttons are actually shown can be altered through the use of plug-in pagination renderers.

-

The example below shows the full_numbers type of pagination.

+

The example below shows the full_numbers type of + pagination.

diff --git a/examples/basic_init/table_sorting.html b/examples/basic_init/table_sorting.html index 06d11ce7..15a373f5 100644 --- a/examples/basic_init/table_sorting.html +++ b/examples/basic_init/table_sorting.html @@ -40,9 +40,10 @@ $(document).ready(function() {

The orderDT parameter is an array of arrays - where the first value of the inner array is the column to order on, and the second is - 'asc' (ascending ordering) or 'desc' (descending ordering) as required. - 'asc' (ascending ordering) or 'desc' (descending ordering) as required. orderDT is a 2D array to allow multi-column ordering to be defined.

diff --git a/examples/server_side/post.html b/examples/server_side/post.html index 6291e6d1..24277054 100644 --- a/examples/server_side/post.html +++ b/examples/server_side/post.html @@ -62,7 +62,7 @@ $(document).ready(function() {

The example below shows ajaxDT being used with the type - option set to POST to make a POST request.

+ option set to POST to make a POST request.