CoreMedia Content Cloud v11 Upgrade Guide / Version 2110
Table Of Contents
When we started with Ext JS 3.4, Configs were a simple concept: To specify the properties of some object to
create, plain JavaScript object literals are used – not really JSON, because their values may be more complex.
These objects are passed around and eventually used to derive a class to instantiate, in Ext 3.4 based on their
xtype
property. The class constructor is then called with the Config object and essentially
"applies" (copies) all properties onto itself.
For example, you could specify a button with a label as a config object and then let Ext create the actual
Ext.Button
instance from that Config:
var buttonCfg = { xtype: "button", label: "Click me!" }; var button = Ext.create(buttonCfg); console.log(button.label); // logs "Click me!"
Example 7.5. Ext config example
So in Ext 3.4, Configs were nothing but properties/fields of the target class which were "bulk applied" through a JSON-like object.