有人可以告诉我在extjs4.1中使用initComponent
函数的用途吗?请提供一个例子
由于
答案 0 :(得分:11)
此方法类似于组件的constructor
。它由真constructor
调用,是一个非常好的钩点,可以自定义组件的初始化(如名称中所述!)。
除非在极少数情况下,您应该覆盖initComponent
而不是constructor
,因为已经进行了更基本的初始化。最值得注意的是,传递给构造函数的配置对象已经合并到了对象中。
假设您要自定义组件的配置,例如设置其width
。如果您尝试在构造函数中执行此操作,则必须首先检查我们是否已经传递了配置对象(以避免尝试在undefined
上设置属性),并且您将拥有覆盖配置对象,这是不好的做法。如果在this
中设置选项,则可能会被配置对象覆盖。如果更改config对象中的值,则修改该对象,从而打破调用代码的期望(即重用config对象将产生意外结果)。在initComponent
中,值始终为this.width
,您无需担心配置。
另一个有趣的观点是initComponent
是创建子组件(用于容器),存储,视图,模板等的地方。因此,在调用超类initComponent
方法之前,您可以对这些方法采取行动,确保它们尚未被使用或需要(例如,添加项目,创建商店等)。另一方面,一旦调用了super方法,就可以保证所有这些依赖项都已创建并实例化。因此,这是向依赖项添加侦听器的好地方,例如。
话虽如此,请记住initComponent
中没有进行渲染。已创建和配置子组件,但尚未创建其DOM元素。要影响渲染,您必须使用渲染相关事件或查找afterRender
或onRender
方法......
以下是一个说明性摘要:
constructor: function(config) {
// --- Accessing a config option is very complicated ---
// unsafe: this may be changed by the passed config
if (this.enableSomeFeature) { ... }
// instead, you would have to do:
var featureEnabled;
if (config) { // not sure we've been passed a config object
if (Ext.isDefined(config.featureEnabled)) {
featureEnabled = config.featureEnabled;
} else {
featureEnabled = this.enableSomeFeature;
}
} else {
featureEnabled = this.enableSomeFeature;
}
// now we know, but that wasn't smooth
if (featureEnabled) {
...
}
// --- Even worse: trying to change the value of the option ---
// unsafe: we may not have a config object
config.enableSomeFeature = false;
// unsafe: we are modifying the original config object
(config = config || {}).enableSomeFeature = false;
// cloning the config object is safe, but that's ineficient
// and inelegant
config = Ext.apply({enableSomeFeature: false}, config);
// --- Super method ---
this.callParent(arguments); // don't forget the arguments here!
// --------------------
// here initComponent will have been called
}
,initComponent: function() {
// --- Accessing config options is easy ---
// reading
if (this.enableSomeFeature) { ... }
// or writing: we now we change it in the right place, and
// we know it has not been used yet
this.deferRender = true;
// --- Completing or changing dependant objects is safe ---
// items, stores, templates, etc.
// Safe:
// 1. you can be sure that the store has not already been used
// 2. you can be sure that the config object will be instantiated
// in the super method
this.store = {
type: 'json'
...
};
// --- However that's too early to use dependant objects ---
// Unsafe: you've no certitude that the template object has
// already been created
this.tpl.compile();
// --- Super method ---
this.callParent();
// --------------------
// Safe: the store has been instantiated here
this.getStore().on({
...
});
// will crash, the element has not been created yet
this.el.getWidth();
}