The link seems to work for me. You might want to try downloading the newer version of this framework just released a few days ago.

It looks like the link to compressed.js is down, when you have a moment could you look into this?

Thanks
Alex

Honestly, not only can I not believe I didn’t notice that, but I’m not sure I ever even knew that. Apparently I don’t know JavaScript prototypes as well as I thought I did.

I would consider this a bug, and therefore will not wait until version 2 to make this change.

Thanks for the heads up!

var fx2 = new FX(‘bar2′, {
‘left’: { from: 0, to: 150 }
});
fx2.play();

Here, a property called frame is a pointer to an Object containing one style “left” with value 100.
Because frame is a reference value, both instances of FX point to the same Object. This means that when
“150” is added to fx2.frame, it is also reflected in fx1.frame.

I see what your driving at… you want easing capabilities, don’t worry, its coming.

Aside from that, I don’t see much difference between your implementation and mine other than moving “frame”, “endAttr”, and “startAttr” into the constructor.

Not sure what the difference is. Is their a particular reason why you’ve done this?

this.FX = function(el, attributes, opt) {
this.el = DOM.get(el);
this.attributes = attributes;
this.duration = opt.duration || 0.7;
this.tweenType = opt.tweenType || “Sine”;
this.easeType = opt.easeType || “easeInOut”;
this.callback = opt.callback || function() { };
this.ctx = opt.ctx || window;

/**
* The object to carry the current values for each frame
* @type Object
*/
this.frame = {},

/**
* The object containing all the ending values for each attribute
* @type Object
*/
this.endAttr= {},

/**
* The object containing all the starting values for each attribute
* @type Object
*/
this.startAttr= {};
};

I will be adding support for a variety of transitional easing functions in the next version which will be along sometime this summer.

In addition to that (for anyone else who is interested) the next version will include support for units (px, em, %, etc.), support for Safari 2, and various other performance optimizations such as what joseanpg suggessted.

That’s a very good point I must have glossed over. I plan to release a second version sometime in the near future, I’ll definitely include your suggestion, thanks for the tip!