[Golist] new message: If Fuse was huge, Go is tiny.

[Alan]

I want Go to be successful.

For brevity I'm just gonna jump into what I think:

The first paragraph feels like a pitch, and I don't want to read  
that.  If someone is going to invest the time to spend on Go, they

1. Know what they are looking for and familiar with the common problems.
2. Already invest time into other open source projects (as well as  
their own) and want to know how Go makes things better- easier- faster.

I would start off with a simple 3-4 sentence intro about how you made  
fuse, saw the short comings of it's and other animation engines and  
wanted to change it.  Make it personal, less like 'some voice-over'  
from a du-pont commercial.  I don't know/care about fuse (im pure as3)  
but I do know a lot of people use it-adding your face to the project  
adds weight to it.

"At its heart is a centralized pulse engine – all animation ....and  
entirely optional for the end-user.

Next, Go offers the most common..... compatibility layer that diverse  
systems can share, instead of reinventing them.

Finally, the.....extend these or create base classes and utilities of  
your own."


To me, these paragraphs say the most interesting stuff, but it's way  
at the bottom. Tell me simply what the engine is and how it can be  
implemented.

For example I've been on this list for a while and I have been trying  
to squeeze in time to go back and revisit the tutorials and code-but  
in all honesty, I'm not really sure why I would use this. Until, that  
recent post about integrating it with PV3D. That's some interesting  
stuff.

Perhaps you could take some time and think up 10 scenarios where one  
would choose to use Go because other animation engines wouldn't be as  
useful. This papervision example being one. Make them varied as  
possible. Show the versatility!

Also, start having a library of short .swfs that people can scroll  
through and just see examples of Go being used.  Make me think - wow I  
want to do that!  One guy who does this great  is mr.doob.

http://mrdoob.com/blog/

You zip through stuff and think, wow that;s neato. In fact, this is  
how I got into PV3D, was by seeing his stuff.  Nothing uber fancy-it  
can be that red square you used in the 2nd tutorial but what I saw at  
the end perked my interest.  Unfortunately- it took till the end of  
the video to see it.  Then I thought " doh! maybe I shouldn't have  
been half distracted while he talked".

I would describe my self as being as just crossing to being an  
advanced coder. I build my own pet animation projects and manager  
classes, but I still don't see the possibilities of Go. The most  
interesting part of the 2nd tutorial was when you  demonstrated  
modulation of what you had built.  THEN light bulbs went off in my  
head and I thought,

"hmm yeah, if he did that then I bet I can change / add things to do  
this and this...".

Lastly, I would LOVE some kind of UML and or class diagrams. Some  
thing visual so I can see how different parts of the engine relate to  
another.

Also, to help someone like me get into it, i'd like to see some *real*  
loose templates - again as varied as possible to show possibilities.  
They can be simple and skeleton- like an interface or even just a  
simple UML of some methods.  I can build upon it and edit and whatnot,  
but perhaps it would be one just a baby step more then what is given  
on the site.  This would help me wet my appetite THEN I go deeper into  
the framework and write / rewrite things.

The idea is to show possibilities, show us the way Moses!

LET YOUR PEOPLE GO!

Alan

On Apr 16, 2008, at 2:18 PM, Moses Gunesch wrote:
> the code looks like, and why you'd want to adopt it.
>
> So it's more straightforward. Less glossy. Shows code samples.
> Explains the value proposition.
>
> What do you think?
> dfddf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080416/f6b24541/attachment.html