Skip to main content

JavaScript [ExtJs3]: Loading complex data in EditorGridPanel with Dynamic Combo Box

Grid is always an important widget of any project and many time we find a situation where we have to render the complex data in grid panel.
And another use-case of dynamic combo box where the combo data comes with the record.

To handle a complex object we have to define a new data type. = {
 convert: function(v){
  v.toString = function(){
   return v.display;
  return v;
 type: 'complexdata'

This extended class will take care of dynamic combo box loading. It’s a plugin class so after creating the object we have to add this to “plugins” property of grid panel.
Ext.ux.ComplexDataColumn = Ext.extend(Ext.grid.Column, {
 dataField: 'options',
 displayField: 'display',
 valueField: 'id',
    constructor: function (c) {        
        c.editor = this.buildComboEditor();, c);
 init: function(grid){
  grid.on('beforeedit', function(e){;
  }, this);
 buildComboEditor: function(){
  return new Ext.form.ComboBox({
   typeAhead: true,
   triggerAction: 'all',
   mode: 'local',
   store: new{
    fields: [this.displayField, this.valueField],
    data: []
   displayField: this.displayField

Complex data which we want to load in our EditorGridPanel
var myData = [
 ['3m Co', 71.72, 0.02,  0.03,  
  {id: 1, display: 'option11'}, 
   {id:1, display: 'option11'},
   {id:2, display: 'option12'},
   {id:3, display: 'option13'}
 ['Alcoa Inc', 29.01, 0.42,  1.47,  
  {id: 1, display: 'option21'}, 
   {id:1, display: 'option21'},
   {id:2, display: 'option22'},
   {id:3, display: 'option23'}
 ['Altria Group Inc', 83.81, 0.28,  0.34,  
  {id: 1, display: 'option31'}, 
   {id:1, display: 'option31'},
   {id:2, display: 'option32'},
   {id:3, display: 'option33'}
 ['American Express Company', 52.55, 0.01,  0.02,  
  {id: 1, display: 'option41'}, 
   {id:1, display: 'option41'},
   {id:2, display: 'option42'},
   {id:3, display: 'option43'}
 ['American International Group, Inc.', 64.13, 0.31,  0.49,  
  {id: 1, display: 'option51'}, 
   {id:1, display: 'option51'},
   {id:2, display: 'option52'},
   {id:3, display: 'option53'}
 ['AT&T Inc.', 31.61, -0.48, -1.54, 
  {id: 1, display: 'option61'}, 
   {id:1, display: 'option61'},
   {id:2, display: 'option62'},
   {id:3, display: 'option63'}
 ['Boeing Co.', 75.43, 0.53,  0.71,  
  {id: 1, display: 'option71'}, 
   {id:1, display: 'option71'},
   {id:2, display: 'option72'},
   {id:3, display: 'option73'}
 ['Caterpillar Inc.', 67.27, 0.92,  1.39,  
  {id: 1, display: 'option81'}, 
   {id:1, display: 'option81'},
   {id:2, display: 'option82'},
   {id:3, display: 'option83'}
 ['Citigroup, Inc.', 49.37, 0.02,  0.04,  
  {id: 1, display: 'option91'}, 
   {id:1, display: 'option91'},
   {id:2, display: 'option92'},
   {id:3, display: 'option93'}

Define the store for the grid and define the respective data type. Here we will assign the custom type to complex data field
//Define a store for grid 
var store = new{
 fields: [
    {name: 'company'},
    {name: 'price',      type: 'float'},
    {name: 'change',     type: 'float'},
    {name: 'pctChange',  type: 'float'},
    {name: 'complexData',type:},
    {name: 'options'}

Editor grid panel
//create column for complex data
var complexColumn = new Ext.ux.ComplexDataColumn({
 header   : 'Complex Data', 
 width    : 85, 
 sortable : true, 
 dataIndex: 'complexData'

// create the Grid
var grid = new Ext.grid.EditorGridPanel({
 store: store,
 plugins: [complexColumn],
 columns: [
  {id:'company', header: 'Company', width: 160, sortable: true, dataIndex: 'company'},
  {header: 'Price', width: 75, sortable: true, dataIndex: 'price'},
  {header: 'Change', width: 75, sortable: true, dataIndex: 'change'},
  {header: '% Change', width: 75, sortable: true, dataIndex: 'pctChange'},
 stripeRows: true,
 autoExpandColumn: 'company',
 height: 350,
 width: 600,
 title: 'Array Grid',
 clicksToEdit: 1


Popular posts from this blog

ERROR: Ignored call to 'alert()'. The document is sandboxed, and the 'allow-modals' keyword is not set.

Recently I found this issue while writing code snippet in "JSFiddle". And after searching, found this was happening because of new feature added in "Chrome 46+". But at the same time Chrome doesn't have support for "allow-modals" property in "sandbox" attribute.

Chromium issue for above behavior:

To make it work you have to add "allow-scripts allow-modals" in "sandbox" attribute, and use "window.alert" instead of "alert".

<!-- Sandbox frame will execute javascript and show modal dialogs --> <iframe sandbox="allow-scripts allow-modals" src="iframe.html"> </iframe>

Feature added: Block modal dialog inside a sandboxed iframe.

Feature working Demo page:

JavaScript [ExtJs3]: EditorGridPanel Read-Only (dynamically)

Many time we face the scenerio where we have to make the editor grid read-only dynamically.

Ext.override(Ext.ux.grid.CheckColumn, { editable: true, onMouseDown: function (e, t) { if ( { e.stopEvent(); var me = this, grid = me.grid, view = grid.getView(), index = view.findRowIndex(t), colindex = view.findCellIndex(t), record =; if (!grid.isReadOnly && grid.colModel.isCellEditable(colindex, index)) { record.set(me.dataIndex, ![me.dataIndex]); } } } }); var grid = new Ext.grid.EditorGridPanel({ ... isReadOnly: true, //set to flag to make check column readonly ... }); //to make other column readonly grid.on('beforeedit', function () { return false; });

CSS Specificity

Many time different CSS rules overlap on one or more element. And some people always get confuse about, which rule will take higher priority then other and why? CSS Specificity is the answer of all these kind of questions.
As the name suggest, the CSS rule which is more specific to the element will take higher priority then other. Means something like “#some_id{}” will always take higher priority then “*{}” universal selector.  And if duplicate rules are define then the last rule will be applied to the element.

The following list of selectors is by increasing specificity:
Type selector (e.g., div) and pseudo-elements in selector (e.g., :after) Class selectors (e.g., .some_class), attributes selectors (e.g., [type=”radio”]) and pseudo-class selector (e.g., :hover) Id selectors (e.g., #some_id)

ID takes higher priority then Class, Type and Universal selector (Note: Universal selector has no effect on specificity, see below special conditions). 

If duplicate rules are given, then last…