Actions and Effects"
From Documentation
Line 28: | Line 28: | ||
where <tt>n</tt> is the DOM element to apply the action, and <tt>opts</tt> is the options specified in the client-side action. | where <tt>n</tt> is the DOM element to apply the action, and <tt>opts</tt> is the options specified in the client-side action. | ||
− | Notice that, before invoking jQuery's effects, you | + | Notice that, before invoking jQuery's effects, you should invoke <javadoc directory="jsdoc" method="defaultAnimaOpts(zk.Widget, _global_.Map, _global_.Array, boolean)">_global_.jqzk</javadoc> to prepare the initial options for animation. For example, |
<source lang="javascript" high="1"> | <source lang="javascript" high="1"> |
Revision as of 02:19, 12 August 2011
[since 5.0.6]
Here we describe how to provide more effects for client-side actions.
The allowed effects are actually the names of methods defined in Actions. Thus, to add a new effect, you have to add a new method to it. For example,
zk.eff.Actions.fooIn = function (n, opts) {
//your own effect to make the node visible, such as
//zk(n).slideIn(this, opts);
};
Then, you could use it in the client-side action:
<div action="show: fooIn">
....
</div>
The signature of an effect method is as follows.
function (DOMElement n, Map opts);
where n is the DOM element to apply the action, and opts is the options specified in the client-side action.
Notice that, before invoking jQuery's effects, you should invoke jqzk.defaultAnimaOpts(Widget, Map, Array, boolean) to prepare the initial options for animation. For example,
this.defaultAnimaOpts(wgt, opts, prop, true).jq
.css(css).show().animate(anima, { //the rest depending the jQuery effect you use
queue: false, easing: opts.easing, duration: opts.duration || 400,
complete: opts.afterAnima
});
Version History
Version | Date | Content |
---|---|---|
5.0.6 | December 2010 | This feature was introduced in 5.0.6 |