Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on May 6, 2015
  1. 1.10.8-dev version flag

    authored
Commits on Apr 30, 2015
  1. DataTables 1.10.7 release

    authored
Commits on Apr 15, 2015
Commits on Apr 3, 2015
  1. Release 1.10.6

    authored
Commits on Feb 16, 2015
Commits on Feb 12, 2015
Commits on Feb 10, 2015
  1. Fix - example: Dro the `http` protocol from the i18n CDN file loder e…

    authored
    …xample so it works over https
Commits on Nov 13, 2014
Commits on Nov 11, 2014
Commits on Nov 7, 2014
Commits on Oct 10, 2014
Commits on Oct 9, 2014
  1. Dev: Remove debug line

    authored
Commits on Oct 7, 2014
  1. Dev: npm now requires the `repository` parameter

    authored
    * This fixes DataTables/DataTables #427
Commits on Oct 2, 2014
  1. @malinow

    Add repository to package.json to stop npm error

    malinow authored
    Hi!
    
    When installing DataTables from the repo with npm >v1.2.20, it'll WARN "No repository field." This small patch resolves that. (See https://www.npmjs.org/doc/files/package.json.html#repository or https://stackoverflow.com/questions/16827858/npm-warn-package-json-no-repository-field.)
    
    I hope it's ok to propose this change against DataTables/DataTables -- I couldn't find a `package.json` in DataTablesSrc.
    
    Thank you for your work!!
    M
Commits on Aug 6, 2014
  1. Update to 1.10.3-dev

    authored
Commits on Jul 31, 2014
Commits on Jul 18, 2014
  1. Fix example: Use `search` terminology

    authored
    * See thread 22268
Commits on Jul 15, 2014
  1. Fix docs: Add clarification for `cellData` in `dt-init columns.create…

    authored
    …dCell`
    
    * Based on discussion in thre 22009
Commits on May 6, 2014
Commits on May 1, 2014
Commits on Apr 28, 2014
  1. Fix DataTables/DataTables #306 - jQuery UI class applied to all spans

    authored
    - The class for sorting should only be applied to the sorting indicator
Commits on Apr 25, 2014
  1. Dev: Minor changes to reduce code size.

    authored
    - This commit trims about 400 bytes off the min library size
Commits on Feb 19, 2014
Commits on Feb 17, 2014
Commits on Feb 5, 2014
Commits on Feb 4, 2014
Commits on Dec 11, 2013
Commits on Jul 21, 2013
Commits on Oct 28, 2012
  1. Updated: Changing the formatting that DataTables uses for the version…

    authored
    … 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.
Commits on Oct 7, 2012
  1. New: The primary public interface for DataTables' initialisation opti…

    authored
    …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...!
Something went wrong with that request. Please try again.