[Golist] Idea for tween library structur

[Moses Gunesch]

Karsten, interesting approach, you're doing some good work here.

One thing that I don't know how to deal with is using Overlap monitor  
regarding nested properties. For example if you state that you're  
handling "blurX", that property name exists in other filters too so  
there would be a false overlap there. I guess one way we could do it  
would be to come up with a convention like  
"filters.DropShadowFilter.blurX" or "DropShadow_blurX". This works but  
it's hard to set a convention like that.

This issue crosses over to color and other transform props as well.  
It's not just an OverlapMonitor question but also a question of how a  
tween handler operates... in an ultimate scenario there would be a  
clear way to organize "nested property" tweens across the board. I'm  
interested in any and all ideas on that.

One grand concept I came up with: Tween definition classes that use  
XML to describe the location and nature of the tween property, as well  
as the name and type of each step down the object chain to get to it.  
So first you'd have a "filters"/Array node, then a ""/DropShadowFilter  
node, then a "blurX"/Number node. Although I love this idea on a  
concept level, in reality I think it would be too slow to do  
lookups... but you could in theory build the ultimate generic tween  
processor that would be able to parse and update any tween, any where,  
any type. I guess the good thing about Go is, if I wanted to give that  
crazy idea a shot, at least I have a platform to work from. :)

Anyway I would be interested to hear your thoughts regarding the  
OverlapMonitor nested props issue...

- m




On Feb 23, 2008, at 12:18 PM, Karsten Goetz wrote:

> Hi,
>
> it's very faszinating to see the developement of Go step by step :-)
>
> I've created a little "timline" using HydroTween and an own  
> filterTween and want to share it with you.
> It looks like this:
>
> 	group.addChild(new HydroTween(clip, {x:200, y:50}, 0, 1,  
> Quadratic.easeInOut));
> 	group.addChild(new HydroTween(clip, {rotation:360}, 0.5, 1,  
> Linear.easeInOut));
> 	group.addChild(new DropShadowTween(clip, endFilter(), 1, 1.3,  
> Bounce.easeOut));
> 	group.addChild(new HydroTween(clip, {x:0, y:100}, 1.5, 1,  
> Quadratic.easeInOut));
> 	group.start();
>
> the function  endFilter() returns a dropshadowfilter. I hat to  
> change the call of the start-properties in Hydrotween to make  
> multiple manipulation of the same property possible ( here the x- 
> value ). Overlapmanagement does not work yet. See the example  
> attached to the mail.
>
> I'm just thinking about small tween packages like this:
>
> tweens
> - dropShadow
> - - DropShadowVO.as // a value object with tweenable Filterprops
> - - DropShadowTween.as // Constructor: new DropShadowTween(clip,  
> startDropShadowVO, endDropShadowVO, 1, 1.3, Bounce.easeOut));
>
> - movieClip
> - - ClipVO.as // a value object with tweenable clipprops
> - - ClipTween.as // Constructor: new DropShadowTween(clip,  
> startClipVO, endClipVO, 0, 1, Linear.easeOut));
>
> - bezier
> - - BezierVO.as // a value object with propertiers
> - - BezierTween.as // Constructor: new DropShadowTween(clip, start  
> BezierVO, endBezierVO, 0, 1, Linear.easeOut))
>
> etc.
>
> Just an idea for a library-structure. What do you think?
>
> Lot's of greetings
>
> k
>
> <example.zip>
>
> ------------------------
> Karsten Goetz
> Flashprogrammierung
>
> Bernstorffstr. 120
> 22767 Hamburg
>
> Tel:       +49 40 43 09 91 07
> Mobil:   0173 57 14 984
>
>
>
> _______________________________________________
> 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/20080227/b8eab97b/attachment.html