Comments on: Last Call for v11 Input

By: Shawn

Shawn — Sat, 05 Sep 2009 03:41:43 +0000

I am new to AS and TweenMax – haven’t used v11 yet (just d/led it) but have been using v.10 this evening. Repeat is SUPER INTUITIVE and I love it. I could live with the change, but imho it would be a step in the wrong direction.

don’t have much to contribute constructively on the other questions.

I was hoping their would be an easy way to do text effects on a per character basis (I have seen the swish-like stuff in your forums, and that is exactly what I am talking about – even in your v11 Max timeline example – the way the letters drop in fade in and bounce – very cool).

I’m not complaining – the solutions offered seem to be sufficient (if not tedious). I haven’t tried them myself yet, but read enough to understand the concept.

I don’t know if doing effects on a per-character basis is within the scope of v11 but, hey, you were asking for suggestions.

Anyway, from my brief experience with Max 10 it seems like you’ve got a fine product here at a MORE THAN FAIR price (I just read your blog on the license issues). Keep up the good work, and I am sure a grateful public will reward you for your efforts. (as I said elsewhere, in faith I am saving my pennies to become a green club member).

Best wishes to you.

By: John Dewar

John Dewar — Mon, 31 Aug 2009 21:48:14 +0000

1) It feels fine, but the use of append/prepend is inconsistent. Personally I’d like to see it expanded for consistency rather than eliminated for consistency, but in general either way would probably be an improvement.
2) No, I always comment out some of the ones that are already activated anyway already.
3) Yes.
4-5) Can’t live without the addCallback, but an appendCallback/appendMultipleCallbacks would be more intuitive and consistent, I think, especially if, via appendMultiple, you could be sure they would get called in that order. I’m not saying that any of this is particularly important because you can sequence them already with the time parameter, it would just kind of fit in with the rest of the interface better.
6) No, I’m a heavy AE user but I still say repeat is fine and easier to understand.
7) Keep them and I second the motion for appendMultiple() and prependMultiple()

By: jack

jack — Sat, 25 Jul 2009 17:31:40 +0000

cassio, That’s exactly what MotionBlur does! It even changes the direction of the blur based on the angle of movement.

By: cassio

cassio — Sat, 25 Jul 2009 17:13:45 +0000

AutoBlur would be a great option (if an element is moving fast on x or y, it automatically would set the blur accordingly to create a great speed effect)

By: misterbenn

misterbenn — Thu, 23 Jul 2009 11:55:57 +0000

1: Everything works great, this version has the best API in my opinion. I like the use of initialising objects in the constructor as this fits in with other API’s I’m using (Away3D for example).

2: yes

3: yes

6: No, repeat keeps it inline with everything else

7: keep them, and possibly add appendMultiple() and prependMultiple() for consistency.

By: hive

hive — Wed, 15 Jul 2009 09:21:11 +0000

#1 / #4
one tiny thing maybe: to tween objects relative how about an option kinda like: relative:Boolean or delta:Boolean to switch between relative and absolute, instead of setting quotes.
would make it easier tweening object with dynamic size

otherwise: it’s more than i thought i’d ever need… i’ve done animations that would have been quite difficult with other engines… LOVE TimelineMax

#2
yes. it’s called TweenMax, then max it

hence:
#3
yes. no plugins (although i’m more of a Max user)

#4 -> #1

#5
bezier, autoAlpha,… and all the others ^^ keep them all, at least within *Max

#6
either suits me. repeat is ok. never change a running system ^^

#7
keep both! let user decide if he need append() or insert()

By: lukas buenger

lukas buenger — Thu, 09 Jul 2009 09:34:57 +0000

Definitely the best tweening solution existing! Thanks for the good work!

7. I’d keep the methods and its names. The Timeline classes represent tweening lists after all and I can’t think of any implementation of a list with methods called push and shift…

I agree with Ramiro: Tween identifiers would be a nice thing to have. If you try to identify a given tween, you have to do a lot of iterating through the get Children()-Array or save a reference when istantiating the tween. This could be made smarter, I guess.

By: Ramiro Araujo

Ramiro Araujo — Thu, 18 Jun 2009 19:07:01 +0000

I’ve been using the timeline classes and they rock. I didn’t have any suggestion but right now reading this I had one idea: The possibility to ‘name’ tweens or timelines inserted inside a timeline, and use that names to modify or remove the tween or timeline later. I now this can be done keeping a reference of the tween or timeline passed, but right now seems easier and more intuitive that way. What do you think?

By: Tim

Tim — Wed, 03 Jun 2009 15:48:27 +0000

3) Keep TweenLite as is for backwards compatibility and add another called TweenSuperLite (or whatever) that includes no default plugins

By: Paul

Paul — Tue, 02 Jun 2009 22:30:33 +0000

Haven’t tried v.11, but I favor simplicity and backward compatibility over size and speed. Make it so you can tweak your import and exclude plugins if you’re super worried about size, but keep it as plug and play as possible. I don’t want to have to go to the top of my file and import more things every time I decide to tween an additional property.

Thanks Jack!