view release on metacpan or  search on metacpan

root/js/Changes.txt  view on Meta::CPAN

the name 'rn' in colModel

rownumWidth: numeric, Default 25. Determines the width of the row number column
if rownumbers option is set to true.

pagerpos: string, Default 'center'. Determines the position of the pager in the
grid. By default the pager element when created is divided in 3 parts (one part
for pager, one part for navigator buttons and one part for record information)

recordpos: string, Default 'right'. Determines the position of the record
information in the pager.

toolbar now accepts another option: "both". When we set toolbar: [true,"both"]
two toolbars are created -- one on the top of table data and one of the bottom
of the table data. When we have two toolbars then we create two elements (div).
The id of the top bar is constructed like "t_"+id of the grid and the bottom
toolbar the id is "tb_"+id of the grid. In case when only one toolbar is
created we have the id as "t_" + id of the grid, independent of where this
toolbar is created (top or bottom)

gridview: boolean, Default value false. In the previous versions of jqGrid,
including 3.5 alfa, reading a relatively big data sets (Rows >=100 ) caused
speed problems. The reason for this was that as every cell was inserted into
the grid we applied about 5-6 jQuery calls to it. Now this problem is resolved;
we now  insert the entry row at once with a jQuery append. The result is
impressive - about 3-5 times faster. What will be the result if we insert all
the data at once? Yes, this can be done with a help of gridview option when set
to true. The result is a grid that is 5 to 10 times faster. Of course when this
option is set to true we have some limitations. If set to true we can not use
- treeGrid
- subGrid, or 
- afterInsertRow event.
If you do not use these three options in the grid you can set this option to
true and enjoy the speed.

addRowData now is 1-2 times faster because we are using the concept to insert
the row at once

Added jQuery function parse (removed from json2.js module):
jQuery.parse(jsonstring)
To prevent JavaScript hijacking attacks, web application authors are encouraged
to use this function. This returns a JSON representation of the variable. 

Cyclic structures are detected and safely interrupted, but could not be further
restored.
1. The while(1); construct, located at the beginning of JSON text,
2. Comments at the beginning and end of the text.
JSON data providers are encouraged to use one or both of these methods to
prevent data execution. Such JSON response may then look like this: 
while(1);/*{[
    {"name":"safe value 1"},
    {"name":"safe value 2"},
   ...
]}*/
jqGrid uses this function when obtaining a data with datatype:'json', also used
in subGrid.

Added jQuery function stringToDoc: jQuery.stringToDoc(xmlstring). This returns
the xml document of xml string

Added new method: jQuery("#mygrid").updateColumns(); this synchronizes the
width of the headers with the data. Useful when used with table drag and drop.


colModel changes and additions
------------------------------
searchhidden is removed from editrules object

added searchoptions object to define properties, events and other settings when
a search is performed
searchoptions : {
    dataUrl : value,
    dataInit: function,
    dataEvents : array,
    defaultValue: value,
    attr: object,
    searchhidden: boolean,
    sopt: array
}
To summarize - when we want to deal with search we should use the following
options in colModel

search : boolean , // true/false
stype: value, // text/select
searchoptions : object // see above

Note: when the dataUrl is not used for the search type select, the definitions
for the select are taken from editoptions value property - i.e
editoptions:{value:"1:one;2:two",...}. See below for how to use these options in
different search methods.


Added new object formoptions to define various settings in form editing. Also
valid only in this module.

formoptions : {
    elmprefix:value,
    elmsuffix:value,
    rowpos: number,
    colpos:number,
    label: value
}
See below for how to use

The editoptions are extended with the following properties. Valid in all editing
modules editoptions : {
    dataUrl : value, dataInit: function, dataEvents : array, defaultValue:
    value/function,
} See below


Changes in all editing modules
==============================

edittype property is extended with the support of the following input elements:
button, image and file

As described above in all editing modules we can add additional properties and
events to the editing element:

editoptions : {