I think I understand the difference between _create
and _init
in widget definitions (see for instance this question), but I\'m still not certain about
Short answer here: _create() will be executed when you run your jquery-ui plugin for the first time, like $xx.your-plugin(your options); _init() will be executed first and after the first time when your code runs into $xx.your-plugin(your options);
As there are some code in jquery-ui.custom.js like this:
var instance = $.data( this, fullName );
if ( instance ) {
instance.option( options || {} )._init();
}
So, if you draw a chart with jquery-ui plugin, after it's drawn out, then you want to use new data to update it, you need to do this in _init() to update your chart. If you just display something and won't update them totally, _create() will meet your needs.
From:
Use
_create
to build and inject markup, bind events, etc. Place default functionality in_init()
. The dialog widget, for example, provides anautoOpen
parameter denoting whether or not the dialog should be open once the widget is initialized; a perfect spot for_init()
!
Also:
The widget factory automatically fires the
_create()
and_init()
methods during initialization, in that order. At first glance it appears that the effort is duplicated, but there is a sight difference between the two. Because the widget factory protects against multiple instantiations on the same element,_create()
will be called a maximum of one time for each widget instance, whereas_init()
will be called each time the widget is called without arguments...
If the author uses _init()
when _create()
should have been coded, the result will be that the code in _init()
will be executed once per widget instantiation.