jQuery Grid Plugin - jqGrid

Hello Tonny,

you are right of cause, that one could overwrite complete function in all $.ajax requests with respect of $.jgrid.ajaxOptions, ajaxEditOptions or ajaxso parameters. But on the other side if somebody does so, he’ll receive problem of using internal jqGrid structures. In complete function inside of createEl in grid.common.js for example one needs use options and other variable in the scope.

The main idea of my suggestion is very easy. With respect of custom serialization/deserialization functions one could change paradigm of jqGrid usage on the side of backend services. Currently one has to provide on the backend server services providing data for jqGrid in a special format prepared for jqGrid. If you allow to use custom serialization and destabilization functions, if would be possible use many existing backend services and convert data for jqGrid before and after $.ajax requests. The conversion can de done on the client side, without any additional requirement to the backend! It could be important for lot of scenarios of jqGrid usage.

Functions serializeGridData, serializeRowData, serializeEditData from v.3.6 provide serialization, but I found no deserialization functions. There are exists also errorfunc, errorTextFormat, which are very useful for decode error messages provided by server.

Why not provide functions like deserializeGridData etc., which could convert data send from server (responseText) to format needed for jqGrid? For example, for conversion from JSON format to HTML fragment (<select>…</select>) like in the case of dataUrl?

Best regards

Oleg

Thank you very much, Tonny!

Oleg

Hi Tony,

I tested buildSelect feature only in the case of edittype: 'select' and editoptions: { dataUrl:'...', buildSelect: mybuildSelectFunction}. There is a small problem which can be easy fixed: mybuildSelectFunction will be called two times: first expected in line 326 of grid.common.js (var b = options.buildSelect(data);) and another time unexpected with 0 as data in the line 340 (jQuery(elem).attr(options);).

To fix the problem one can add, for example, after the line 326 (var b = options.buildSelect(data);) the following line:

    try { delete options['buildSelect']; } catch (e) { }

Exactly like you do in the line 323:

    try {delete options['dataUrl'];delete options['value'];} catch (e){}

Another small problem, that you add {nd:new Date().getTime()} as a "data" parameter of jQuery.ajax request (see line 321). It force executing jQuery.ajax in IE, but switch off response cashing (see http://www.trirand.com/blog/?page_id=393/bugs/no-caching-of-server-data-because-of-new-nd-property-in-prmnames&value=sf%25members%251%25user1671&search=2&ret=all). To fix the problem I had to use ajaxSelectOptions, which are seen in createEl() as ajaxso. It works now very good, but I am not sure, that setting ajaxSelectOptions: { data: ""} for $.jgrid.defaults is OK for all other places of ajaxSelectOptions usage.

After all such changes everything works perfectly. One more time thanks for the nice feature buildSelect.

Generally I see buildSelect function as a custom deserialization after an ajax request. Version 3.6 has not serialisation for all $.ajax calls. Do you think to implement also custom deserialization? For example, if jqGrid will provide not only serializeGridData, serializeRowData, serializeEditData etc. functions, but also deserializeGridData etc. which convert responseText to format needed for jqGrid, then one could be able fill jqGrid with data not prepared specially for jqGrid. For example, one can call Amazon of twitter services and fill jqGrid with the response data. Is it not interesting?

Best regards

Oleg