Comments on: JavaScript Tween function

By: Nabil

Nabil — Wed, 26 May 2010 19:04:57 +0000

I wrote that on purpose, this doesn’t hurt but sure there is a better way to write it.

Actually I should have wrote a comment to remember me why I coded it that way… oops.

But the way, I forgot to tell you that I was very busy with my personal life, I apologize for not responding to your comments/requests earlier.

By: Nabil

Nabil — Wed, 26 May 2010 18:58:03 +0000

Thank you for your interest, this small library is a draft and I will put more effort on improving if I see that people like you are willing to support it by providing bug reports and feedback.

I posted the full version of the function and I will – in the near future – have a repository and a bug tracker.

By: Peter Bowey

Peter Bowey — Fri, 14 May 2010 12:24:18 +0000

Notes: The two (original) failed ‘if’ conditionals occur on the following code:

1) if (tw[f]["from_orig"] === ‘current’); // line 53
2) if (typeof(a) == “object”); // line 155

There is no ‘TRUE’ state code to execute after either of the above condtions. Note the semicolon; ending each condition

Peter Bowey

By: Peter Bowey

Peter Bowey — Fri, 14 May 2010 11:58:53 +0000

Thanks Kadimi for sharing this tween() javascript function:

I have taken the original ‘minimized’ tween() js code and expanded it back to a human readable source. I have corrected some JSLint issues presented with code and additionally corrected two js ‘if conditionals’ that had no ‘TRUE’ state code to execute. I think this code you have created is educational in human readable code format:

>————————————-<


// Use:   tween(element, property, from, to, duration, [optional] function)

// Where: element: ID of HTML element, property: CSS property for tween'ing, from: initial value, to: final value

var fps = 40; var debugging = 0; var tw = []; [...] code removed by Nabil Kadimi>-------------------------------------<

Peter Bowey