What is xhooks?

[mitchellsimoens]

If we were to change it we would still have to support xhooks.

[LesJ]

If we were to change it we would still have to support xhooks.

You mean continue to support the name xhooks? There's no back compatibility issue since this feature is not in 4.0.7. It's only in 4.1 Beta.

[mitchellsimoens]

It is since 4.1.0 has been out for quite some time now (Oct 2011). Not saying that would be hard but something we would have to think about.

[LesJ]

It is since 4.1.0 has been out for quite some time now (Oct 2011). Not saying that would be hard but something we would have to think about.

Yes, think about it... 4.1 is still in Beta. It's OK to make changes in Beta.

[mitchellsimoens]

Yes, think about it... 4.1 is still in Beta. It's OK to make changes in Beta.

Haven't we pissed enough people off?

[LesJ]

Haven't we pissed enough people off?

I wouldn't sweat it. This is a very rarely used feature. It's used only once in the entire Ext code base, but if it had a less scary and more descriptive name... maybe it would be used more often

[LesJ]

I found this short youtube clip. If you are a visual person, it might speak volumes to you...

It show that it's important to select the right words.... you will have better results

http://www.youtube.com/watch_popup?v...m7oU&vq=medium

[mitchellsimoens]

Just FYI, I put in a story to consider renaming xhooks to something more descriptive like overrides.

EXTJSIV-5555

[themightychris]

I remembered xhooks from SenchaCon today and tried using it in a proxy config, but no luck! They're not in the docs either.

It seems that only components support xhooks, why not all classes? Shouldn't it be part of Ext.Base rather than AbstractComponent?

[dongryphon]

We chose a somewhat out-of-the-way name for this config (though it is in legue with "xtype" and "xclass") to not be confused with "override" in Ext.define. It is also something you probably don't need very often. The reason this is even present is that the underlying ability this config uses was needed by Ext.define/override to deal with singletons.

Also, the reason this is only applicable to components is that not all classes have the "config" concept as part of their design. Many classes do, but not all in the framework. And very likely not all classes in user applications.

The good news is that the functionality is now provided by Ext.override when the target of the override is an instance and not a class (which was previously an supported thing). The internal method Mitchell mentioned has been removed in favor of providing this functionality to any class or object via Ext.override.