Differences

This shows you the differences between two versions of the page.

--- wiki:cell_editing [2009/10/05 15:18]
tony
+++ wiki:cell_editing [2017/12/12 17:18] (current)
admin
@@ Line 1: / Line 1: @@
 ====== Cell Editing ======
-cellEditing supports key navigation and editing individual cells, with the following behaviour:
+Cell editing provides the frontend user with functionality to change the contents of one single cell from a row and then the developer has the abbility to handle the changed data by AJAX or in a jqGrid cell edit event (see below).
+Cell Editing supports key navigation and editing individual cells, with the following behaviour:
     * When we click on a cell that is not editable, the cell is selected and we can use the up, down, left and right keys to navigate through the cells.
     * If we move to a cell that is editable, we can press [Enter] to edit the cell. The cell is saved when we press [Enter] again, when we press [Tab], or when we click on another cell. If we press [ESC], the cell is not saved. When editing a cell, the cursor keys move only within the cell.
     * When we click on cell that is editable, then we go directly into edit mode.
+    * The cell is not editable if it has a class 'not-editable-cell', instead that in colModel is set to be editable
 ===== Installation =====
 In order to use this module you should mark the Cell editing and Common when you download the grid. For more information refer to [[Download]].\\
-For Developers - this is the grid.celledit.js in the src directory.
+For Developers of the JQuery plugin itself they can use the grid.celledit.js file in the src directory.
 The properties, events and methods used in cell editing are a sub-set of those of the parent grid, and described below
@@ Line 17: / Line 21: @@
 ^Property^Type^Description^Default^
 |cellEdit|boolean|Enables (disables) cell editing. When this option is set to true, onSelectRow event can not be used, and hovering is disabled (when mouseover on the rows).|false|
-|cellsubmit|string|Determines where the contents of the cell are saved - can have two values: 'remote' or 'clientArray'. \\ If //remote// the content is immediately saved to the server using the cellurl property, via ajax. The rowid and the cell content are added to the url as name:value pairs. For example, if we save the cell named mycell,{id: rowid, mycell: cellvalue} is added to the url. \\ If 'clientArray', no ajax request is made and the content of the changed cell can be obtained via the method getChangedCells |remote|
+|cellsubmit|string|Determines where the contents of the cell are saved - can have two values: 'remote' or 'clientArray'. \\ If //remote// the content of the cell if anything is changed is immediately saved to the server using the cellurl property, via ajax. The rowid and the cell content are added to the url by default. If you have the "mtype" setting set to post, the key value pears will be send as post variables. For example, if we save the cell named mycell,{id: rowid, mycell: cellvalue} is added to the url. \\ If cellsubmit is 'clientArray', no ajax request is made and the content of the changed cell can be obtained via the method getChangedCells or thru a event. |remote|
-|cellurl|string|the url where the cell is to be saved|null|
+|cellurl|string|the url where the cell is to be saved. You need to set this only when you use cellsubmit as 'remote'.|null|
+|ajaxCellOptions|object|This option allow to set global ajax settings for the cell editiing when we save the data to the server. Note that with this option is possible to overwrite all current ajax setting in the save request including the complete event.|empty object|
+==== Examples ====
+When using the 'remote' setting you could add these lines to your grid configuration:
+<code javascript>
+{
+	'cellEdit' : true,
+	'cellsubmit' : 'remote',
+	'cellurl' : '/url/to/handling/the/changed/cell/value'
+}
+</code>
+When your are using 'clientArray' as cellsubmit setting, only these settings are important:
+<code javascript>
+{
+	'cellEdit' : true,
+	'cellsubmit' : 'remote'
+}
+</code>
 ===== Events =====
@@ Line 33: / Line 59: @@
 ^Event^Parameters^Description^
 |afterEditCell|rowid, cellname, value, iRow, iCol|applies only to a cell that is editable; this event fires after the edited cell is edited - i.e. after the element is inserted into the DOM|
+|afterRestoreCell|rowid, value, iRow, iCol|applies only to a cell that is editable; this event fires after calling the method restoreCell or the user press ESC leaving the changes|
 |afterSaveCell|rowid, cellname, value, iRow, iCol|applies only to a cell that is editable; this event fires after the cell has been successfully saved. This is the ideal place to change other content.|
 |afterSubmitCell|serverresponse, rowid, cellname, value, iRow, iCol|applies only to a cell that is editable; this event Fires after the cell and other data is posted to the server Should return array of type [success(boolean),message] when return [true,""] all is ok and the cellcontent is saved [false,"Error message"] then a dialog appears with the "Error message" and the cell content is not saved. servereresponse is the response from the server. To use this we should use serverresponse.responseText to obtain the text message from the server.|
