Alien-Web-ExtJS-V3
39 results

 view release on metacpan or  search on metacpan

share/docs/source/Fx.html  view on Meta::CPAN 

<!DOCTYPE html>
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  <title>The source code</title>
  <link href="../resources/prettify/prettify.css" type="text/css" rel="stylesheet" />
  <script type="text/javascript" src="../resources/prettify/prettify.js"></script>
  <style type="text/css">
    .highlight { display: block; background-color: #ddd; }
  </style>
  <script type="text/javascript">
    function highlight() {
      document.getElementById(location.hash.replace(/#/, "")).className = "highlight";
    }
  </script>
</head>
<body onload="prettyPrint(); highlight();">
  <pre class="prettyprint lang-js">(function(){
    // contants
    var NULL = null,
        UNDEFINED = undefined,
        TRUE = true,
        FALSE = false,
        SETX = &quot;setX&quot;,
        SETY = &quot;setY&quot;,
        SETXY = &quot;setXY&quot;,
        LEFT = &quot;left&quot;,
        BOTTOM = &quot;bottom&quot;,
        TOP = &quot;top&quot;,
        RIGHT = &quot;right&quot;,
        HEIGHT = &quot;height&quot;,
        WIDTH = &quot;width&quot;,
        POINTS = &quot;points&quot;,
        HIDDEN = &quot;hidden&quot;,
        ABSOLUTE = &quot;absolute&quot;,
        VISIBLE = &quot;visible&quot;,
        MOTION = &quot;motion&quot;,
        POSITION = &quot;position&quot;,
        EASEOUT = &quot;easeOut&quot;,
        /*
         * Use a light flyweight here since we are using so many callbacks and are always assured a DOM element
         */
        flyEl = new Ext.Element.Flyweight(),
        queues = {},
        getObject = function(o){
            return o || {};
        },
        fly = function(dom){
            flyEl.dom = dom;
            flyEl.id = Ext.id(dom);
            return flyEl;
        },
        /*
         * Queueing now stored outside of the element due to closure issues
         */
        getQueue = function(id){
            if(!queues[id]){
                queues[id] = [];
            }
            return queues[id];
        },
        setQueue = function(id, value){
            queues[id] = value;
        };
        
//Notifies Element that fx methods are available
Ext.enableFx = TRUE;

<span id='Ext-Fx-cfg-stopFx'><span id='Ext-Fx-cfg-concurrent'><span id='Ext-Fx-cfg-block'><span id='Ext-Fx-cfg-afterStyle'><span id='Ext-Fx-cfg-useDisplay'><span id='Ext-Fx-cfg-remove'><span id='Ext-Fx-cfg-endOpacity'><span id='Ext-Fx-cfg-duration'><...
</span></span></span></span></span></span></span></span></span></span></span></span></span> * @class Ext.Fx
 * &lt;p&gt;A class to provide basic animation and visual effects support.  &lt;b&gt;Note:&lt;/b&gt; This class is automatically applied
 * to the {@link Ext.Element} interface when included, so all effects calls should be performed via {@link Ext.Element}.
 * Conversely, since the effects are not actually defined in {@link Ext.Element}, Ext.Fx &lt;b&gt;must&lt;/b&gt; be
 * {@link Ext#enableFx included} in order for the Element effects to work.&lt;/p&gt;&lt;br/&gt;
 * 
 * &lt;p&gt;&lt;b&gt;&lt;u&gt;Method Chaining&lt;/u&gt;&lt;/b&gt;&lt;/p&gt;
 * &lt;p&gt;It is important to note that although the Fx methods and many non-Fx Element methods support &quot;method chaining&quot; in that
 * they return the Element object itself as the method return value, it is not always possible to mix the two in a single
 * method chain.  The Fx methods use an internal effects queue so that each effect can be properly timed and sequenced.
 * Non-Fx methods, on the other hand, have no such internal queueing and will always execute immediately.  For this reason,
 * while it may be possible to mix certain Fx and non-Fx method calls in a single chain, it may not always provide the
 * expected results and should be done with care.  Also see &lt;tt&gt;{@link #callback}&lt;/tt&gt;.&lt;/p&gt;&lt;br/&gt;
 *
 * &lt;p&gt;&lt;b&gt;&lt;u&gt;Anchor Options for Motion Effects&lt;/u&gt;&lt;/b&gt;&lt;/p&gt;
 * &lt;p&gt;Motion effects support 8-way anchoring, meaning that you can choose one of 8 different anchor points on the Element
 * that will serve as either the start or end point of the animation.  Following are all of the supported anchor positions:&lt;/p&gt;
&lt;pre&gt;
Value  Description
-----  -----------------------------
tl     The top left corner
t      The center of the top edge
tr     The top right corner
l      The center of the left edge
r      The center of the right edge
bl     The bottom left corner
b      The center of the bottom edge
br     The bottom right corner
&lt;/pre&gt;
 * &lt;b&gt;Note&lt;/b&gt;: some Fx methods accept specific custom config parameters.  The options shown in the Config Options
 * section below are common options that can be passed to any Fx method unless otherwise noted.&lt;/b&gt;
 *



( run in 0.485 second using v1.01-cache-2.11-cpan-62a16548d74 )