MojoX-ValidateHeadLinks
view release on metacpan or search on metacpan
t/assets/js/DataTables-1.9.4/media/js/jquery.dataTables.js view on Meta::CPAN
* over the filtering logic. Each element in this array is a function (parameters
* described below) that is called for every row in the table, and your logic decides if
* it should be included in the filtered data set or not.
* <ul>
* <li>
* Function input parameters:
* <ul>
* <li>{object} DataTables settings object: see {@link DataTable.models.oSettings}.</li>
* <li>{array|object} Data for the row to be processed (same as the original format
* that was passed in as the data source, or an array from a DOM data source</li>
* <li>{int} Row index in aoData ({@link DataTable.models.oSettings.aoData}), which can
* be useful to retrieve the TR element if you need DOM interaction.</li>
* </ul>
* </li>
* <li>
* Function return:
* <ul>
* <li>{boolean} Include the row in the filtered result set (true) or not (false)</li>
* </ul>
* </il>
* </ul>
* @type array
* @default []
*
* @example
* // The following example shows custom filtering being applied to the fourth column (i.e.
* // the aData[3] index) based on two input values from the end-user, matching the data in
* // a certain range.
* $.fn.dataTableExt.afnFiltering.push(
* function( oSettings, aData, iDataIndex ) {
* var iMin = document.getElementById('min').value * 1;
* var iMax = document.getElementById('max').value * 1;
* var iVersion = aData[3] == "-" ? 0 : aData[3]*1;
* if ( iMin == "" && iMax == "" ) {
* return true;
* }
* else if ( iMin == "" && iVersion < iMax ) {
* return true;
* }
* else if ( iMin < iVersion && "" == iMax ) {
* return true;
* }
* else if ( iMin < iVersion && iVersion < iMax ) {
* return true;
* }
* return false;
* }
* );
*/
"afnFiltering": [],
/**
* Plug-in sorting functions - this method of sorting is complimentary to the default type
* based sorting that DataTables does automatically, allowing much greater control over the
* the data that is being used to sort a column. This is useful if you want to do sorting
* based on live data (for example the contents of an 'input' element) rather than just the
* static string that DataTables knows of. The way these plug-ins work is that you create
* an array of the values you wish to be sorted for the column in question and then return
* that array. Which pre-sorting function is run here depends on the sSortDataType parameter
* that is used for the column (if any). This is the corollary of <i>ofnSearch</i> for sort
* data.
* <ul>
* <li>
* Function input parameters:
* <ul>
* <li>{object} DataTables settings object: see {@link DataTable.models.oSettings}.</li>
* <li>{int} Target column index</li>
* </ul>
* </li>
* <li>
* Function return:
* <ul>
* <li>{array} Data for the column to be sorted upon</li>
* </ul>
* </il>
* </ul>
*
* Note that as of v1.9, it is typically preferable to use <i>mData</i> to prepare data for
* the different uses that DataTables can put the data to. Specifically <i>mData</i> when
* used as a function will give you a 'type' (sorting, filtering etc) that you can use to
* prepare the data as required for the different types. As such, this method is deprecated.
* @type array
* @default []
* @deprecated
*
* @example
* // Updating the cached sorting information with user entered values in HTML input elements
* jQuery.fn.dataTableExt.afnSortData['dom-text'] = function ( oSettings, iColumn )
* {
* var aData = [];
* $( 'td:eq('+iColumn+') input', oSettings.oApi._fnGetTrNodes(oSettings) ).each( function () {
* aData.push( this.value );
* } );
* return aData;
* }
*/
"afnSortData": [],
/**
* Feature plug-ins - This is an array of objects which describe the feature plug-ins that are
* available to DataTables. These feature plug-ins are accessible through the sDom initialisation
* option. As such, each feature plug-in must describe a function that is used to initialise
* itself (fnInit), a character so the feature can be enabled by sDom (cFeature) and the name
* of the feature (sFeature). Thus the objects attached to this method must provide:
* <ul>
* <li>{function} fnInit Initialisation of the plug-in
* <ul>
* <li>
* Function input parameters:
* <ul>
* <li>{object} DataTables settings object: see {@link DataTable.models.oSettings}.</li>
* </ul>
* </li>
* <li>
* Function return:
* <ul>
* <li>{node|null} The element which contains your feature. Note that the return
* may also be void if your plug-in does not require to inject any DOM elements
* into DataTables control (sDom) - for example this might be useful when
t/assets/js/DataTables-1.9.4/media/js/jquery.dataTables.js view on Meta::CPAN
*
* @example
* // Currency type detection plug-in:
* jQuery.fn.dataTableExt.aTypes.push(
* function ( sData ) {
* var sValidChars = "0123456789.-";
* var Char;
*
* // Check the numeric part
* for ( i=1 ; i<sData.length ; i++ ) {
* Char = sData.charAt(i);
* if (sValidChars.indexOf(Char) == -1) {
* return null;
* }
* }
*
* // Check prefixed by currency
* if ( sData.charAt(0) == '$' || sData.charAt(0) == '£' ) {
* return 'currency';
* }
* return null;
* }
* );
*/
"aTypes": [],
/**
* Provide a common method for plug-ins to check the version of DataTables being used,
* in order to ensure compatibility.
* @type function
* @param {string} sVersion Version string to check for, in the format "X.Y.Z". Note
* that the formats "X" and "X.Y" are also acceptable.
* @returns {boolean} true if this version of DataTables is greater or equal to the
* required version, or false if this version of DataTales is not suitable
*
* @example
* $(document).ready(function() {
* var oTable = $('#example').dataTable();
* alert( oTable.fnVersionCheck( '1.9.0' ) );
* } );
*/
"fnVersionCheck": DataTable.fnVersionCheck,
/**
* Index for what 'this' index API functions should use
* @type int
* @default 0
*/
"iApiIndex": 0,
/**
* Pre-processing of filtering data plug-ins - When you assign the sType for a column
* (or have it automatically detected for you by DataTables or a type detection plug-in),
* you will typically be using this for custom sorting, but it can also be used to provide
* custom filtering by allowing you to pre-processing the data and returning the data in
* the format that should be filtered upon. This is done by adding functions this object
* with a parameter name which matches the sType for that target column. This is the
* corollary of <i>afnSortData</i> for filtering data.
* <ul>
* <li>
* Function input parameters:
* <ul>
* <li>{*} Data from the column cell to be prepared for filtering</li>
* </ul>
* </li>
* <li>
* Function return:
* <ul>
* <li>{string|null} Formatted string that will be used for the filtering.</li>
* </ul>
* </il>
* </ul>
*
* Note that as of v1.9, it is typically preferable to use <i>mData</i> to prepare data for
* the different uses that DataTables can put the data to. Specifically <i>mData</i> when
* used as a function will give you a 'type' (sorting, filtering etc) that you can use to
* prepare the data as required for the different types. As such, this method is deprecated.
* @type object
* @default {}
* @deprecated
*
* @example
* $.fn.dataTableExt.ofnSearch['title-numeric'] = function ( sData ) {
* return sData.replace(/\n/g," ").replace( /<.*?>/g, "" );
* }
*/
"ofnSearch": {},
/**
* Container for all private functions in DataTables so they can be exposed externally
* @type object
* @default {}
*/
"oApi": {},
/**
* Storage for the various classes that DataTables uses
* @type object
* @default {}
*/
"oStdClasses": {},
/**
* Storage for the various classes that DataTables uses - jQuery UI suitable
* @type object
* @default {}
*/
"oJUIClasses": {},
/**
* Pagination plug-in methods - The style and controls of the pagination can significantly
* impact on how the end user interacts with the data in your table, and DataTables allows
* the addition of pagination controls by extending this object, which can then be enabled
* through the <i>sPaginationType</i> initialisation parameter. Each pagination type that
( run in 0.617 second using v1.01-cache-2.11-cpan-2398b32b56e )