Clear Up
SharpKit Reference

AbstractStoreConfig Class


Base Types




Name Description
autoLoad If data is not specified, and if autoLoad is true or an Object, this store's load method is automatically called after creation. If the value of autoLoad is an Object, this Object will be passed to the store's load method. Defaults to false.
autoSync True to automatically sync the Store with its Proxy after every edit to one of its Records. Defaults to false. Defaults to: false
batchUpdateMode Sets the updating behavior based on batch synchronization. 'operation' (the default) will update the Store's internal representation of the data after each operation of the batch has completed, 'complete' will wait until the entire batch has been completed before updating the Store's data. 'complete' is a good choice for local storage proxies, 'operation' is better for remote proxies, where there is a comparatively high latency. Defaults to: "operation"
fields This may be used in place of specifying a model configuration. The fields should be a set of configuration objects. The store will automatically create a with these fields. In general this configuration option should only be used for simple stores like a two-field store of ComboBox. For anything more complicated, such as specifying a particular id property or associations, a should be defined and specified for the model config.
filterOnLoad If true, any filters attached to this Store will be run after loading data, before the datachanged event is fired. Defaults to true, ignored if remoteFilter is true Defaults to: true
filters Array of Filters for this store. Can also be passed array of functions which will be used as the filterFn config for filters:
filters: [
            function(item) {
            return item.internalId > 0;
To filter after the grid is loaded use the filterBy function.
listeners A config object containing one or more event handlers to be added to this object during initialization. This should be a valid listeners config object as specified in the addListener example for attaching multiple handlers at once. DOM events from Ext JS Components While some Ext JS Component classes export selected DOM events (e.g. "click", "mouseover" etc), this is usually only done when extra value can be added. For example the DataView's itemclick event passing the node clicked on. To access DOM events directly from a child element of a Component, we need to specify the element option to identify the Component property to add a DOM listener to:
new Ext.panel.Panel({
            width: 400,
            height: 200,
            dockedItems: [{
            xtype: 'toolbar'
            listeners: {
            click: {
            element: 'el', //bind to the underlying el property on the panel
            fn: function(){ console.log('click el'); }
            dblclick: {
            element: 'body', //bind to the underlying body property on the panel
            fn: function(){ console.log('dblclick body'); }
model Name of the Model associated with this store. The string is used as an argument for Ext.ModelManager.getModel.
proxy The Proxy to use for this Store. This can be either a string, a config object or a Proxy instance - see setProxy for details.
remoteFilter True to defer any filtering operation to the server. If false, filtering is done locally on the client. Defaults to: false
remoteSort True to defer any sorting operation to the server. If false, sorting is done locally on the client. Defaults to: false
sortOnLoad If true, any sorters attached to this Store will be run after loading data, before the datachanged event is fired. Defaults to true, igored if remoteSort is true Defaults to: true
storeId Unique identifier for this store. If present, this Store will be registered with the, making it easy to reuse elsewhere. Note that when store is instatiated by Controller, the storeId will be overridden by the name of the store.
© Copyright 2005-2011 SharpKit. All rights reserved.