@@ Line 41: / Line 68: @@
 |formatCell|rowid, cellname, value, iRow, iCol|applies only to a cell that is editable; this event allows formatting the cell content before editing, and returns the formatted value|
 |onSelectCell|rowid, celname, value, iRow, iCol|applies only to cells that are not editable; fires after the cell is selected|
+|serializeCellData|postdata|If set this event can serialize the data passed to the ajax request when we save a cell. The function should return the serialized data. This event can be used when a custom data should be passed to the server - e.g - JSON string, XML string and etc. To this event is passed the data which will be posted to the server|
+==== Event calling stack ====
+Depending on your cellSubmit setting set to 'remote' or 'clientArray' the following events will be fired in the following order:
+=== cellSubmit setting 'remote' ===
-Below is the order of which the events are called when the cellsubmit option is 'remote'
+  - **formatCell** (//rowid, cellname, value, iRow, iCol//) : You can change the cell value here which will be used in the edit mode
+  - **beforeEditCell** (//rowid, cellname, value, iRow, iCol//) : Just before the cell jumps into edit mode this event is fired
+  - **afterEditCell** (//rowid, cellname, value, iRow, iCol//) : Just after the input element is created this event will be fired
+  - **beforeSaveCell** (//rowid, cellname, value, iRow, iCol//) : Fires before the cell is saved, you can save the value here which is send to the server.
+  - **beforeSubmitCell** (//rowid, cellname, value, iRow, iCol//) : Fires before value will be send to the server, you can add extra parameters here to the request by returning an array
+  - **afterSubmitCell** (//serverresponse, rowid, cellname, value, iRow, iCol//) : Fires only if saving cell is succesful, you can return a error message here that causes a dialog with the message
+  - **afterSaveCell** (//rowid, cellname, value, iRow, iCol//) : Fires when the value of the cell is saved
+  - **errorCell** (//serverresponse, status//) : Fires when a server error is occured (like: 403, 404, 500, etc)
+  - **onSelectCell** (//rowid, celname, value, iRow, iCol//) : Fires when a cell is not editable
-if a cell is editable then \\
+=== cellSubmit setting 'clientArray' ===
-. formatCell - format and the value of the cell can be changed before editing \\
-. beforeEditCell \\
-. afterEditCell - after the input element is created \\
-. beforeSaveCell  \\
-. beforeSubmitCell  \\
-if the submit is successfully \\
-. afterSubmitCell \\
-. afterSaveCell \\
-else \\
-. errorCell \\
-else if the cell is not editable \\
-. onSelectCell \\
-If the cellsubmit is 'clientArray' then \\
+  - **formatCell** (//rowid, cellname, value, iRow, iCol//) : You can change the cell value here which will be used in the edit mode
-if a cell is editable then \\
+  - **beforeEditCell** (//rowid, cellname, value, iRow, iCol//) : Just before the cell jumps into edit mode this event is fired
-. formatCell - format and the value of the cell can be changed before editing \\
+  - **afterEditCell** (//rowid, cellname, value, iRow, iCol//) : Just after the input element is created this event will be fired
-. beforeEditCell \\
+  - **beforeSaveCell** (//rowid, cellname, value, iRow, iCol//) : Fires before the cell is saved by user
-. afterEditCell - after the input element is created \\
+  - **beforeSubmitCell** (//rowid, cellname, value, iRow, iCol//) : You can save the value somewhere here
-. beforeSaveCell \\
+  - **afterSaveCell** (//rowid, cellname, value, iRow, iCol//) : Fires when the value of the cell is succesfully saved by beforeSubmitCell
-. beforeSubmitCell \\
+  - **onSelectCell** (//rowid, celname, value, iRow, iCol//) : Fires when a cell is not editable
-. afterSaveCell \\
-else if the cell is not editable \\
-. onSelectCell \\
 ===== Methods =====
@@ Line 83: / Line 109: @@
 ==== How is the data organized ====
 When the cell is edited and the input elements is created we set the following rules: \\
-  * The id of the editable cell element is constructed as 'iRow_'+ the name from the colModel array - where the iRow is the index of the row (not rowid) Example if we edit cell with index=20 and eitable element has name 'myname' (from colModel) then the id becomes 20_myname.
+  * The id of the editable cell element is constructed as 'iRow_'+ the name from the colModel array - where the iRow is the index of the row (not rowid) Example if we edit cell with index=20 and editable element has name 'myname' (from colModel) then the id becomes 20_myname.
-  * The name of the editable element is constructed from the name of the colModel array - propery - name
+  * The name of the editable element is constructed from the name of the colModel array - property - name
 ==== What is posted to the server? ====

Differences

Navigation

Search

Toolbox

QR Code