4 Commits

Author	SHA1	Message	Date
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	ede9f77de8	Updated: Reliability of unit tests in non-webkit browsers	2010-12-15 21:22:22 +00:00
Allan Jardine	7f04b7ffb5	Fixed: When infinite scrolling, DataTables would clear it's internal cache of rows on every draw, when server-side processing was being used. This could result in fnGetNodes giving only a subset of the nodes which are visible, rather than the full set (which it now does).	2010-09-15 10:29:03 +01:00
Allan Jardine	fde6ba858a	New: Infinite scrolling! Building on the scrolling feature set that was introduced with 1.7, you can now have DataTables do infinite scrolling (bScrollInfinite: true), where data is loaded dynamically as and when needed by the user's interaction with scrolling. Infinite scrolling can be used by all DataTables' supported data sources without modification. ... New: The distance from the end of the current scrolling container before new data is added (with infinite scrolling) can be controlled with iScrollLoadGap (which is a numeric value in pixels). New: Example (basic_init/scrolling_y_infinite.html) to show how infinite scrolling can be used. Fixed: iDraw was not being incremented for a draw that did not use server-side processing.	2010-09-05 10:21:26 +01:00