<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Moses,<div><br class="webkit-block-placeholder"></div><div>I think the perception of Go being complicated also comes from people's familiarity with Fuse. Fuse was easy to use, but went pretty deep by comparison, which could be throwing people. The idea of building Fuse with Go sounds daunting, and there could be a sense that you are required to roll all that functionality yourself, even though it might not be required for the code you're writing. People hate losing options, even when it costs them.</div><div><br class="webkit-block-placeholder"></div><div>Also, it's possible that people are confused by the methodology change. Instead of controlling everything through the Fuse class, you create individual tween objects, which <i>seems</i> more complex.</div><div><br class="webkit-block-placeholder"></div><div>Tim</div><div><br><div><div>On 4-Mar-08, at 1:00 PM, <a href="mailto:golist-request@goasap.org">golist-request@goasap.org</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Send GoList mailing list submissions to<br><span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:golist@goasap.org">golist@goasap.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br><span class="Apple-tab-span" style="white-space:pre"> </span>http://goasap.org/mailman/listinfo/golist_goasap.org<br>or, via email, send a message with subject or body 'help' to<br><span class="Apple-tab-span" style="white-space:pre"> </span>golist-request@goasap.org<br><br>You can reach the person managing the list at<br><span class="Apple-tab-span" style="white-space:pre"> </span>golist-owner@goasap.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of GoList digest..."<br><br><br>Today's Topics:<br><br> 1. Go: Scary-complicated? (Moses Gunesch)<br> 2. Re: Go: Scary-complicated? (Angela Ferraiolo)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 4 Mar 2008 11:56:48 -0500<br>From: Moses Gunesch <moses@goasap.org><br>Subject: [Golist] Go: Scary-complicated?<br>To: Mailing list for the Go ActionScript Animation Platform<br><span class="Apple-tab-span" style="white-space:pre"> </span><golist@goasap.org><br>Message-ID: <48147780-4E36-4B8F-913B-C1BC8613C070@goasap.org><br>Content-Type: text/plain; charset=WINDOWS-1252; format=flowed;<br><span class="Apple-tab-span" style="white-space:pre"> </span>delsp=yes<br><br>Hi everyone,<br><br>So now that the new site is live, let's assess how I did for making Go <br>approachable.<br>Go is actually very simple once you understand it, but before that it <br>intimidates people and seems really complicated.<br><br>So:<br>Are the goals of Go still confusing?<br>Is the presentation of Go confusing?<br>Is it intimidating, say if you had first seen it at the new site http://www.goasap.org/ <br> ?<br>Is it clear yet that very little is required for the compatibility <br>layer ? just GoEngine, GoEvent, and PlayableBase/IPlayable ? and that <br>everything else is entirely optional?<br>Is it obvious yet that it's very easy to build a tween over LinearGo <br>in 3 easy steps or does that still feel like everest?<br><br><br>Here's one idea I had ? a swf slideshow with a "next" nav button, that <br>would walk you through step by step how Go is structured. Because each <br>bit of it is extremely logical and is there for a reason... for <br>example, GoItem is there as an abstract base class for any animation <br>type, not just tweens, and PlayableBase sits at the very core because <br>some things that you can play, are not animations at all, like a <br>Sequence. I want that structure to be really clearly presented but I'm <br>worried that the Architecture page does not show this simply enough....<br><br>thanks,<br>Moses <br><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 4 Mar 2008 12:22:47 -0500<br>From: "Angela Ferraiolo" <aferraiolo@gmail.com><br>Subject: Re: [Golist] Go: Scary-complicated?<br>To: "Mailing list for the Go ActionScript Animation Platform"<br><span class="Apple-tab-span" style="white-space:pre"> </span><golist@goasap.org><br>Message-ID:<br><span class="Apple-tab-span" style="white-space:pre"> </span><4499c75b0803040922o66462498ibf315fd2178f614f@mail.gmail.com><br>Content-Type: text/plain; charset=WINDOWS-1252<br><br>Hello Moses & the list,<br><br>Thanks for Go! A .swf walkthough would be awesome!<br><br>It is not that your site is confusing so much as there is<br>a lot of new stuff to learn right now on all sides. Anything<br>you can do to help speed the process would be greatly<br>wonderful and go-tatstic.<br><br>Right now Go is still in my "to do" list! But I am a fan.<br><br>Thank you again,<br><br>-- Angela<br><br><br>On 3/4/08, Moses Gunesch <moses@goasap.org> wrote:<br><blockquote type="cite">Hi everyone,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> So now that the new site is live, let's assess how I did for making Go<br></blockquote><blockquote type="cite"> approachable.<br></blockquote><blockquote type="cite"> Go is actually very simple once you understand it, but before that it<br></blockquote><blockquote type="cite"> intimidates people and seems really complicated.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> So:<br></blockquote><blockquote type="cite"> Are the goals of Go still confusing?<br></blockquote><blockquote type="cite"> Is the presentation of Go confusing?<br></blockquote><blockquote type="cite"> Is it intimidating, say if you had first seen it at the new site http://www.goasap.org/<br></blockquote><blockquote type="cite"> ?<br></blockquote><blockquote type="cite"> Is it clear yet that very little is required for the compatibility<br></blockquote><blockquote type="cite"> layer ? just GoEngine, GoEvent, and PlayableBase/IPlayable ? and that<br></blockquote><blockquote type="cite"> everything else is entirely optional?<br></blockquote><blockquote type="cite"> Is it obvious yet that it's very easy to build a tween over LinearGo<br></blockquote><blockquote type="cite"> in 3 easy steps or does that still feel like everest?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Here's one idea I had ? a swf slideshow with a "next" nav button, that<br></blockquote><blockquote type="cite"> would walk you through step by step how Go is structured. Because each<br></blockquote><blockquote type="cite"> bit of it is extremely logical and is there for a reason... for<br></blockquote><blockquote type="cite"> example, GoItem is there as an abstract base class for any animation<br></blockquote><blockquote type="cite"> type, not just tweens, and PlayableBase sits at the very core because<br></blockquote><blockquote type="cite"> some things that you can play, are not animations at all, like a<br></blockquote><blockquote type="cite"> Sequence. I want that structure to be really clearly presented but I'm<br></blockquote><blockquote type="cite"> worried that the Architecture page does not show this simply enough....<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> thanks,<br></blockquote><blockquote type="cite"> Moses<br></blockquote><blockquote type="cite"> _______________________________________________<br></blockquote><blockquote type="cite"> GoList mailing list<br></blockquote><blockquote type="cite"> GoList@goasap.org<br></blockquote><blockquote type="cite"> http://goasap.org/mailman/listinfo/golist_goasap.org<br></blockquote><blockquote type="cite"><br></blockquote><br><br><br>------------------------------<br><br>_______________________________________________<br>GoList mailing list<br>GoList@goasap.org<br>http://goasap.org/mailman/listinfo/golist_goasap.org<br><br><br>End of GoList Digest, Vol 4, Issue 1<br>************************************<br></blockquote></div><br></div></body></html>