[Golist] cycles design continued...

[Moses Gunesch]

Here's one more little puzzle piece on this:

I'm thinking that sometimes people might want to repeat tweens from  
the start, not cycle them back and forth.

Since this gets pretty elaborate and clutters LinearGo's code quite a  
bit, it might be prudent to create some kind of cycle handling class  
that could be instantiated by the tween on start if cycles isn't 1..?

This would solve a bunch of problems in that we could condense cycles,  
easeOnCycle and extraEasingParamsOnCycle and this looping option in  
one place. So maybe both LinearGo and Sequence could accept a  
parameter like repeater : Repeater, which would clean up both of those  
classes dramatically. Of course it's a tad more direct to just set  
mySequence.repeatCount = 2; than do something like  
mySequence.repeater.count = 2....

I'll look into this option though, I sorta like it because it  
encapsulates some of the messy iterator mechanics that are cluttering  
up my next build of LinearGo, both in update() and skipTo()....

opinions?

-m




On Mar 23, 2008, at 2:01 AM, Jan m. Danielsson wrote:

> Go (!) for the complete version!
> Like Michael Avila wrote - since you subclass it anyhow, the amount of
> parameters doesn´t really matter. But contrary to him, I like when  
> there
> are a lot of parameters to fiddle around with.
>
> And, btw, thank you for an awsome tweening system. So far I´ve only  
> used
> LinearGo, but I do love it. Keep up the good work!
>
> ///JmD
>
> _______________________________________________
> GoList mailing list
> GoList at goasap.org
> http://goasap.org/mailman/listinfo/golist_goasap.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080323/9ea1933d/attachment.html