1
0
mirror of https://github.com/DataTables/DataTables.git synced 2024-12-04 16:24:11 +01:00
Commit Graph

24 Commits

Author SHA1 Message Date
Allan Jardine
a0455fa858 New: The primary public interface for DataTables' initialisation options is now camel case parameters rather than the Hungarian notation that was used before. There are a number of reasons for doing this, the primary one being that the Hungarian notation used by DataTables is actively stopping people from using the library due to their aversion to using Hungarian notation. Without doubt the Hungarian notation used was a mistake (the reason it was used was that when DataTables was originally written, the company I worked for at the time required the use of Hungarian notation, and thus I was trained in it...).
Backwards compatibility issues: The main goal here (other than to use camel-case notation!) is to preserve backwards compatibility. Unfortunately this isn't 100% possible:
	- DataTable.defaults.columns has been renamed to be DataTable.defaults.column
		- Otherwise it conflicts with aoColumns in the defaults.

Without doubt this is going to be a long process - for example the unit tests and examples need to be completely updated for this change. The JSDoc comments have been updated, so the site should take care of itself for the most part, when released.

In terms of implementation, it is important to note that I have not broken backwards compatibility here - the way it is does is that the current defaults are retained, and a camel-case to Hungarian mapping is automatically generated and then applied to the objects given by the end user. This adds around 0.5K to the size of DataTables, but writing the mapping manually would require at least 3K, and changing DataTables wholesale to camel-case would utterly break backwards compatibility. This is the least 'evil' way to accomplish this. It is important to note that this is a step along the roadmap for DataTables - come v2 Hungarian notation will likely be dropped completely.

One important note to make about this mapping is that if you use camel-case DataTables will copy the value from the camel-case properties to their Hungarian counterparts, so you will end up with additional properties on your source object. As I say, this appears to be to be the least 'evil' option, although still not perfect itself. The challenges of working with legacy software and installs...!
2012-10-07 11:50:29 +01:00
Allan Jardine
93b0c9ede7 Examples: update - bind the 'xhr' event to the table without calling DataTables - no need for that call to be made. 2012-09-02 09:48:45 +01:00
Allan Jardine
660e8cb374 Update - examples: Witht he change in name from mDataProp to mData, this change is now refelected in the examples to encorage mData usage (do remember that mDataProp will still work, but use of mData is encoraged). 2012-08-08 22:30:26 +01:00
Allan Jardine
9c51aa0ad7 New: xhr event 2012-08-08 16:27:42 +01:00
Allan Jardine
1fa1ef94a8 Update - examples: Update XRegExp to 1.5.1 with IE8 fix 2012-04-16 18:42:21 +01:00
Allan Jardine
b6709c017b Examples: When the node to show the XHR return is not available, don't try to use it 2012-03-03 13:49:13 +00:00
Allan Jardine
019b235b0e Examples: Fix: SyntaxHighlighter was having problems with copy and paste in webkit browsers - fix pushed to syntax highlighter here: https://github.com/alexgorbatchev/SyntaxHighlighter/pull/86 - this is the commit of that fix to the local copy 2012-01-28 10:08:43 +00:00
Allan Jardine
94976c2554 Fix: IE7 issue with xregexp 2012-01-07 16:58:01 +00:00
Allan Jardine
486315a25c Fix: Was only binding xhr event where there was more than one table! Doh! 2011-12-06 17:09:39 +00:00
Allan Jardine
af16d8016c Don't initialise the xhr listener if there is no DataTable on the page 2011-11-08 10:13:03 +00:00
Allan Jardine
9b0bc1bbf9 New: Update SyntaxHighlighter to include a submit button to run the example directly in JSBin (live.datables.net) 2011-11-01 12:09:08 +00:00
Allan Jardine
1d2db4d5e9 New: All examples which show Ajax requests now show the JSON response from the server (highlighted to be readiable JSON formatting) and the responses shown will update with each additional request. The idea is to make the formatting that DataTables expects / can cope with more obvious 2011-09-10 08:53:02 +01:00
Allan Jardine
a444026985 New: In the syntax highlighting also pickout DataTables' API methods and link them to the reference page 2011-09-05 19:24:18 +01:00
Allan Jardine
f788dd28d3 New: Syntax highlighting for the examples and provide a link for DataTables initialisation options to the reference page 2011-09-05 19:14:02 +01:00
Allan Jardine
f172ef5383 New: Significant change to how data is handled by DataTables. DataTables now has the ability to deal with complex objects as data sourced, which is particularly useful for dealing with Ajax data, and other data which doesn't belong in the visible table (db IDs for example). See the examples/ajax/ files that are in this commit for examples on how this works. More unit tests and further tidy up to come. Detailed examples will also be added in future - the current examples are mainly for testing 2011-04-19 19:35:33 +01:00
Allan Jardine
70305b1831 Updated: Move the various server-side example support scripts into the server_side/scripts directory 2011-04-17 10:54:14 +01:00
Allan Jardine
07b3557c53 Fix: With all warnings enabled in PHP, there were certain DataTables initialisations which could trigger warnings in the example server porecessing script. 2011-03-01 21:44:43 +00:00
Allan Jardine
1e9436cc5e Updated: jEditable source to v1.7.1 2011-01-18 19:02:33 +00:00
Allan Jardine
eec881b8ac Fixed: Remove the 'sNames' parameter that was introduced for server-side processing in 1.7.4. The parameter 'sColumns' actually performs exactly this task already. Doh. Also update the example PHP to take this into account - 3218 2010-10-31 17:16:35 +00:00
Allan Jardine
a6365b3f69 Updated: Server-side processing script for column re-ordering has been updated to take account of sNames parameter which is sent in from DataTables, and also brought up to date with the main server-side processing script.
Changed: From the previous commit sNames sent from the client to server is now a comma seperated list of sNames and is always sent regardless of if names are given or not. This matches the sName formatting for the server-to-client return.
2010-10-29 08:48:13 +01:00
Allan Jardine
af94c4b217 Updated: server-side processing example script updated to use json_encode, so this version will now require PHP 5.2 or newer. A version for older PHP versions can be found here: http://datatables.net/development/server-side/php_mysql4 2010-10-07 18:09:04 +01:00
Allan Jardine
35b7655bec Fixed: server-side processing demo script now takes account of strings which new line characters 2010-10-07 17:53:48 +01:00
Allan Jardine
ced3b96264 Fixed: Themeroller 1.8 introduced a few changes from 1.7 (main fg-button* > ui-button) which was causing 1.8 themes to not show correctly. This release updates DataTables to use ThemeRoller 1.8 themes by default, but retains 1.7 backwards compatibility for now (to be removed in future) - 1559 2010-08-22 13:48:20 +01:00
Allan Jardine
9fcaccb570 Initial commit - DataTables 1.7.0 2010-08-17 08:42:13 +01:00