mixin vs plugin. What to choose?

Question

Let's assume I have defined several new components -MyComponent1, MyComponent2, ..., which extend Ext.Component.

Now I wnat to extend all this widgets with the same functionality - I want to add close button which would appear at the top-right position of MyComponentX.el.

What should I use: mixin? plugin? or something else?
And in general: mixin vs plugin, what is the best practise?

Mixin is inheritance but plugin are composition. – Aug 20 '13 at 09:58 — , Aug 20 '13 at 09:58

score 19 · Accepted Answer · answered Sep 04 '11 at 15:04

19

I like to think about it as -

mixin is what you use to achieve 'multiple inheritence'
plugin is what you use to enhance an existing component. plugin's lifecycle is managed by the component. (no lifecycle managemen for mixin. think of mixin as base class equivalent)

answered Sep 04 '11 at 15:04

Amol Katdare

6,740
2
33
36

Thank you for answer. So, which do you think is the best choice for my close-button example? – Molecular Man Sep 04 '11 at 15:26
3

I've got it. The best choice would be `plugin` as I want `to enhance an existing component`. Thanks, again. – Molecular Man Sep 05 '11 at 09:53
Also, since the OP asked about in general, you can only use plugins on `Ext.Component`s – Ruan Mendes Nov 09 '16 at 12:38

score 14 · Answer 2 · answered Nov 18 '11 at 15:14

14

Mixin properties and functions are injected into the class directly so they are part of the class definition.

plugins are added at the instance level

answered Nov 18 '11 at 15:14

user732456

2,638
2
35
49

score 1 · Answer 3 · answered Dec 01 '15 at 12:10

Plugins will add functionality to the Ext.Component class or the class extending Ext.Component. Scope of any method in plugin is in plugin itself.

Mixins can be used to add functionality to any other class. mixins methods will be available directly into the class.

mixin vs plugin. What to choose?

3 Answers3