Comments on: Code Hinting and Strict Data Typing for TweenLite and TweenMax Vars

By: Mark

Mark — Fri, 23 Dec 2011 20:09:46 +0000

Thanks, that was fast. I see you’ve added rotation() too, I forgot to mention that one too, had it in my mind too. Awesome! I’m glad I’ve requested it. Have a lovely christmas!

By: Jack

Jack — Fri, 23 Dec 2011 18:38:49 +0000

Your wish is my command, Mark I added those convenience methods (along with a few others) in the latest version.

By: Mark

Mark — Fri, 23 Dec 2011 13:37:04 +0000

I think TweenLiteVars are awesome (use it alot), but I would like to see these functions added to it:

.move(x:Number, y:Number, relative:Boolean = false)

.scaleX(value:Number, relative:Boolean = false)

.scaleY(value:Number, relative:Boolean = false)

.scale(value:Number, relative:Boolean = false) // does scaleX and scaleY

By: Mr. Lawyer

Mr. Lawyer — Fri, 08 Apr 2011 10:58:45 +0000

Come on guys inline isn’t so bad

By: Ryno

Ryno — Sat, 12 Mar 2011 20:01:55 +0000

Inline isnt that bad really – its better for quick coding and user friendlyness

By: Zachary Dremann

Zachary Dremann — Sat, 04 Dec 2010 02:10:28 +0000

I hate to say it… But I like the new syntax. There are some negatives, but it really is easy to use inline. You win.

(But I still consider that unreadable. I can’t tell what variable i’m changing, and I can’t – at a glance – tell anything about it at all. But even with that, it’s better this way.)

By: Jack

Jack — Tue, 30 Nov 2010 21:41:34 +0000

Zachary, it is a bit of a double-edged sword but I’m confident that when you weigh all the pros and cons, they add up pretty decisively on the side of the new syntax. Even with having to define the 5 extra parameters in the example you posted, the new syntax is shorter. And remember that one of the primary purposes of these optional classes is enabling code hinting, so the readability argument loses its strength pretty quickly (put your cursor on any argument and CTRL-SPACE). The old way was practically impossible to do inline, making things much more verbose plus it required more than double the file size. And extra helper classes (like GlowFilterVars) were necessary. Not anymore. The new system even checks to make sure you activated the plugin if necessary. So all in all, it’s a big step forward, but I realize there will be some growing pains for folks who were used to the old way. I apologize for that.

By: Zachary Dremann

Zachary Dremann — Tue, 30 Nov 2010 20:33:17 +0000

This new syntax is pretty bad for things like blur filters. In the old method, you could do something like

myVars:TweenLiteVars = new TweenLiteVars();
myGlowVars:GlowFilterVars = new GlowFilterVars(1,1,0xffffff);
myGlowVars.addFilter = false;

In the new syntax, You have to do:
myVars:TweenLiteVars = new TweenLiteVars();
myVars.GlowFilter(1,1,0xffffff,1,2,false,false,2,false);

Not only is that not readable at at all, I have to define all those unnecessary variables.

By: sjimmi

sjimmi — Wed, 24 Nov 2010 10:52:50 +0000

hmmm.. not digging the new way…

By: Ramiro Araujo

Ramiro Araujo — Wed, 17 Nov 2010 21:24:28 +0000

Hmm, ok. I’ve never used the old version. What I meant was that you can like your first example: declare it and call one method per line.