<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Well sure, tweening APIs are very useful, and some of them get very popular.</div><div><br class="webkit-block-placeholder"></div><div>However, that doesn't mean that developers shouldn't be offered a toolset for building their own tweening APIs instead of having to work with other people's ideas, overhead, and limitations.</div><div><br class="webkit-block-placeholder"></div><div>Also consider this: If both you and I program our own stuff over Go, then try to work with each other's code, a lot of stuff will be common and familiar, even if we've made up our own syntax or tween classes. In fact there's a very good chance that we could mix and match, port features easily between our code bases and so forth... all while retaining the knowledge and flexibility to be able to work in the way we want with it instead of being forced to agree on a single monolithic API.</div><div><br class="webkit-block-placeholder"></div><div>But that's just the party line... everyone else, what do you think?</div><div><br class="webkit-block-placeholder"></div><div>- moses</div><br><div><div>On Jan 4, 2008, at 10:52 AM, Rich Hauck wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div> <font face="Verdana, Helvetica, Arial"><span style="font-size:12.0px">Moses is advocating that Adobe take the reins and redo Flash’s built-in Tween engine. In the meanwhile, the flexibility of Go’s package concerns me, as I believe that either:<br> </span></font><blockquote type="cite"><font face="Verdana, Helvetica, Arial"><span style="font-size:12.0px"> <br> </span></font><ul><li><font face="Verdana, Helvetica, Arial"><span style="font-size:12.0px">Developers will avoid Go in lieu of Tweener or TweenLite, since those packages have a defined syntax that larger groups can easily agree upon </span></font></li><li><font face="Verdana, Helvetica, Arial"><span style="font-size:12.0px">Developers use Go and make a slew of proprietary animation engines--and in-turn generate a learning curve for anyone forced to use their engines </span></font></li><li><font face="Verdana, Helvetica, Arial"><span style="font-size:12.0px">Someone creates a syntax similar to ZManager.paramsObj(), something that trumps the current AS3 Tween engine offerings, and that emerges as the unofficial definitive engine.<br> </span></font></li></ul></blockquote><font face="Verdana, Helvetica, Arial"><span style="font-size:12.0px"><br> What’s everyone else’s take on this?</span></font> </div> _______________________________________________<br>GoList mailing list<br><a href="mailto:GoList@goasap.org">GoList@goasap.org</a><br>http://goasap.org/mailman/listinfo/golist_goasap.org<br></blockquote></div><br></body></html>