Allan Jardine
6d140835a9
Update: Examples syntax highlighter needs to use on rather than live
2013-02-01 10:03:26 +00:00
Allan Jardine
0e8e0d6793
Update: Updating to jQuery 1.9
2013-02-01 10:02:57 +00:00
Allan Jardine
076744a84c
Merge branch 'master' of github.com:DataTables/DataTables
2012-12-21 09:36:10 +00:00
Allan Jardine
86cc702539
Fix:Server-side scripts security flaw - The example server-side scripts
...
had an injection vunrebility where paging and sorting could be exploited
- 13314. DataTables 1.9.4 has been reissued with these fixes.
2012-12-21 09:33:41 +00:00
Allan Jardine
70e784d84a
Merge pull request #137 from DukeAstar/patch-1
...
Fix backward compatibility with mDataProp = null
2012-12-07 13:46:19 -08:00
DukeAstar
d9bb6b63cd
Fix backward compatibility with mDataProp = null
2012-12-07 22:32:41 +01:00
Allan Jardine
c74db5aee6
Merge pull request #135 from Tiax/master
...
Fix: The sorting 'none' class was not being correctly assigned to columns which could not be sorted - 12736.
2012-11-23 08:09:08 -08:00
Tiax
a528bbb6b6
Applying proper CSS classes for sorting to columns
...
As discussed on the forums here: http://datatables.net/forums/discussion/12736/setting-sortable-with-aocolumndefs-glitched
2012-11-23 10:49:26 +01:00
Allan Jardine
a5c80d4711
Merge pull request #133 from cirosantilli/patch-1
...
Update examples/api/multi_filter.html
2012-11-06 03:13:57 -08:00
Ciro Duran Santilli
f78ce70580
Update examples/api/multi_filter.html
...
minor improvement: calculate index based on the element's parent th.
this is better because it allows to have some columns that are not searchable (like when the first row is a checkbox row)
2012-11-06 09:08:09 -02:00
Allan Jardine
36fc3cc92e
Update: If aLengthMenu is given, but iDisplayLength is not, DataTables used to default to using the built in iDisplayLength option. However, this lead to a bit of confusion as to why the first value from aLengthMenu was not used (issue #61 and numerous forum posts). This commit changes that behaviour - the first value from aLengthMenu is used, if iDisplayLength is not given as well.
2012-11-02 09:28:06 +00:00
Allan Jardine
823e64cccb
Dev: A bit of love for hte type detection functions. Tidy them up and improve the comments.
2012-11-02 08:43:37 +00:00
Allan Jardine
33d3667bbe
Update: Much smaller numeric type detection method, based on isNumeric in jQuery. Also a whole lot faster.
2012-11-02 08:33:07 +00:00
Allan Jardine
a073515b20
Update: fnUpdate is now inline with the changes to how data can be added to the table. Rather than taking a copy of the data source, it will simply assign the data given to the row (if it is given for the row) and apply it. Documentation comments update as well.
2012-11-01 21:56:02 +00:00
Allan Jardine
065c2cc66b
Fix: Filtering wasn't correctly applying the type adjustments needed for the global filter. For example this meant that html was not stripped from 'html' type columns, resulting in filtering being done on html tags/attributes as well as the content.
2012-11-01 21:45:48 +00:00
Allan Jardine
b56f3619cb
Dev: Remove padding on code when in the syntax highlighter
2012-11-01 21:45:26 +00:00
Allan Jardine
46d483d055
Tests: With the change for the state saving into localStorage we need to update the state destroy in the unit tests
2012-10-31 18:12:22 +00:00
Allan Jardine
94f06473c6
New: DataTables now uses HTML5 localStorage by default for state saving. This has a number of advantages over cookies, the first of which is that we are no longer limited to 4KiB in size. It also makes HTTP requests faster since they aren't included in the HTTP transport. Better yet, the removal of the cookie code reduces the DataTables minified size by 1.5K (1573 bytes). It must be noted that this does mean that IE6/7 don't, by default, work with state saving in DataTables. If support for those browsers is required, then fnStateSaveCallback and fnStateLoadCallback must be used by the developer to define their own state saving methods.
...
Removed: fnCookieCallback (cookieCallback) - This is now irrelevant since DataTables does not state save in cookies by default.
Removed: sCookiePrefix (cookiePrefix) - This is now irrelevant since DataTables does not state save in cookies by default.
Depreciated: iCookieDuration (cookieDuration) - Since DataTables does not use cookies for state saving by default the name of this parameter is now incorrect. The new parameter `stateDuration` should be used instead, although the old parameter is still supported. It will be removed in the next major version of DataTables.
2012-10-31 18:09:41 +00:00
Allan Jardine
c883cdac54
Dev: Fix issue with the moved oInit defaults copy - couldn't get a reference to an exisiting DataTable
2012-10-31 15:42:09 +00:00
Allan Jardine
0ff0858734
Dev: Fix logic check for passing data to the updated _fnCreateTr method
2012-10-31 15:39:10 +00:00
Allan Jardine
5209e2f058
Dev: Removed the _fnGatherData method, replacing it with _fnAddTr and slightly updated _fnAddData / _fnCreateTr. This means that the new API add add existing TR element if needed, but more importantly it reduces code duplication and makes the code size smaller (almost 1K - 967 bytes exactly, minified). Must confess I was really hoping it would be more, but every little helps...
2012-10-31 14:56:34 +00:00
Allan Jardine
3ac3cedf53
Fix: When sorting numerically, '-' and '' should be treated as -Infinity rather than as 0, since negative numbers could also be used int he column and this would split the numbers.
2012-10-30 21:05:15 +00:00
Allan Jardine
ec0556b4f6
Updated: Changing the formatting that DataTables uses for the version numbers to be compatible with semver ( http://semver.org/ ). The impact is minimal (unless you are parsing the version for the final part in dev builds). The change is to use a dash ('-') at the end of the version string for a non-release build, rather than a dot.
2012-10-28 16:39:35 +00:00
Allan Jardine
e7e0fb83f0
Fix: Make was building invalid JSON files for the component.json file
2012-10-28 16:35:57 +00:00
Allan Jardine
eafd70f53a
Dev fix: When updating the parameters for lack of hungraian notation, I renamed 'iDeferLoading' as 'deferLoading' which broke server-side processing...
2012-10-28 16:34:11 +00:00
Allan Jardine
88e12aabfe
Merge branch 'master' of github.com:DataTables/DataTables
2012-10-26 08:09:04 +01:00
Allan Jardine
8eb8c90627
Dev - Build latest changes
2012-10-26 08:04:14 +01:00
Allan Jardine
e89958cb45
Fix docs: Example for mRender has a syntax error
2012-10-26 08:02:59 +01:00
Allan Jardine
59782cf6ab
Fix: Add -dev to the version number
2012-10-25 08:46:55 +02:00
Allan Jardine
8948ed24e1
Merge pull request #127 from rikkert/patch-1
...
Fix component.json trailing comma and update version property
2012-10-24 23:46:09 -07:00
Ramiro Rikkert
8c1ab09381
Fix component.json
...
Two small fixes that will prevent bower from crashing:
- use a [semver](http://semver.org/ ) for 'version' property
- remove syntax error in main array property
2012-10-23 09:03:21 +03:00
Allan Jardine
cab0c534f1
Fix - core: Stripe removal was broken - it was stripping the classes from only the first row rows, rather than all of them, which was wrong. This was unfortunatly introduced in 1.9.4 and there weren't any unit tests to catch it. There are now, and I've rewritten the code that wil remove existing stripe classes. Its now much smaller and should be a little faster. Now it only checks the first row to see if it has any exisiting stripe classes, which is good enough. The smallest this could could be would be a simple removeClass, but that may result in significant overhead which really isn't needed in cases where there are no exisiting stripe classes.
2012-10-19 15:31:35 +01:00
Allan Jardine
8e1068e603
Dev fix: Fix issue highlighted by JSHint - The DataTable object is addressed in the private methods so it needs to be defined before them, but the contracturo needs to come after the priavte methods!
2012-10-07 18:13:16 +01:00
Allan Jardine
0e3a60b52f
Dev fix: Variable name oSettings was incorrect
2012-10-07 18:11:54 +01:00
Allan Jardine
f7dddabfa3
Fix: Trailing comma
2012-10-07 18:11:41 +01:00
Allan Jardine
de935de4c6
Merge branch 'master' of github.com:DataTables/DataTables
2012-10-07 18:08:56 +01:00
Allan Jardine
ab454c1c33
Fix: In _fnExtend there was a bug where a variable referenced a 'locally global' (for lack of a better term) variable rather than the in function variable that it should be have. Got away with this since _fnExtend is only used for one thing at the moment, but it was wrong. Now fixed.
...
Update - Performance / Memory: The functions that DataTables uses are not instance based, they are locally scoped, but they were included in the DataTable constructore, which meant that every time you create a new 'instance' of DataTables ($().dataTable()) it would create these functions in that scope again and again. That's completely pointless since we only need them once, so moving them outside the constructor helps both performance and memory (not huge, but very little helps!).
2012-10-07 18:02:38 +01:00
Allan Jardine
8a6737520a
Merge pull request #123 from timtucker/patch-34
...
Dev: Fix introduced issue
2012-10-07 07:12:37 -07:00
Tim Tucker
2b35b262cb
Update media/src/api/api.static.js
...
Variable initialization was wrong in the prior pull (should have been iThat, not sThat)
2012-10-07 09:11:10 -03:00
Allan Jardine
f420f1462b
Merge pull request #117 from timtucker/patch-29
...
Dev: Modify how DataTables builds the filtering regular expressions to simplify.
2012-10-07 04:31:06 -07:00
Allan Jardine
ec10497217
Dev: Update generated file from the marges made recently
2012-10-07 12:23:24 +01:00
Allan Jardine
7a388a0a76
Merge branch 'master' of github.com:DataTables/DataTables
2012-10-07 12:23:07 +01:00
Allan Jardine
09a9976907
Dev: Trivial code styling change
2012-10-07 12:22:18 +01:00
Allan Jardine
7bcd2955ff
Merge pull request #116 from timtucker/patch-28
...
Dev: Remove unused variable in _fnDraw
2012-10-07 04:15:17 -07:00
Allan Jardine
76507795ed
Merge pull request #109 from timtucker/patch-22
...
Update media/src/core/core.ajax.js
2012-10-07 04:14:12 -07:00
Allan Jardine
be6fc4185d
Merge pull request #106 from timtucker/patch-19
...
Dev: Simplify language handling of start number for infinite scrolling
2012-10-07 04:12:23 -07:00
Allan Jardine
8cabf6f830
Merge pull request #107 from timtucker/patch-20
...
Dev: Different algorithm for fnVersionCheck
2012-10-07 04:10:43 -07:00
Allan Jardine
542066100a
Merge pull request #115 from timtucker/patch-27
...
Update media/src/core/core.draw.js
2012-10-07 04:09:27 -07:00
Allan Jardine
8b6e3fe264
Merge pull request #108 from timtucker/patch-21
...
Fix: Update string sorting to correctly sort undefined values.
2012-10-07 04:08:40 -07:00
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
