-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
New: The primary public interface for DataTables' initialisation opti…
…ons 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...!
- Loading branch information
Allan Jardine
committed
Oct 7, 2012
1 parent
65cde4c
commit a0455fa
Showing
19 changed files
with
1,736 additions
and
1,155 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,17 @@ | ||
{ | ||
"sProcessing": "Bitte warten...", | ||
"sLengthMenu": "_MENU_ Einträge anzeigen", | ||
"sZeroRecords": "Keine Einträge vorhanden.", | ||
"sInfo": "_START_ bis _END_ von _TOTAL_ Einträgen", | ||
"sInfoEmpty": "0 bis 0 von 0 Einträgen", | ||
"sInfoFiltered": "(gefiltert von _MAX_ Einträgen)", | ||
"sInfoPostFix": "", | ||
"sSearch": "Suchen", | ||
"sUrl": "", | ||
"oPaginate": { | ||
"sFirst": "Erster", | ||
"sPrevious": "Zurück", | ||
"sNext": "Nächster", | ||
"sLast": "Letzter" | ||
"processing": "Bitte warten...", | ||
"lengthMenu": "_MENU_ Einträge anzeigen", | ||
"zeroRecords": "Keine Einträge vorhanden.", | ||
"info": "_START_ bis _END_ von _TOTAL_ Einträgen", | ||
"infoEmpty": "0 bis 0 von 0 Einträgen", | ||
"infoFiltered": "(gefiltert von _MAX_ Einträgen)", | ||
"infoPostFix": "", | ||
"search": "Suchen", | ||
"url": "", | ||
"paginate": { | ||
"first": "Erster", | ||
"previous": "Zurück", | ||
"next": "Nächster", | ||
"last": "Letzter" | ||
} | ||
} |
Oops, something went wrong.