I am trying to dynamically set fields to a extjs data store so that I could dynamically create a different grid at run time.
Case A works for me. But when I use as in Case B, the store's proxy hangs on to the previous model and so the grid rendering is messed up.
What is the really the difference between these two?
Case A
Ext.define('FDG.store.reading.FDGDynamicGridStore', {
extend: 'Ext.data.Store'
});
var fdgstore = Ext.create('FDG.store.reading.FDGDynamicGridStore', {
fields: fields,
proxy: {
type: 'memory',
reader: {
type: 'json',
totalProperty: 'tc',
root: 'Result'
}
}
});
fdgstore.loadRawData(output);
this.reconfigure(fdgstore, columns);
Case B
Ext.define('FDG.store.reading.FDGDynamicGridStore', {
extend: 'Ext.data.Store',
proxy: {
type: 'memory',
reader: {
type: 'json',
totalProperty: 'tc',
root: 'Result'
}
}
});
var fdgstore = Ext.create('FDG.store.reading.FDGDynamicGridStore', {
fields: fields
});
fdgstore.loadRawData(output);
this.reconfigure(fdgstore, columns);
Here's what I think is going on:
Ext.data.Model is responsible for holding the proxy and field. Setting those properties on a store is discouraged in favor of MVC, though it was the only way before Ext-JS MVC came along.
A store always uses the proxy associated with the model object. When you pass in a
fields
property to a store, an anonymousModel
is created with a default proxy. You shouldn't use that when specifying proxies. From the docMy suggestion is that you create the models dynamically based on fields so you don't have any of the anonymous Model voodoo.