[Golist] the possibilities of go

[Moses Gunesch]

Curt,

You've hit on the key here when you say that the bar will continue to  
lower.

Don't forget everyone that Go is at the early adopter stage right now  
and is looking for involvement by coders who are interested in the  
more low-level challenges of creating bundles of tween classes,  
optimizing and improving the Go architecture and so forth. No one has  
yet put out a single parser built with Go! But once they do, you'll be  
able to go in and add features to it because you'll be familiar with  
Go's structure...

Nothing is stopping anyone here who is comfortable working with OO  
code from writing a Go parser though!

Personally I already wrote one and it works great, and was simple to  
write. It involves one tween class, BlockTweenMG that is only slightly  
more complicated than the video tutorial example MotionTweenMG, in  
that it uses Arrays to store multiple properties dynamically. Then a  
single parser class which simply walks through the object passed, uses  
blockTweenMG.hasOwnProperty() to determine if it's a tween property  
like easing, and if not adds the value as an animation prop. The whole  
thing is literally just a few lines of code and it works just like  
Fuse in many ways... it was easy to make it support parallel-tween  
action arrays like Fuse, and even jam in some sweet custom-advance  
functionality because Go already provides utils that do all that!

So, don't think of it like "I have to go build Fuse now".. it's not  
like that~!

More like: "I need one or more tweens so I can throw together a simple  
parser for a syntax I'm familiar with, that uses Go's Sequence class."

m



On Mar 5, 2008, at 9:04 AM, Curt Kotula wrote:

> I agree. I wouldn't change a thing.
>
> With each new published extension of go the entry bar will be lowered
> a little bit.
>
> Also, learning curves are healthy. The users that take the time to
> learn the go platform will be able to manipulate it better when they
> need functionality that doesn't currently exist. You should have to
> walk before you run.
>
> _curt