From moses at goasap.org Tue Mar 4 08:56:48 2008 From: moses at goasap.org (Moses Gunesch) Date: Tue, 4 Mar 2008 11:56:48 -0500 Subject: [Golist] Go: Scary-complicated? Message-ID: <48147780-4E36-4B8F-913B-C1BC8613C070@goasap.org> Hi everyone, So now that the new site is live, let's assess how I did for making Go approachable. Go is actually very simple once you understand it, but before that it intimidates people and seems really complicated. So: Are the goals of Go still confusing? Is the presentation of Go confusing? Is it intimidating, say if you had first seen it at the new site http://www.goasap.org/ ? Is it clear yet that very little is required for the compatibility layer ? just GoEngine, GoEvent, and PlayableBase/IPlayable ? and that everything else is entirely optional? Is it obvious yet that it's very easy to build a tween over LinearGo in 3 easy steps or does that still feel like everest? Here's one idea I had ? a swf slideshow with a "next" nav button, that would walk you through step by step how Go is structured. Because each bit of it is extremely logical and is there for a reason... for example, GoItem is there as an abstract base class for any animation type, not just tweens, and PlayableBase sits at the very core because some things that you can play, are not animations at all, like a Sequence. I want that structure to be really clearly presented but I'm worried that the Architecture page does not show this simply enough.... thanks, Moses From aferraiolo at gmail.com Tue Mar 4 09:22:47 2008 From: aferraiolo at gmail.com (Angela Ferraiolo) Date: Tue, 4 Mar 2008 12:22:47 -0500 Subject: [Golist] Go: Scary-complicated? In-Reply-To: <48147780-4E36-4B8F-913B-C1BC8613C070@goasap.org> References: <48147780-4E36-4B8F-913B-C1BC8613C070@goasap.org> Message-ID: <4499c75b0803040922o66462498ibf315fd2178f614f@mail.gmail.com> Hello Moses & the list, Thanks for Go! A .swf walkthough would be awesome! It is not that your site is confusing so much as there is a lot of new stuff to learn right now on all sides. Anything you can do to help speed the process would be greatly wonderful and go-tatstic. Right now Go is still in my "to do" list! But I am a fan. Thank you again, -- Angela On 3/4/08, Moses Gunesch wrote: > Hi everyone, > > So now that the new site is live, let's assess how I did for making Go > approachable. > Go is actually very simple once you understand it, but before that it > intimidates people and seems really complicated. > > So: > Are the goals of Go still confusing? > Is the presentation of Go confusing? > Is it intimidating, say if you had first seen it at the new site http://www.goasap.org/ > ? > Is it clear yet that very little is required for the compatibility > layer ? just GoEngine, GoEvent, and PlayableBase/IPlayable ? and that > everything else is entirely optional? > Is it obvious yet that it's very easy to build a tween over LinearGo > in 3 easy steps or does that still feel like everest? > > > Here's one idea I had ? a swf slideshow with a "next" nav button, that > would walk you through step by step how Go is structured. Because each > bit of it is extremely logical and is there for a reason... for > example, GoItem is there as an abstract base class for any animation > type, not just tweens, and PlayableBase sits at the very core because > some things that you can play, are not animations at all, like a > Sequence. I want that structure to be really clearly presented but I'm > worried that the Architecture page does not show this simply enough.... > > thanks, > Moses > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org > From timuruski at gmail.com Tue Mar 4 12:59:57 2008 From: timuruski at gmail.com (Timothy Uruski) Date: Tue, 4 Mar 2008 13:59:57 -0700 Subject: [Golist] Go: Scary-complicated? In-Reply-To: References: Message-ID: Moses, 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. 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 seems more complex. Tim On 4-Mar-08, at 1:00 PM, golist-request at goasap.org wrote: > Send GoList mailing list submissions to > golist at goasap.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://goasap.org/mailman/listinfo/golist_goasap.org > or, via email, send a message with subject or body 'help' to > golist-request at goasap.org > > You can reach the person managing the list at > golist-owner at goasap.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of GoList digest..." > > > Today's Topics: > > 1. Go: Scary-complicated? (Moses Gunesch) > 2. Re: Go: Scary-complicated? (Angela Ferraiolo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 4 Mar 2008 11:56:48 -0500 > From: Moses Gunesch > Subject: [Golist] Go: Scary-complicated? > To: Mailing list for the Go ActionScript Animation Platform > > Message-ID: <48147780-4E36-4B8F-913B-C1BC8613C070 at goasap.org> > Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; > delsp=yes > > Hi everyone, > > So now that the new site is live, let's assess how I did for making Go > approachable. > Go is actually very simple once you understand it, but before that it > intimidates people and seems really complicated. > > So: > Are the goals of Go still confusing? > Is the presentation of Go confusing? > Is it intimidating, say if you had first seen it at the new site http://www.goasap.org/ > ? > Is it clear yet that very little is required for the compatibility > layer ? just GoEngine, GoEvent, and PlayableBase/IPlayable ? and that > everything else is entirely optional? > Is it obvious yet that it's very easy to build a tween over LinearGo > in 3 easy steps or does that still feel like everest? > > > Here's one idea I had ? a swf slideshow with a "next" nav button, that > would walk you through step by step how Go is structured. Because each > bit of it is extremely logical and is there for a reason... for > example, GoItem is there as an abstract base class for any animation > type, not just tweens, and PlayableBase sits at the very core because > some things that you can play, are not animations at all, like a > Sequence. I want that structure to be really clearly presented but I'm > worried that the Architecture page does not show this simply > enough.... > > thanks, > Moses > > > ------------------------------ > > Message: 2 > Date: Tue, 4 Mar 2008 12:22:47 -0500 > From: "Angela Ferraiolo" > Subject: Re: [Golist] Go: Scary-complicated? > To: "Mailing list for the Go ActionScript Animation Platform" > > Message-ID: > <4499c75b0803040922o66462498ibf315fd2178f614f at mail.gmail.com> > Content-Type: text/plain; charset=WINDOWS-1252 > > Hello Moses & the list, > > Thanks for Go! A .swf walkthough would be awesome! > > It is not that your site is confusing so much as there is > a lot of new stuff to learn right now on all sides. Anything > you can do to help speed the process would be greatly > wonderful and go-tatstic. > > Right now Go is still in my "to do" list! But I am a fan. > > Thank you again, > > -- Angela > > > On 3/4/08, Moses Gunesch wrote: >> Hi everyone, >> >> So now that the new site is live, let's assess how I did for making >> Go >> approachable. >> Go is actually very simple once you understand it, but before that it >> intimidates people and seems really complicated. >> >> So: >> Are the goals of Go still confusing? >> Is the presentation of Go confusing? >> Is it intimidating, say if you had first seen it at the new site http://www.goasap.org/ >> ? >> Is it clear yet that very little is required for the compatibility >> layer ? just GoEngine, GoEvent, and PlayableBase/IPlayable ? and that >> everything else is entirely optional? >> Is it obvious yet that it's very easy to build a tween over LinearGo >> in 3 easy steps or does that still feel like everest? >> >> >> Here's one idea I had ? a swf slideshow with a "next" nav button, >> that >> would walk you through step by step how Go is structured. Because >> each >> bit of it is extremely logical and is there for a reason... for >> example, GoItem is there as an abstract base class for any animation >> type, not just tweens, and PlayableBase sits at the very core because >> some things that you can play, are not animations at all, like a >> Sequence. I want that structure to be really clearly presented but >> I'm >> worried that the Architecture page does not show this simply >> enough.... >> >> thanks, >> Moses >> _______________________________________________ >> GoList mailing list >> GoList at goasap.org >> http://goasap.org/mailman/listinfo/golist_goasap.org >> > > > > ------------------------------ > > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org > > > End of GoList Digest, Vol 4, Issue 1 > ************************************ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080304/b5ba7b10/attachment.html From moses at goasap.org Tue Mar 4 13:32:14 2008 From: moses at goasap.org (Moses Gunesch) Date: Tue, 4 Mar 2008 16:32:14 -0500 Subject: [Golist] Go: Scary-complicated? In-Reply-To: References: Message-ID: Thanks for the thoughts Tim.. > > 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. I think for projects, the drive is to find something that works and is already built because you need it immediately and don't have extra time to mess around thinking about the mechanics of it. Fuse was geared toward prepackaging everything in that way and hiding its complexity. So, yeah. > 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. I can't wait to get time to show you guys this tutorial on how you can build a parser in just a few minutes. It is really, super easy. It doesn't have too many complex features in it, true, but I think as time goes on people will start building those out again. > 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 seems more complex. Actually that's a misconception right there ? the Fuse style parser I wrote worked with static methods, where you never see any tween classes at all. So, yes the tween objects are exposed for OO-style extensibility, but that does not limit you to that style as your final end product at all. For example let's say you write a tween class like HydroTween.. simply add a static method HydroTween.go() that generates and starts a tween, and you have a totally clean usage. I like that it gives you both options ? you can still make a new tween and store it in your code for reuse, which is far more efficient than generating one every time, or use the static call to avoid having to bother making the instance and then starting it. Even a third usage would be new CustomTween(...).start() which is pretty much the same as the static call would be, unless the static method does something special to it. Go not about offering "features" that you have to learn, like an API does. The options that it leaves open are just normal AS3 coding options that are always there... maybe people are just uncomfortable not being locked into one narrow way of doing things? - m -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080304/d76cdea6/attachment.html From jon at shovemedia.com Tue Mar 4 13:38:51 2008 From: jon at shovemedia.com (Jon Williams) Date: Tue, 04 Mar 2008 16:38:51 -0500 Subject: [Golist] PhysicsGo? Message-ID: <47CDC16B.20105@shovemedia.com> moses said i should post this here, so: curious ... how do you see PhysicsGo fitting in with the tweening engine stuff? rigid body dynamics and such seem altogether a different animal than go-from-this-number-to-this-number-in-this-much-time (and such) :j From patrick.figueroa at gmail.com Tue Mar 4 13:54:38 2008 From: patrick.figueroa at gmail.com (Patrick Figueroa) Date: Tue, 4 Mar 2008 16:54:38 -0500 Subject: [Golist] Go: Scary-complicated? In-Reply-To: References: Message-ID: <5847D094-28F1-42B3-83B4-645E3E6D8ABD@gmail.com> Thanks for clarifying a bit Moses... I also think that a great way for some users to start diving into Go is to see it as a comparison to Fuse. I know a lot of designers and developers (including me) know Fuse inside and out after using it for so long. I think perhaps a great way to introduce Go to those veteran Fuse users is with a simple fla or tutorial showing what Go is in a Fuse context. A lot of the time I learn new techniques through dissection of a fla because things are already grouped in a familiar environment (e.g. this is a nav button, this is an animated mc, this is what happens after it animates, etc...). In this context we all know what each item is supposed to do and how we would code that using Fuse, but to show how that would be coded with Go would put things into perspective. I hope I didn't get too confusing there... I can clarify a bit if things don't make sense. Patrick. On Mar 4, 2008, at 4:32 PM, Moses Gunesch wrote: > Thanks for the thoughts Tim.. >> >> 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. > > I think for projects, the drive is to find something that works and > is already built because you need it immediately and don't have > extra time to mess around thinking about the mechanics of it. Fuse > was geared toward prepackaging everything in that way and hiding its > complexity. So, yeah. > >> 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. > > I can't wait to get time to show you guys this tutorial on how you > can build a parser in just a few minutes. It is really, super easy. > It doesn't have too many complex features in it, true, but I think > as time goes on people will start building those out again. > >> 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 seems more complex. > > Actually that's a misconception right there ? the Fuse style parser > I wrote worked with static methods, where you never see any tween > classes at all. So, yes the tween objects are exposed for OO-style > extensibility, but that does not limit you to that style as your > final end product at all. For example let's say you write a tween > class like HydroTween.. simply add a static method HydroTween.go() > that generates and starts a tween, and you have a totally clean usage. > > I like that it gives you both options ? you can still make a new > tween and store it in your code for reuse, which is far more > efficient than generating one every time, or use the static call to > avoid having to bother making the instance and then starting it. > Even a third usage would be new CustomTween(...).start() which is > pretty much the same as the static call would be, unless the static > method does something special to it. > > Go not about offering "features" that you have to learn, like an API > does. The options that it leaves open are just normal AS3 coding > options that are always there... maybe people are just uncomfortable > not being locked into one narrow way of doing things? > > - m > > > _______________________________________________ > 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/20080304/8cf0c14d/attachment-0001.html From michaelxxoa at gmail.com Tue Mar 4 14:05:05 2008 From: michaelxxoa at gmail.com (Michael Avila) Date: Tue, 4 Mar 2008 14:05:05 -0800 Subject: [Golist] PhysicsGo? In-Reply-To: <47CDC16B.20105@shovemedia.com> References: <47CDC16B.20105@shovemedia.com> Message-ID: <616a462a0803041405r5c07a902r1cba998d2b1fc008@mail.gmail.com> The major similarity seems to be how they are updated (Pulse?). Beyond that each will need it's own syntax, but both do not necessarily need sequencing... On Tue, Mar 4, 2008 at 1:38 PM, Jon Williams wrote: > moses said i should post this here, so: > > curious ... how do you see PhysicsGo fitting in with the tweening engine > stuff? > rigid body dynamics and such seem altogether a different animal than > go-from-this-number-to-this-number-in-this-much-time (and such) > > :j > > _______________________________________________ > 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/20080304/f32c3adf/attachment.html From go at tweego.org Tue Mar 4 22:17:36 2008 From: go at tweego.org (Sebastian Weyrauch) Date: Wed, 5 Mar 2008 07:17:36 +0100 Subject: [Golist] Go: Scary-complicated? In-Reply-To: <48147780-4E36-4B8F-913B-C1BC8613C070@goasap.org> References: <48147780-4E36-4B8F-913B-C1BC8613C070@goasap.org> Message-ID: <006901c87e88$9b7a8890$d26f99b0$@org> Hi, I think Go is really great. But for the "normal" Flash user it's to heavy. But we will see.. (we need some parsers ;)) regards s -----Urspr?ngliche Nachricht----- Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im Auftrag von Moses Gunesch Gesendet: Dienstag, 4. M?rz 2008 17:57 An: Mailing list for the Go ActionScript Animation Platform Betreff: [Golist] Go: Scary-complicated? Hi everyone, So now that the new site is live, let's assess how I did for making Go approachable. Go is actually very simple once you understand it, but before that it intimidates people and seems really complicated. So: Are the goals of Go still confusing? Is the presentation of Go confusing? Is it intimidating, say if you had first seen it at the new site http://www.goasap.org/ ? Is it clear yet that very little is required for the compatibility layer ? just GoEngine, GoEvent, and PlayableBase/IPlayable ? and that everything else is entirely optional? Is it obvious yet that it's very easy to build a tween over LinearGo in 3 easy steps or does that still feel like everest? Here's one idea I had ? a swf slideshow with a "next" nav button, that would walk you through step by step how Go is structured. Because each bit of it is extremely logical and is there for a reason... for example, GoItem is there as an abstract base class for any animation type, not just tweens, and PlayableBase sits at the very core because some things that you can play, are not animations at all, like a Sequence. I want that structure to be really clearly presented but I'm worried that the Architecture page does not show this simply enough.... thanks, Moses _______________________________________________ GoList mailing list GoList at goasap.org http://goasap.org/mailman/listinfo/golist_goasap.org From burak at delizade.com Wed Mar 5 00:37:31 2008 From: burak at delizade.com (Burak Delice) Date: Wed, 5 Mar 2008 10:37:31 +0200 Subject: [Golist] Go: Scary-complicated? In-Reply-To: References: Message-ID: <006701c87e9c$2704c0c0$750e4240$@com> Timothy Uruski wrote "I think the perception of Go being complicated also comes from people's familiarity with Fuse" and definately he is right. I think every developer who used Fuse, are trying/ will try make his own go-fuse version.because I think we got used to it. And actually, I wonder that where is current active Go users' custom tweener classes. I think we need more samples. Angela, I am in same stuation with you. I have little experiance with go, but we want it, we love it and yesJ we are fun of it. So your ides is great Moses. Wee need like that stuff. And according to me, Go is complicated, when I think on it, it seems that "you have to consantrate it and you have to write your own custom tweener, if you dont do that you can not use GO". And that thought makes me feel stressed, makes think that there are lots of things to do/achive. But, of course we have to consantrate on it yes J so, your effort about helping us with some video or presentation material would be very very useful and would be great shurtcuts for us. Regards, Burak From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Timothy Uruski Sent: Tuesday, March 04, 2008 11:00 PM To: golist at goasap.org Subject: Re: [Golist] Go: Scary-complicated? Moses, 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. 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 seems more complex. Tim On 4-Mar-08, at 1:00 PM, golist-request at goasap.org wrote: Send GoList mailing list submissions to golist at goasap.org To subscribe or unsubscribe via the World Wide Web, visit http://goasap.org/mailman/listinfo/golist_goasap.org or, via email, send a message with subject or body 'help' to golist-request at goasap.org You can reach the person managing the list at golist-owner at goasap.org When replying, please edit your Subject line so it is more specific than "Re: Contents of GoList digest..." Today's Topics: 1. Go: Scary-complicated? (Moses Gunesch) 2. Re: Go: Scary-complicated? (Angela Ferraiolo) ---------------------------------------------------------------------- Message: 1 Date: Tue, 4 Mar 2008 11:56:48 -0500 From: Moses Gunesch Subject: [Golist] Go: Scary-complicated? To: Mailing list for the Go ActionScript Animation Platform Message-ID: <48147780-4E36-4B8F-913B-C1BC8613C070 at goasap.org> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Hi everyone, So now that the new site is live, let's assess how I did for making Go approachable. Go is actually very simple once you understand it, but before that it intimidates people and seems really complicated. So: Are the goals of Go still confusing? Is the presentation of Go confusing? Is it intimidating, say if you had first seen it at the new site http://www.goasap.org/ ? Is it clear yet that very little is required for the compatibility layer ? just GoEngine, GoEvent, and PlayableBase/IPlayable ? and that everything else is entirely optional? Is it obvious yet that it's very easy to build a tween over LinearGo in 3 easy steps or does that still feel like everest? Here's one idea I had ? a swf slideshow with a "next" nav button, that would walk you through step by step how Go is structured. Because each bit of it is extremely logical and is there for a reason... for example, GoItem is there as an abstract base class for any animation type, not just tweens, and PlayableBase sits at the very core because some things that you can play, are not animations at all, like a Sequence. I want that structure to be really clearly presented but I'm worried that the Architecture page does not show this simply enough.... thanks, Moses ------------------------------ Message: 2 Date: Tue, 4 Mar 2008 12:22:47 -0500 From: "Angela Ferraiolo" Subject: Re: [Golist] Go: Scary-complicated? To: "Mailing list for the Go ActionScript Animation Platform" Message-ID: <4499c75b0803040922o66462498ibf315fd2178f614f at mail.gmail.com> Content-Type: text/plain; charset=WINDOWS-1252 Hello Moses & the list, Thanks for Go! A .swf walkthough would be awesome! It is not that your site is confusing so much as there is a lot of new stuff to learn right now on all sides. Anything you can do to help speed the process would be greatly wonderful and go-tatstic. Right now Go is still in my "to do" list! But I am a fan. Thank you again, -- Angela On 3/4/08, Moses Gunesch wrote: Hi everyone, So now that the new site is live, let's assess how I did for making Go approachable. Go is actually very simple once you understand it, but before that it intimidates people and seems really complicated. So: Are the goals of Go still confusing? Is the presentation of Go confusing? Is it intimidating, say if you had first seen it at the new site http://www.goasap.org/ ? Is it clear yet that very little is required for the compatibility layer ? just GoEngine, GoEvent, and PlayableBase/IPlayable ? and that everything else is entirely optional? Is it obvious yet that it's very easy to build a tween over LinearGo in 3 easy steps or does that still feel like everest? Here's one idea I had ? a swf slideshow with a "next" nav button, that would walk you through step by step how Go is structured. Because each bit of it is extremely logical and is there for a reason... for example, GoItem is there as an abstract base class for any animation type, not just tweens, and PlayableBase sits at the very core because some things that you can play, are not animations at all, like a Sequence. I want that structure to be really clearly presented but I'm worried that the Architecture page does not show this simply enough.... thanks, Moses _______________________________________________ GoList mailing list GoList at goasap.org http://goasap.org/mailman/listinfo/golist_goasap.org ------------------------------ _______________________________________________ GoList mailing list GoList at goasap.org http://goasap.org/mailman/listinfo/golist_goasap.org End of GoList Digest, Vol 4, Issue 1 ************************************ __________ Informazione NOD32 2921 (20080304) __________ Questo messaggio ? stato controllato dal Sistema Antivirus NOD32 http://www.nod32.it -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080305/861f89eb/attachment-0001.html From KarstenGoetz at web.de Wed Mar 5 01:01:05 2008 From: KarstenGoetz at web.de (Karsten Goetz) Date: Wed, 5 Mar 2008 10:01:05 +0100 Subject: [Golist] the possibilities of go Message-ID: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> Hi Moses, i don't think Go is to complicated. But I think tutorials would be great. It's true that the learning curve at the beginning is higher compared to Tween engines like Fuse - but at the other hand it gives us a great flexibilities and possibilities. It's great to have examples, like HydroTween and your tutorials. But for a lot of people the "ready to go" aspect of an tweenengine counts and they turn around when it's not usable in some minutes . Go can do that and we have to create a playground to show. Hope I can send my part soon :-) Greetings Karsten ------------------------ Karsten Goetz Flashprogrammierung Bernstorffstr. 120 22767 Hamburg Tel: +49 40 43 09 91 07 Mobil: 0173 57 14 984 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080305/1ba51711/attachment.html From curt at fastspot.com Wed Mar 5 06:04:59 2008 From: curt at fastspot.com (Curt Kotula) Date: Wed, 5 Mar 2008 09:04:59 -0500 Subject: [Golist] the possibilities of go In-Reply-To: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> References: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> Message-ID: <1B5AC840-8391-4DB6-BDBB-EE44133F1FC5@fastspot.com> 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 On Mar 5, 2008, at 4:01 AM, Karsten Goetz wrote: > Hi Moses, > > i don't think Go is to complicated. But I think tutorials would be > great. > It's true that the learning curve at the beginning is higher > compared to Tween engines like Fuse - but at the other hand it gives > us a great flexibilities and possibilities. > > It's great to have examples, like HydroTween and your tutorials. But > for a lot of people the "ready to go" aspect of an tweenengine > counts and they turn around when it's not usable in some minutes . > Go can do that and we have to create a playground to show. > Hope I can send my part soon :-) > > Greetings > Karsten > > > > > > > ------------------------ > 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 From donovan at hydrotik.com Wed Mar 5 06:21:06 2008 From: donovan at hydrotik.com (donovan at hydrotik.com) Date: Wed, 05 Mar 2008 09:21:06 -0500 Subject: [Golist] the possibilities of go In-Reply-To: <1B5AC840-8391-4DB6-BDBB-EE44133F1FC5@fastspot.com> Message-ID: Sorry to post this to the list. Curt I tried emailing you back a few times and my emails got bounced back. There are spots for a complete, and an update callback in the static arguments so you don't need to return an instance of the tween and add the listeners. However I did add the return type for future needs. HydroTween.go(target, {scaleX:(original_scaleX + .2),scaleY:(original_scaleY + .2)}, .25, 0, Quartic.easeInOut, null, reCenter);? The null arg in front of your update callback is the onComplete callback argument fyi I updated the SVN with the return type. http://code.google.com/p/goplayground/downloads/list On 3/5/08 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 > > > On Mar 5, 2008, at 4:01 AM, Karsten Goetz wrote: > >> Hi Moses, >> >> i don't think Go is to complicated. But I think tutorials would be >> great. >> It's true that the learning curve at the beginning is higher >> compared to Tween engines like Fuse - but at the other hand it gives >> us a great flexibilities and possibilities. >> >> It's great to have examples, like HydroTween and your tutorials. But >> for a lot of people the "ready to go" aspect of an tweenengine >> counts and they turn around when it's not usable in some minutes . >> Go can do that and we have to create a playground to show. >> Hope I can send my part soon :-) >> >> Greetings >> Karsten >> >> >> >> >> >> >> ------------------------ >> 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 > > > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org From jon at shovemedia.com Wed Mar 5 06:46:08 2008 From: jon at shovemedia.com (Jon Williams) Date: Wed, 05 Mar 2008 09:46:08 -0500 Subject: [Golist] the possibilities of go In-Reply-To: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> References: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> Message-ID: <47CEB230.4000109@shovemedia.com> i think the only thing i'd change is adding a public extra:* prop on LinearGo (same as there is on GoEvent). Though i'm not sure if that slows things down due to less-specific strong-typing... for my purposes, that simplifies the whole setup immensely because i don't even have to subclass anything (and you KNOW people find subclasses pretty daunting): create a linearGo, add the listeners, start it up, inside the update event, i can get my object(s) and property(s) from the extra obj above and pull the position via GoEvent.target.position. from there convert from a percent to actual coordinates or whatever right inside the event listener. done! :j From moses at goasap.org Wed Mar 5 08:46:14 2008 From: moses at goasap.org (Moses Gunesch) Date: Wed, 5 Mar 2008 11:46:14 -0500 Subject: [Golist] the possibilities of go In-Reply-To: <47CEB230.4000109@shovemedia.com> References: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> <47CEB230.4000109@shovemedia.com> Message-ID: John, that's not a good idea, sorry. :) That defeats all the benefits that as3 offers, you're still thinking like an AS2 coder. The object that you add there would not be strictly typed and so you are once again back in the dark ages of having to hunt and peck for hours to track down mystery bugs. That's what strict typing is for really, is to tighten up the ship so you can much more specifically determine where and when bugs occur. There is no reason to fear subclassing. It's extremely simple, you just need to know a little bit how it works. When you create a subclass you inherit all the public and protected methods of the superclass(es). You also have access to call the immediate parent superclass' functions using the keyword super, like super.start(). This is handy because you can choose where in your overridden method to call the super's method.. sometimes you need it to be before some of your code, other times after, still others you might simply replace the method's functionality entirely by not ever calling the super's method. The only thing that is restrictive about AS3 is that overridden methods have to "match" the super methods as far as input datatypes and return datatype, and can't add or remove parameters... personally I don't like this at all and it's making it hard to build an open platform! (For example, you can't add a named parameter to your subclass' start method without actually modifying the base class... this is terribly restrictive.) But in general, I'd say watch the LinearGo tutorial until you understand what I'm doing with it, it's really not that difficult and, since you're a professional who codes you really should take the time to know how to do OO. I'm here for you if you have questions along the way. - m PS I created an example called BlockTweenMG that lets you assign and tween multiple properties very easily.. it's the same as the MotionTween example but it uses a couple of arrays to store props & endvals, then loops through the arrays to store tween start & changevals in a few more arrays. So, this sort of structural difference is significant and LinearGo leaves that open for subclasses so it is not too restricting. Give it a try! On Mar 5, 2008, at 9:46 AM, Jon Williams wrote: > i think the only thing i'd change is adding a public extra:* prop on > LinearGo > (same as there is on GoEvent). Though i'm not sure if that slows > things > down due to > less-specific strong-typing... > > for my purposes, that simplifies the whole setup immensely because > i don't even have to subclass anything (and you KNOW people find > subclasses pretty daunting): > > create a linearGo, add the listeners, start it up, > inside the update event, i can get my object(s) and property(s) from > the > extra obj above and pull the position via GoEvent.target.position. > from there convert from a percent to actual > coordinates or whatever right inside the event listener. > > done! > > :j From moses at goasap.org Wed Mar 5 08:55:33 2008 From: moses at goasap.org (Moses Gunesch) Date: Wed, 5 Mar 2008 11:55:33 -0500 Subject: [Golist] the possibilities of go In-Reply-To: <1B5AC840-8391-4DB6-BDBB-EE44133F1FC5@fastspot.com> References: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> <1B5AC840-8391-4DB6-BDBB-EE44133F1FC5@fastspot.com> Message-ID: <97466D41-A35F-4372-BB62-9E4A5CD6F973@goasap.org> 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 From jon at shovemedia.com Wed Mar 5 09:03:48 2008 From: jon at shovemedia.com (Jon Williams) Date: Wed, 05 Mar 2008 12:03:48 -0500 Subject: [Golist] the possibilities of go In-Reply-To: References: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> <47CEB230.4000109@shovemedia.com> Message-ID: <47CED274.4010203@shovemedia.com> it's not that i don't understand (or use) subclassing; AS2 has strong-typing and subclassing etc too let's not forget. i was just thinking about it from a newbie POV. that said, i am *quite* an AS3 noob and haven't yet worked on anything sufficiently complex that strong-typing has had the opportunity to save my hide. if the 'extra' prop is such a rotten approach, then i suggest removing it from GoEvent (unless you can tell me how that's different) ; ) Afterall, you should just subclass GoEvent... :j Moses Gunesch wrote: > John, that's not a good idea, sorry. :) > > That defeats all the benefits that as3 offers, you're still thinking > like an AS2 coder. The object that you add there would not be strictly > typed and so you are once again back in the dark ages of having to > hunt and peck for hours to track down mystery bugs. That's what strict > typing is for really, is to tighten up the ship so you can much more > specifically determine where and when bugs occur. > > There is no reason to fear subclassing. It's extremely simple, you > just need to know a little bit how it works. When you create a > subclass you inherit all the public and protected methods of the > superclass(es). You also have access to call the immediate parent > superclass' functions using the keyword super, like super.start(). > This is handy because you can choose where in your overridden method > to call the super's method.. sometimes you need it to be before some > of your code, other times after, still others you might simply replace > the method's functionality entirely by not ever calling the super's > method. The only thing that is restrictive about AS3 is that > overridden methods have to "match" the super methods as far as input > datatypes and return datatype, and can't add or remove parameters... > personally I don't like this at all and it's making it hard to build > an open platform! (For example, you can't add a named parameter to > your subclass' start method without actually modifying the base > class... this is terribly restrictive.) > > But in general, I'd say watch the LinearGo tutorial until you > understand what I'm doing with it, it's really not that difficult and, > since you're a professional who codes you really should take the time > to know how to do OO. I'm here for you if you have questions along the > way. > > - m > > PS I created an example called BlockTweenMG that lets you assign and > tween multiple properties very easily.. it's the same as the > MotionTween example but it uses a couple of arrays to store props & > endvals, then loops through the arrays to store tween start & > changevals in a few more arrays. So, this sort of structural > difference is significant and LinearGo leaves that open for subclasses > so it is not too restricting. Give it a try! > > > > On Mar 5, 2008, at 9:46 AM, Jon Williams wrote: > > >> i think the only thing i'd change is adding a public extra:* prop on >> LinearGo >> (same as there is on GoEvent). Though i'm not sure if that slows >> things >> down due to >> less-specific strong-typing... >> >> for my purposes, that simplifies the whole setup immensely because >> i don't even have to subclass anything (and you KNOW people find >> subclasses pretty daunting): >> >> create a linearGo, add the listeners, start it up, >> inside the update event, i can get my object(s) and property(s) from >> the >> extra obj above and pull the position via GoEvent.target.position. >> from there convert from a percent to actual >> coordinates or whatever right inside the event listener. >> >> done! >> >> :j >> > > > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org > From moses at goasap.org Wed Mar 5 16:18:09 2008 From: moses at goasap.org (Moses Gunesch) Date: Wed, 5 Mar 2008 19:18:09 -0500 Subject: [Golist] the possibilities of go In-Reply-To: <47CED274.4010203@shovemedia.com> References: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> <47CEB230.4000109@shovemedia.com> <47CED274.4010203@shovemedia.com> Message-ID: <017D6DE7-5387-457B-B025-FEB3EF083AF0@goasap.org> That's true and so far it hasn't really come in handy at all. I had put it in there so it would be easy to pass target or prop info but it's also easy to just add those params since it's all open code. You are right that I should probably remove that since it simply encourages bad practice, I just didn't want it to be terribly restrictive either... will revisit. - m On Mar 5, 2008, at 12:03 PM, Jon Williams wrote: > if the 'extra' prop is such a rotten approach, then i suggest > removing it from GoEvent (unless you can tell me how that's > different) ; ) Afterall, you should just subclass GoEvent... > :j From separ8 at gmail.com Wed Mar 5 16:42:02 2008 From: separ8 at gmail.com (Brett Coffin) Date: Thu, 6 Mar 2008 10:42:02 +1000 Subject: [Golist] the possibilities of go In-Reply-To: <017D6DE7-5387-457B-B025-FEB3EF083AF0@goasap.org> References: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> <47CEB230.4000109@shovemedia.com> <47CED274.4010203@shovemedia.com> <017D6DE7-5387-457B-B025-FEB3EF083AF0@goasap.org> Message-ID: Hi everyone, Moses, i love the concept of Go i thing it will "go" all the way !!! I understand the concept of the parser in regards to xml but i don't have a clear idea of what would be a parser for go, could you extend on it... the way i am think of it is: you created a syntax like the fuse for example and the parser is receiving it and then would "dispatch" the task to tween particular parameters to the respective tweening class... is that correct ? Could you make your parser available ? On Thu, Mar 6, 2008 at 10:18 AM, Moses Gunesch wrote: > That's true and so far it hasn't really come in handy at all. I had > put it in there so it would be easy to pass target or prop info but > it's also easy to just add those params since it's all open code. You > are right that I should probably remove that since it simply > encourages bad practice, I just didn't want it to be terribly > restrictive either... will revisit. > > - m > > > On Mar 5, 2008, at 12:03 PM, Jon Williams wrote: > > > if the 'extra' prop is such a rotten approach, then i suggest > > removing it from GoEvent (unless you can tell me how that's > > different) ; ) Afterall, you should just subclass GoEvent... > > :j > > > _______________________________________________ > 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/20080306/e3b8eecf/attachment.html From moses at goasap.org Wed Mar 5 18:44:14 2008 From: moses at goasap.org (Moses Gunesch) Date: Wed, 5 Mar 2008 21:44:14 -0500 Subject: [Golist] the possibilities of go In-Reply-To: References: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> <47CEB230.4000109@shovemedia.com> <47CED274.4010203@shovemedia.com> <017D6DE7-5387-457B-B025-FEB3EF083AF0@goasap.org> Message-ID: <3FE9A89F-FD38-4139-9926-9468AFB6184F@goasap.org> I started with a simple multi-prop tween, then created a separate parser class with 2 public static methods called BlockParserMG: public static function go(action:Object): BlockTweenMG { // parse, start & return a tween var tween:BlockTweenMG = parseAction(action); tween.start(); return tween; } public static function sequence(...actions): SequenceCA { // parse, start, and return a sequence } private static function parseAction(action : Object) : BlockTweenMG { // used by both. parse one action object and return a tween. } I built SequenceStepCA's during the sequence() loop because that way i could support custom-advance. I checked for "is Array" for each action passed in and would parse each sub-object within it to support parallel. That's just a few lines of code to do both of those things then sequence.addStep(step);. The parser is literally one if() statement for the custom-advance and one if() to see if the property being parsed is a tween property (tween.hasOwnProperty(prop)) or should else just be added as an animation property. That's it... simple! And ... works! -m On Mar 5, 2008, at 7:42 PM, Brett Coffin wrote: > Hi everyone, > > Moses, i love the concept of Go i thing it will "go" all the way !!! > > I understand the concept of the parser in regards to xml but i don't > have a clear idea of what would be a parser for go, could you extend > on it... the way i am think of it is: > > you created a syntax like the fuse for example and the parser is > receiving it and then would "dispatch" the task to tween particular > parameters to the respective tweening class... is that correct ? > Could you make your parser available ? > > > > > > On Thu, Mar 6, 2008 at 10:18 AM, Moses Gunesch > wrote: > That's true and so far it hasn't really come in handy at all. I had > put it in there so it would be easy to pass target or prop info but > it's also easy to just add those params since it's all open code. You > are right that I should probably remove that since it simply > encourages bad practice, I just didn't want it to be terribly > restrictive either... will revisit. > > - m > > > On Mar 5, 2008, at 12:03 PM, Jon Williams wrote: > > > if the 'extra' prop is such a rotten approach, then i suggest > > removing it from GoEvent (unless you can tell me how that's > > different) ; ) Afterall, you should just subclass GoEvent... > > :j > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080305/da1d50db/attachment.html From go at tweego.org Wed Mar 5 22:07:11 2008 From: go at tweego.org (Sebastian Weyrauch) Date: Thu, 6 Mar 2008 07:07:11 +0100 Subject: [Golist] the possibilities of go In-Reply-To: <3FE9A89F-FD38-4139-9926-9468AFB6184F@goasap.org> References: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> <47CEB230.4000109@shovemedia.com> <47CED274.4010203@shovemedia.com> <017D6DE7-5387-457B-B025-FEB3EF083AF0@goasap.org> <3FE9A89F-FD38-4139-9926-9468AFB6184F@goasap.org> Message-ID: <00c901c87f50$5161bc10$f4253430$@org> Hi Moses, I'dont like the static methods. Some extract of tweego: public function add(...args):uint { for(var i:int = 0; i0); } continue; } seq.addStep(getItem(args[i])); } return i; } public function push(...args):uint { return add.apply(this, args); } protected function getItem(o:Object):TweegoItem { } I think I will upload a version this weekend. I'm not very far, but need some help - have not enough time. Do you remember the problem with the weak references in a class usage? Do you have solved it in the current version? (I work with a hacked version of Go at the moment) sebastian Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im Auftrag von Moses Gunesch Gesendet: Donnerstag, 6. M?rz 2008 03:44 An: Mailing list for the Go ActionScript Animation Platform Betreff: Re: [Golist] the possibilities of go I started with a simple multi-prop tween, then created a separate parser class with 2 public static methods called BlockParserMG: public static function go(action:Object): BlockTweenMG { // parse, start & return a tween var tween:BlockTweenMG = parseAction(action); tween.start(); return tween; } public static function sequence(...actions): SequenceCA { // parse, start, and return a sequence } private static function parseAction(action : Object) : BlockTweenMG { // used by both. parse one action object and return a tween. } I built SequenceStepCA's during the sequence() loop because that way i could support custom-advance. I checked for "is Array" for each action passed in and would parse each sub-object within it to support parallel. That's just a few lines of code to do both of those things then sequence.addStep(step);. The parser is literally one if() statement for the custom-advance and one if() to see if the property being parsed is a tween property (tween.hasOwnProperty(prop)) or should else just be added as an animation property. That's it... simple! And ... works! -m On Mar 5, 2008, at 7:42 PM, Brett Coffin wrote: Hi everyone, Moses, i love the concept of Go i thing it will "go" all the way !!! I understand the concept of the parser in regards to xml but i don't have a clear idea of what would be a parser for go, could you extend on it... the way i am think of it is: you created a syntax like the fuse for example and the parser is receiving it and then would "dispatch" the task to tween particular parameters to the respective tweening class... is that correct ? Could you make your parser available ? On Thu, Mar 6, 2008 at 10:18 AM, Moses Gunesch wrote: That's true and so far it hasn't really come in handy at all. I had put it in there so it would be easy to pass target or prop info but it's also easy to just add those params since it's all open code. You are right that I should probably remove that since it simply encourages bad practice, I just didn't want it to be terribly restrictive either... will revisit. - m On Mar 5, 2008, at 12:03 PM, Jon Williams wrote: > if the 'extra' prop is such a rotten approach, then i suggest > removing it from GoEvent (unless you can tell me how that's > different) ; ) Afterall, you should just subclass GoEvent... > :j -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080306/cdc0ad09/attachment-0001.html From moses at goasap.org Thu Mar 6 01:40:15 2008 From: moses at goasap.org (Moses Gunesch) Date: Thu, 6 Mar 2008 04:40:15 -0500 Subject: [Golist] the possibilities of go In-Reply-To: <00c901c87f50$5161bc10$f4253430$@org> References: <8C567F9F-3CD1-4A14-801E-D6744043E354@web.de> <47CEB230.4000109@shovemedia.com> <47CED274.4010203@shovemedia.com> <017D6DE7-5387-457B-B025-FEB3EF083AF0@goasap.org> <3FE9A89F-FD38-4139-9926-9468AFB6184F@goasap.org> <00c901c87f50$5161bc10$f4253430$@org> Message-ID: <369EBBD1-FE40-4996-B830-005C778A40FE@goasap.org> On Mar 6, 2008, at 1:07 AM, Sebastian Weyrauch wrote: > Do you remember the problem with the weak references in a class > usage? Do you have solved it in the current version? (I work with a > hacked version of Go at the moment) > Tweego looks cool! Yes that problem has been resolved... there is a private static property added to PlayableBase called playRetainer that non-GoEngine playbles can use to stash a reference to themselves during play, and SequenceBase now does that. - m -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080306/52e2aa27/attachment.html From moses at goasap.org Thu Mar 6 10:37:42 2008 From: moses at goasap.org (Moses Gunesch) Date: Thu, 6 Mar 2008 13:37:42 -0500 Subject: [Golist] Go Video Tutorial #2: Sequence Parser In-Reply-To: References: <003001c86fad$7f534c90$7df9e5b0$@com> Message-ID: This tutorial walks you through one way you could create a Fuse-style tween & sequence parser. But remember, this is just one way... You should build things to work the way you like 'em to! Both tutorials should be linked here?if not try Refreshing your browser. (Be sure to watch #1 first!) http://www.goasap.org/developers.html Enjoy! Moses From robert at bennybula.com Thu Mar 6 11:30:11 2008 From: robert at bennybula.com (=?WINDOWS-1252?Q?Robert_Sk=F6ld?=) Date: Thu, 6 Mar 2008 20:30:11 +0100 Subject: [Golist] Go Video Tutorial #2: Sequence Parser In-Reply-To: References: <003001c86fad$7f534c90$7df9e5b0$@com> Message-ID: That's awesome moses! Just what I was wondering about, how the sequencing was to be used. I'll be using Go on my current project, it'll use an XML based parser, I'll probably share it with you guys when it's done (unless it's terrible :P). I'm really looking forward to digging into it. :) /bob On Mar 6, 2008, at 19:37, Moses Gunesch wrote: > This tutorial walks you through one way you could create a Fuse-style > tween & sequence parser. > > But remember, this is just one way... You should build things to work > the way you like 'em to! > > Both tutorials should be linked here?if not try Refreshing your > browser. (Be sure to watch #1 first!) > http://www.goasap.org/developers.html > > Enjoy! > Moses > > > > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org From moses at goasap.org Thu Mar 6 11:36:15 2008 From: moses at goasap.org (Moses Gunesch) Date: Thu, 6 Mar 2008 14:36:15 -0500 Subject: [Golist] Go Video Tutorial #2: Sequence Parser In-Reply-To: References: <003001c86fad$7f534c90$7df9e5b0$@com> Message-ID: Great! I love the concept of an XML parser but the one issue I have with it is that it's so hard to tie directly into your actual code elements such as display objects, callbacks, etc. Flex has a way of making it look like you can do more than you really can. Like in regular E4X you can do something like target="{mySprite"} but it doesn't store a reference to the real sprite in the XML object, unfortunately.. at least not that I can figure. I think that's why Penner's paste motion as AS3 classes accept a direct reference to a target object in the constructor, then the XML secondarily. - m On Mar 6, 2008, at 2:30 PM, Robert Sk?ld wrote: > That's awesome moses! > > Just what I was wondering about, how the sequencing was to be used. > > I'll be using Go on my current project, it'll use an XML based parser, > I'll probably share it with you guys when it's done (unless it's > terrible :P). > > I'm really looking forward to digging into it. :) > > /bob > > On Mar 6, 2008, at 19:37, Moses Gunesch wrote: > >> This tutorial walks you through one way you could create a Fuse-style >> tween & sequence parser. >> >> But remember, this is just one way... You should build things to work >> the way you like 'em to! >> >> Both tutorials should be linked here?if not try Refreshing your >> browser. (Be sure to watch #1 first!) >> http://www.goasap.org/developers.html >> >> Enjoy! >> Moses >> >> >> >> _______________________________________________ >> GoList mailing list >> GoList at goasap.org >> http://goasap.org/mailman/listinfo/golist_goasap.org > > > _______________________________________________ > 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/20080306/c482cbf1/attachment.html From burak at delizade.com Thu Mar 6 11:51:05 2008 From: burak at delizade.com (Burak Delice) Date: Thu, 6 Mar 2008 21:51:05 +0200 Subject: [Golist] Go Video Tutorial #2: Sequence Parser In-Reply-To: References: <003001c86fad$7f534c90$7df9e5b0$@com> Message-ID: <006201c87fc3$6bcdd160$43697420$@com> Thankyou very much Moses. Burak. -----Original Message----- From: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] On Behalf Of Moses Gunesch Sent: Thursday, March 06, 2008 8:38 PM To: Mailing list for the Go ActionScript Animation Platform Subject: [Golist] Go Video Tutorial #2: Sequence Parser This tutorial walks you through one way you could create a Fuse-style tween & sequence parser. But remember, this is just one way... You should build things to work the way you like 'em to! Both tutorials should be linked here-if not try Refreshing your browser. (Be sure to watch #1 first!) http://www.goasap.org/developers.html Enjoy! Moses _______________________________________________ GoList mailing list GoList at goasap.org http://goasap.org/mailman/listinfo/golist_goasap.org __________ Informazione NOD32 2927 (20080306) __________ Questo messaggio ? stato controllato dal Sistema Antivirus NOD32 http://www.nod32.it From moses at goasap.org Thu Mar 6 11:57:25 2008 From: moses at goasap.org (Moses Gunesch) Date: Thu, 6 Mar 2008 14:57:25 -0500 Subject: [Golist] Go Video Tutorial #2: Sequence Parser In-Reply-To: <006201c87fc3$6bcdd160$43697420$@com> References: <003001c86fad$7f534c90$7df9e5b0$@com> <006201c87fc3$6bcdd160$43697420$@com> Message-ID: <953F1464-F712-4643-AF14-48626A93FA82@goasap.org> :) On Mar 6, 2008, at 2:51 PM, Burak Delice wrote: > Thankyou very much Moses. > > > Burak. From moses at goasap.org Thu Mar 6 20:57:27 2008 From: moses at goasap.org (Moses Gunesch) Date: Thu, 6 Mar 2008 23:57:27 -0500 Subject: [Golist] Video tutorial source files In-Reply-To: <953F1464-F712-4643-AF14-48626A93FA82@goasap.org> References: <003001c86fad$7f534c90$7df9e5b0$@com> <006201c87fc3$6bcdd160$43697420$@com> <953F1464-F712-4643-AF14-48626A93FA82@goasap.org> Message-ID: <8E3CFC6F-5E56-4C23-8E6C-07DCD893DAED@goasap.org> files are on the svn at GoPlayground. -m From moses at goasap.org Fri Mar 7 06:42:09 2008 From: moses at goasap.org (Moses Gunesch) Date: Fri, 7 Mar 2008 09:42:09 -0500 Subject: [Golist] PhysicsGo? In-Reply-To: <616a462a0803041405r5c07a902r1cba998d2b1fc008@mail.gmail.com> References: <47CDC16B.20105@shovemedia.com> <616a462a0803041405r5c07a902r1cba998d2b1fc008@mail.gmail.com> Message-ID: <046B459E-4054-4CDA-A263-8D4291F55AB2@goasap.org> I don't think the ultimate system has necessarily been developed yet. For example, why shouldn't physics be sequenceable along with tweens? Sure, many physics animations are open ended but then again many of them might have natural endings where they would be considered done within an app, such as a game. Laser blast goes off screen, rock bounces to ground then comes to rest, etc. It's totally possible that there are systems yet to design here. Physics is new territory for Go and one looming question is how much of various physics systems (particle / rigid body / constraint based etc.) could be "layered" in the same way tween functionality can be. It might be that it can't, and having a unified pulse would be as good as it gets, I'm not sure yet! Even if it's only sharing a pulse, that's a big deal. Imagine trying to run a highly optimized particle system in a real-world program that might also include a tween engine, PV3D or other pulse-based systems that do rendering. Efficiency of all systems is badly compromised, and there is no way to make them play well together. Go is an attempt to offer that by saying hey, even if we only end up sharing centralized update lists, that's a really big deal for efficiency. Eventually it might turn out that we can add common physics events to the core system as well which will also make it easier to tie things together, and it may emerge that physics is layerable in other ways... Open for suggestions! -m On Mar 4, 2008, at 5:05 PM, Michael Avila wrote: > The major similarity seems to be how they are updated (Pulse?). > Beyond that each will need it's own syntax, but both do not > necessarily need sequencing... > > > On Tue, Mar 4, 2008 at 1:38 PM, Jon Williams > wrote: > moses said i should post this here, so: > > curious ... how do you see PhysicsGo fitting in with the tweening > engine > stuff? > rigid body dynamics and such seem altogether a different animal than > go-from-this-number-to-this-number-in-this-much-time (and such) > > :j > > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org > > _______________________________________________ > 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/20080307/1c10d730/attachment.html From newsl at analogdesign.ch Sat Mar 8 06:09:44 2008 From: newsl at analogdesign.ch (Cedric M. analogdesign) Date: Sat, 8 Mar 2008 15:09:44 +0100 Subject: [Golist] hydrotween Go groups and sequences? In-Reply-To: Message-ID: Hi Donovan, I've just got vers 0.4.4 of HydroTween. I wonder if it possible to use GO groups and sequences with your HydroTweens? Thank you in advance for your answer. Thank oyu for your work! Best regards. Cedric M. (aka maddec) Interactive Creative Adobe Flash/Flex/AIR Specialist Since 1998 ---------------------------------------------------- http://analogdesign.ch http://analogdesign.ch/blog visual & interactive communication ---------------------------------------------------- From donovan at hydrotik.com Sat Mar 8 08:09:15 2008 From: donovan at hydrotik.com (donovan at hydrotik.com) Date: Sat, 08 Mar 2008 11:09:15 -0500 Subject: [Golist] hydrotween Go groups and sequences? Message-ID: In the version that's up there no, But I have been working on an updated version that will. I added a property class and have also converted array targets to using playable group. I started working on sequences so I will have that going in the next rev. I made a considerable amount of changes and refactoring which is why it's taking me a bit longer to get the next rev up:) So to answer your question, yes. It might not all be in the next rev, but along with the performance changes I should have sequencing up. On 3/8/08 9:09 AM, "Cedric M. analogdesign" wrote: > Hi Donovan, > > I've just got vers 0.4.4 of HydroTween. > > I wonder if it possible to use GO groups and sequences with your > HydroTweens? > > > Thank you in advance for your answer. > Thank oyu for your work! > > > Best regards. > > Cedric M. (aka maddec) > > Interactive Creative > Adobe Flash/Flex/AIR Specialist > Since 1998 > ---------------------------------------------------- > http://analogdesign.ch > http://analogdesign.ch/blog > visual & interactive communication > ---------------------------------------------------- > > > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org From moses at goasap.org Sat Mar 8 11:43:06 2008 From: moses at goasap.org (Moses Gunesch) Date: Sat, 8 Mar 2008 14:43:06 -0500 Subject: [Golist] Video tutorial source files In-Reply-To: <8E3CFC6F-5E56-4C23-8E6C-07DCD893DAED@goasap.org> References: <003001c86fad$7f534c90$7df9e5b0$@com> <006201c87fc3$6bcdd160$43697420$@com> <953F1464-F712-4643-AF14-48626A93FA82@goasap.org> <8E3CFC6F-5E56-4C23-8E6C-07DCD893DAED@goasap.org> Message-ID: I just added a zip download of the video tutorial source files at the playground as well. - m On Mar 6, 2008, at 11:57 PM, Moses Gunesch wrote: > files are on the svn at GoPlayground. > > -m From moses at goasap.org Sat Mar 8 15:21:43 2008 From: moses at goasap.org (Moses Gunesch) Date: Sat, 8 Mar 2008 18:21:43 -0500 Subject: [Golist] blog posts In-Reply-To: References: <003001c86fad$7f534c90$7df9e5b0$@com> <006201c87fc3$6bcdd160$43697420$@com> <953F1464-F712-4643-AF14-48626A93FA82@goasap.org> <8E3CFC6F-5E56-4C23-8E6C-07DCD893DAED@goasap.org> Message-ID: <97F3E058-97FA-4228-B823-7434EA4A20EB@goasap.org> I posted about the new video tutorial and Go Playground so, cat's outa the bag folks! Please blog about these new articles, all of your blogs are actually the best way to spread the word about Go. Thanks! http://go.mosessupposes.com/ :) From newsl at analogdesign.ch Sun Mar 9 03:25:51 2008 From: newsl at analogdesign.ch (Cedric M. analogdesign) Date: Sun, 9 Mar 2008 11:25:51 +0100 Subject: [Golist] blog posts In-Reply-To: <97F3E058-97FA-4228-B823-7434EA4A20EB@goasap.org> Message-ID: Done, Added to the post on Video tutorials ;) Congratulations for number 2 ! Very interesting and it was a good idea to show the equivalence with timeline in Flash! By far clearer. Best regards. Cedric M. (aka maddec) Interactive Creative Adobe Flash/Flex/AIR Specialist since 1998 ---------------------------------------------------- http://analogdesign.ch http://analogdesign.ch/blog visual & interactive communication ---------------------------------------------------- >-----Message d'origine----- >De : golist-bounces at goasap.org >[mailto:golist-bounces at goasap.org] De la part de Moses Gunesch >Envoy? : dimanche, 9. mars 2008 00:22 >? : Mailing list for the Go ActionScript Animation Platform >Objet : [Golist] blog posts > >I posted about the new video tutorial and Go Playground so, >cat's outa >the bag folks! > >Please blog about these new articles, all of your blogs are actually >the best way to spread the word about Go. Thanks! > >http://go.mosessupposes.com/ > >:) > >_______________________________________________ >GoList mailing list >GoList at goasap.org >http://goasap.org/mailman/listinfo/golist_goasap.org > From KarstenGoetz at web.de Sun Mar 9 05:41:45 2008 From: KarstenGoetz at web.de (Karsten Goetz) Date: Sun, 9 Mar 2008 13:41:45 +0100 Subject: [Golist] Go Tween Library, new example Message-ID: Hi there, last month I post an idea for a tween library structure for "go-tweens". Now I post some classes and would like to know from you if that is a good idea and maybe could work for a library anyone can quickly use, expand and share tweens. I have not tested it yet with sequencing and performance. Here some code form the example to show how parameters are passed // pre-define parameters with the value objects. can be usefull if there are a lot of parameters or for often used animation settings var startFormatVo : TextFormatVO = new TextFormatVO(); startFormatVo.size = 1; startFormatVo.letterSpacing = 50; startFormatVo.leading = 10; var endFormatVo : TextFormatVO = new TextFormatVO(); endFormatVo.size = 25; endFormatVo.letterSpacing = 3; endFormatVo.leading = 15; group = new PlayableGroup(); // if startvalue is null, the tween takes the instance parameters group.addChild(new ClipTween(textField, null, {alpha:1}, 0, .4, Linear.easeIn)); // start and endvalues as objects, most common and quick use... group.addChild(new ClipTween(textField, {y:200}, {y:50}, 0, 1, Bounce.easeOut)); // start and endvalues predefined with value objects group.addChild(new TextFormatTween(textField, startFormatVo, endFormatVo, 0, 1, Bounce.easeOut)); // start defined inline with the value object, endvalue defined with a DropShadowFilter ( returned from the function endFilter() ). Only the tweenable values of the valueobject will be used group.addChild(new DropShadowTween(textField, new DropShadowVO(10, 50, 0x000000, 1, 50, 45, 20), endFilter(), 0, 1, Linear.easeNone)); It's build upon Moses Tween-example plus ValueObject classes to define the tweenable parameters. Try the example and let me know what you think... Ehm, and can anybody tell me how to answer to a specific post. I only can open a new thread via golist at goasap.org - hm, i know it's easy...:-) Greetings! karsten ? ------------------------ Karsten Goetz Flashprogrammierung Bernstorffstr. 120 22767 Hamburg Tel: +49 40 43 09 91 07 Mobil: 0173 57 14 984 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080309/2f006e37/attachment-0002.html -------------- next part -------------- A non-text attachment was scrubbed... Name: classes.zip Type: application/zip Size: 207607 bytes Desc: not available Url : http://goasap.org/pipermail/golist_goasap.org/attachments/20080309/2f006e37/attachment-0001.zip -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080309/2f006e37/attachment-0003.html From moses at goasap.org Sun Mar 9 13:12:28 2008 From: moses at goasap.org (Moses Gunesch) Date: Sun, 9 Mar 2008 16:12:28 -0400 Subject: [Golist] Go Tween Library, new example In-Reply-To: References: Message-ID: <432A3859-A3F1-4E6A-9FC0-369D7F3842FB@goasap.org> You just reply to any post and it will go back to the list. I like your VO ideas, and will check out the classes! -m On Mar 9, 2008, at 8:41 AM, Karsten Goetz wrote: > Ehm, and can anybody tell me how to answer to a specific post. From moses at goasap.org Sun Mar 9 13:13:10 2008 From: moses at goasap.org (Moses Gunesch) Date: Sun, 9 Mar 2008 16:13:10 -0400 Subject: [Golist] blog posts In-Reply-To: <97F3E058-97FA-4228-B823-7434EA4A20EB@goasap.org> Message-ID: Thanks Cedric! I'm glad that one person likes the new video tutorial, at least. -m On Mar 9, 2008, at 6:25 AM, Cedric M. analogdesign wrote: > Done, > > Added to the post on Video tutorials ;) > Congratulations for number 2 ! Very interesting and it was a good > idea to > show the equivalence with timeline in Flash! > By far clearer. > > > Best regards. > > Cedric M. (aka maddec) > > Interactive Creative > Adobe Flash/Flex/AIR Specialist > since 1998 > ---------------------------------------------------- > http://analogdesign.ch > http://analogdesign.ch/blog > visual & interactive communication > ---------------------------------------------------- > > > > > >> -----Message d'origine----- >> De : golist-bounces at goasap.org >> [mailto:golist-bounces at goasap.org] De la part de Moses Gunesch >> Envoy? : dimanche, 9. mars 2008 00:22 >> ? : Mailing list for the Go ActionScript Animation Platform >> Objet : [Golist] blog posts >> >> I posted about the new video tutorial and Go Playground so, >> cat's outa >> the bag folks! >> >> Please blog about these new articles, all of your blogs are actually >> the best way to spread the word about Go. Thanks! >> >> http://go.mosessupposes.com/ >> >> :) >> >> _______________________________________________ >> GoList mailing list >> GoList at goasap.org >> http://goasap.org/mailman/listinfo/golist_goasap.org >> > > > _______________________________________________ > 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/20080309/aaa22364/attachment.html From romuald at thoughtomatic.co.uk Tue Mar 18 03:40:47 2008 From: romuald at thoughtomatic.co.uk (Romuald Quantin) Date: Tue, 18 Mar 2008 10:40:47 -0000 Subject: [Golist] GO and LinearGo features Message-ID: Hi, First post, great work everyone and thanks to Moses. Just few questions if you've got some time. I've been an intensive user of Fuse in as2, I'm now using Tweener in as3 as it is quite simple to write and, as you know, time count on projects for clients :-) I hope I not bother you as I'm asking information because I know I won't have time to build my own parser (also because it won't be as great as some could do here). I saw the benchmarks and as I loved using Fuse I'd like to pass on GO for the next project depending on what I can do "quickly". I'd like to understand if I can start with GO now or wait that I get a kind of Fuse for as3 based on GO already built. I read the LinearGo is a complete tween class. Can someone tell me what I can do the following list with this LinearGo class? Or if I'll have to build my own one? What I'll need is: - Delay property Like be able to add a delay between tweens, or before, after, etc. basically I even used Fuse and delay only to sequence an animation, calling some function after a delay, etc. like I'd do with a setInterval? Maybe not the best pratice but so easy with Fuse. f.push({delay:1}); - Tween Basic properties such as x, y, scale, rotation and alpha - Tween colors - Tween filters (occasionally) - Tween brightness (occasionally) - Be able to add this kind or function in the middle of a tweening: f.push({scope:this, func: function() { // code } }); - Tweening different objects in the same time, playing with delay in a loop: for (var i:Number=0; i<__max; i++) { arr.push({target:__thumbnail["thumb"+i], alpha:0, time:.8, delay:i*.2}); } That's the base I'll need. Thanks for your time. Romuald -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080318/965ee995/attachment.html From newsl at analogdesign.ch Tue Mar 18 04:54:38 2008 From: newsl at analogdesign.ch (Cedric M. analogdesign) Date: Tue, 18 Mar 2008 12:54:38 +0100 Subject: [Golist] GO and LinearGo features In-Reply-To: Message-ID: Hi, I think Go Asap has everything you need and even more. To start with, you should check video tutorials: http://www.goasap.org/files/go-tutorial1.html http://www.goasap.org/files/go-tutorial2.html Moses proposed a simple parser (BlockParserMG and BlockTweenMG featured on video tutorials). You can find also a parser made by Donovan which is currently pretty advanced supports filters and colors matrix manipulations: http://blog.hydrotik.com/category/go/ (currently does not support groups, sequences and advance property). He also started one to tween Papervision3d properties, which I currently use and which is pretty quick to start with. In GO you have delays but also a system to manage sequences and group of tweens, moreover you can use the advance property to set up complex chaining of things as you would in a timeline approach (far better than using simple delays). GO also at its core scheduled to support in the future (currently in dev): physic engines management, Collada 3d animations, ...) I hope this will help you. Best regards. Cedric M. (aka maddec) Interactive Creative Adobe Flash/Flex/AIR Specialist Since 1998 ---------------------------------------------------- http://analogdesign.ch http://analogdesign.ch/blog visual & interactive communication ---------------------------------------------------- _____ De : golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] De la part de Romuald Quantin Envoy? : mardi, 18. mars 2008 11:41 ? : GoList at goasap.org Objet : [Golist] GO and LinearGo features Hi, First post, great work everyone and thanks to Moses. Just few questions if you?ve got some time. I?ve been an intensive user of Fuse in as2, I?m now using Tweener in as3 as it is quite simple to write and, as you know, time count on projects for clients :-) I hope I not bother you as I?m asking information because I know I won?t have time to build my own parser (also because it won?t be as great as some could do here). I saw the benchmarks and as I loved using Fuse I?d like to pass on GO for the next project depending on what I can do ?quickly?. I?d like to understand if I can start with GO now or wait that I get a kind of Fuse for as3 based on GO already built. I read the LinearGo is a complete tween class. Can someone tell me what I can do the following list with this LinearGo class? Or if I?ll have to build my own one? What I?ll need is: - Delay property Like be able to add a delay between tweens, or before, after, etc basically I even used Fuse and delay only to sequence an animation, calling some function after a delay, etc like I?d do with a setInterval? Maybe not the best pratice but so easy with Fuse. f.push({delay:1}); - Tween Basic properties such as x, y, scale, rotation and alpha - Tween colors - Tween filters (occasionally) - Tween brightness (occasionally) - Be able to add this kind or function in the middle of a tweening: f.push({scope:this, func: function() { // code } }); - Tweening different objects in the same time, playing with delay in a loop: for (var i:Number=0; i<__max; i++) { arr.push({target:__thumbnail["thumb"+i], alpha:0, time:.8, delay:i*.2}); } That?s the base I?ll need. Thanks for your time. Romuald -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080318/79de31e7/attachment.html From moses at goasap.org Tue Mar 18 07:59:40 2008 From: moses at goasap.org (Moses Gunesch) Date: Tue, 18 Mar 2008 10:59:40 -0400 Subject: [Golist] GO and LinearGo features In-Reply-To: References: Message-ID: <9F40F7D0-AD71-44BF-84F0-CC52CD0C8351@goasap.org> Go already supports delays and callbacks as long as you associate them with an actual animation. One feature you might want for a Sequencer would be support for a non-tweened delay / callback action. This could be done very easily in the parser by simply instantiating a plain LinearGo instance with a duration that matches the delay, so it would still have all the features of a tween (pause/resume control, callbacks, events etc.) but simply not update any real properties. You're right: No one has built a complete tween / sequencing API in Go yet. I keep trying to indicate to people that this would not be a huge undertaking, most of the hard stuff is already done for you. The video tutorial #2 proves that you can build a simple Fuse parser in around 5-10 minutes, and adding feature is simply not that tough. :) The final need in making a solid Fuse type utility would be special tween classes. Most simply you can just subclass LinearGo to create various tween types like say, a simple bitmap-filter handler. Your parser can search for specific properties (like say, "DropShadow_blurX") and then instantiate that type of tween... the rest of it works the same. Here's why these custom tween classes shouldn't be such a big deal: Most all of the complicated details have been done many times, and are freely available. For example Flash 9 ships with a package called motion that includes a Color class that has its own interpolate method that Robert Penner wrote specifically for tweening color ? someone could make use of this class. Alex Uhlmann's Animation Package, Tweener and many other package out there can help you flesh this stuff out ? just be sure to honor their license terms and of course, give credit where it is due. Later, your Sequencing system described above could be made a tad more sophisticated by writing a property-registration system. This would allow your users to only compile the special tween classes that they need per project ?? but that's fairly advanced stuff. Without getting that deep into things, anyone here could still build a really nice Sequence Parser with very little effort using the information above, and because your Go tools are your own thing you can simply add the stuff you want per project if you need to save the filesize. By the way, although everyone's systems differ a little, it's not like any of the developers in the Flash world invented computer animation! We are all just rehashing a tiny bit of the Wheel here. What I would like to get back to with Go is the ease with which the first Atari video game programmers were able to throw down any type of motion, be it linear or physics ? and those guys were using assembly!!! - m On Mar 18, 2008, at 6:40 AM, Romuald Quantin wrote: > Hi, > > First post, great work everyone and thanks to Moses. > > Just few questions if you?ve got some time. > > I?ve been an intensive user of Fuse in as2, I?m now using Tweener in > as3 as it is quite simple to write and, as you know, time count on > projects for clients J > > I hope I not bother you as I?m asking information because I know I > won?t have time to build my own parser (also because it won?t be as > great as some could do here). > > I saw the benchmarks and as I loved using Fuse I?d like to pass on > GO for the next project depending on what I can do ?quickly?. I?d > like to understand if I can start with GO now or wait that I get a > kind of Fuse for as3 based on GO already built. > > I read the LinearGo is a complete tween class. Can someone tell me > what I can do the following list with this LinearGo class? Or if > I?ll have to build my own one? > > What I?ll need is: > > - Delay property > > Like be able to add a delay between tweens, or before, after, etc? > basically I even used Fuse and delay only to sequence an animation, > calling some function after a delay, etc? like I?d do with a > setInterval? Maybe not the best pratice but so easy with Fuse. > > f.push({delay:1}); > > - Tween Basic properties such as x, y, scale, rotation and alpha > - Tween colors > - Tween filters (occasionally) > - Tween brightness (occasionally) > > - Be able to add this kind or function in the middle of a tweening: > f.push({scope:this, func: > function() { > // code > } > }); > > > - Tweening different objects in the same time, playing with delay in > a loop: > for (var i:Number=0; i<__max; i++) { > arr.push({target:__thumbnail["thumb"+i], alpha:0, time:. > 8, delay:i*.2}); > } > > That?s the base I?ll need. > > Thanks for your time. > > Romuald > > > > > _______________________________________________ > 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/20080318/0baf6a88/attachment.html From moses at goasap.org Fri Mar 21 23:43:36 2008 From: moses at goasap.org (Moses Gunesch) Date: Sat, 22 Mar 2008 02:43:36 -0400 Subject: [Golist] upcoming Go version 0.4.5... In-Reply-To: References: Message-ID: <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> Well the time had come to add a useFrames option to LinearGo... it was pretty much the last major tween feature to fall. :) Go is so weirdly flexible ? you can actually useFrames but also set a pulseInterval other than the player framerate.. very cool. But to make it easy for normal project use, I added a static method setupUseFramesMode() which turns on useFrames by default for all new tweens and sets the default pulse to ENTER_FRAME which is how you'd typically want it set up. I also added an advanced option to use a zero-based index for currentFrame, but the default behavior is that if you run a useFrames tween with a duration of 10, it will count from 1 to 10 just like the flash timeline. Not that I'm recommending useFrames by the way ? time-based updates are way better because they sync to the clock. Frame based updates are like the timeline, they lag with the processor. However, there are always certain moments when you need these things (like... if you're building collada tweens right? wink wink.) The only sticking point I ran into was good old skipTo()... always a chore. I'm not really happy with skipTo's regular time-based functionality anyway.. it does a lot but you can't jump around across multiple cycles which is a hassle (like, how to fast-forward to the end of all cycles?). So that's holding up this release.. yuck. In other news we have new PAUSE and RESUME event types in GoEvent. I've also added a CYCLE event which is fired when a multi-cycle tween ends a cycle and starts the next one, or when sequence with its repeatCount set ends then loops back. Hopefully will get this out soon! If you want to check it out early, email me off-list. Woohoo! :) Moses From moses at goasap.org Sat Mar 22 09:10:09 2008 From: moses at goasap.org (Moses Gunesch) Date: Sat, 22 Mar 2008 12:10:09 -0400 Subject: [Golist] upcoming Go version 0.4.5... In-Reply-To: <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> References: <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> Message-ID: <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> Need y'all's opinion on something... Unfortunately LinearGo's constructor inputs are going to need to change on the next release (see my previous email ? this release will add a useFrames option). Sorry, I know that is really inconvenient because it means that your tween classes will need to be fixed ? but this should be the last time this happens for LinearGo. A useFrames option will be added to the constructor. I also realized at this update that easing has an extraEasingParams setting, but easingOnCycle doesn't ? oops. So extraEasingParamsOnCycle is being added to LinearGo as well. Option A: This would be the most complete version of the constructor ? on the downside it's pretty ugly. public function LinearGo(delay : Number=NaN, duration : Number=NaN, easing : Function=null, extraEasingParams : Array=null, cycles : Number=NaN, easingOnCycle : Function=null, extraEasingParamsOnCycle: Array=null, // NEW useRelative : Boolean=false, useRounding : Boolean=false, useFrames : Boolean=false, // NEW pulseInterval : Number=NaN) Option B: Omit the 2 extraEasing inputs considering how infrequently they are actually used. This cleans up the constructor quite a bit. Subclasses could of course choose to add them back in if that is their preference, and of course any tween can first be instantiated then these special settings can be applied afterwards. (If you're unfamiliar, these params are settings for Back & Elastic easings like overshoot and amplitude, very few people know how to use them effectively so they are practically a moot point.) public function LinearGo(delay : Number=NaN, duration : Number=NaN, easing : Function=null, cycles : Number=NaN, easingOnCycle : Function=null, useRelative : Boolean=false, useRounding : Boolean=false, useFrames : Boolean=false, pulseInterval : Number=NaN) So what do you think... completeness or tidiness? -moses -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080322/fe57d057/attachment.html From michaelxxoa at gmail.com Sat Mar 22 13:49:56 2008 From: michaelxxoa at gmail.com (Michael Avila) Date: Sat, 22 Mar 2008 13:49:56 -0700 Subject: [Golist] upcoming Go version 0.4.5... In-Reply-To: <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> References: <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> Message-ID: <616a462a0803221349u43e4e591r225baf02abb80481@mail.gmail.com> My two cents worth. After the constructor runs the instance should be ready to use. If you can make the constructor more tidy, providing it still works properly, I would do so. Any parameters that don't relate to preparing the instance for use are a convenience. I don't like a lot of parameters, even the tidy version is a few too many for me. Since you sub-class LinearGo I don't think the amount of parameters are as much of an issue as they would be if you had to instantiate and use LinearGo within your applications code. On Sat, Mar 22, 2008 at 9:10 AM, Moses Gunesch wrote: > Need y'all's opinion on something... > > Unfortunately LinearGo's constructor inputs are going to need to change on > the next release (see my previous email ? this release will add a * > useFrames* option). Sorry, I know that is really inconvenient because it > means that your tween classes will need to be fixed ? but this should be the > last time this happens for LinearGo. > > A *useFrames* option will be added to the constructor. I also realized at > this update that *easing* has an *extraEasingParams* setting, but *easingOnCycle > *doesn't ? oops. So *extraEasingParamsOnCycle* is being added to LinearGo > as well. > > > Option A: This would be the most complete version of the constructor ? on > the downside it's pretty ugly. > > public function LinearGo(delay : Number=NaN, > duration : Number=NaN, > easing : Function=null, > extraEasingParams : Array=null, > cycles : Number=NaN, > easingOnCycle : Function=null, > extraEasingParamsOnCycle: Array=null, // NEW > useRelative : Boolean=false, > useRounding : Boolean=false, > useFrames : Boolean=false, // NEW > pulseInterval : Number=NaN) > > > Option B: Omit the 2 *extraEasing* inputs considering how infrequently > they are actually used. This cleans up the constructor quite a bit. > Subclasses could of course choose to add them back in if that is their > preference, and of course any tween can first be instantiated then these > special settings can be applied afterwards. > > (If you're unfamiliar, these params are settings for Back & Elastic > easings like overshoot and amplitude, very few people know how to use them > effectively so they are practically a moot point.) > > > public function LinearGo(delay : Number=NaN, > duration : Number=NaN, > easing : Function=null, > cycles : Number=NaN, > easingOnCycle : Function=null, > useRelative : Boolean=false, > useRounding : Boolean=false, > useFrames : Boolean=false, > pulseInterval : Number=NaN) > > So what do you think... completeness or tidiness? > > -moses > > > > > _______________________________________________ > 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/20080322/90d5b32a/attachment.html From michaelxxoa at gmail.com Sat Mar 22 13:49:56 2008 From: michaelxxoa at gmail.com (Michael Avila) Date: Sat, 22 Mar 2008 13:49:56 -0700 Subject: [Golist] upcoming Go version 0.4.5... In-Reply-To: <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> References: <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> Message-ID: <616a462a0803221349u43e4e591r225baf02abb80481@mail.gmail.com> My two cents worth. After the constructor runs the instance should be ready to use. If you can make the constructor more tidy, providing it still works properly, I would do so. Any parameters that don't relate to preparing the instance for use are a convenience. I don't like a lot of parameters, even the tidy version is a few too many for me. Since you sub-class LinearGo I don't think the amount of parameters are as much of an issue as they would be if you had to instantiate and use LinearGo within your applications code. On Sat, Mar 22, 2008 at 9:10 AM, Moses Gunesch wrote: > Need y'all's opinion on something... > > Unfortunately LinearGo's constructor inputs are going to need to change on > the next release (see my previous email ? this release will add a * > useFrames* option). Sorry, I know that is really inconvenient because it > means that your tween classes will need to be fixed ? but this should be the > last time this happens for LinearGo. > > A *useFrames* option will be added to the constructor. I also realized at > this update that *easing* has an *extraEasingParams* setting, but *easingOnCycle > *doesn't ? oops. So *extraEasingParamsOnCycle* is being added to LinearGo > as well. > > > Option A: This would be the most complete version of the constructor ? on > the downside it's pretty ugly. > > public function LinearGo(delay : Number=NaN, > duration : Number=NaN, > easing : Function=null, > extraEasingParams : Array=null, > cycles : Number=NaN, > easingOnCycle : Function=null, > extraEasingParamsOnCycle: Array=null, // NEW > useRelative : Boolean=false, > useRounding : Boolean=false, > useFrames : Boolean=false, // NEW > pulseInterval : Number=NaN) > > > Option B: Omit the 2 *extraEasing* inputs considering how infrequently > they are actually used. This cleans up the constructor quite a bit. > Subclasses could of course choose to add them back in if that is their > preference, and of course any tween can first be instantiated then these > special settings can be applied afterwards. > > (If you're unfamiliar, these params are settings for Back & Elastic > easings like overshoot and amplitude, very few people know how to use them > effectively so they are practically a moot point.) > > > public function LinearGo(delay : Number=NaN, > duration : Number=NaN, > easing : Function=null, > cycles : Number=NaN, > easingOnCycle : Function=null, > useRelative : Boolean=false, > useRounding : Boolean=false, > useFrames : Boolean=false, > pulseInterval : Number=NaN) > > So what do you think... completeness or tidiness? > > -moses > > > > > _______________________________________________ > 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/20080322/90d5b32a/attachment-0003.html From jan at renderstormstudios.com Sat Mar 22 23:01:50 2008 From: jan at renderstormstudios.com (Jan m. Danielsson) Date: Sun, 23 Mar 2008 07:01:50 +0100 Subject: [Golist] upcoming Go version 0.4.5... In-Reply-To: <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> Message-ID: Go (!) for the complete version! Like Michael Avila wrote - since you subclass it anyhow, the amount of parameters doesn?t really matter. But contrary to him, I like when there are a lot of parameters to fiddle around with. And, btw, thank you for an awsome tweening system. So far I?ve only used LinearGo, but I do love it. Keep up the good work! ///JmD From moses at goasap.org Sun Mar 23 11:18:05 2008 From: moses at goasap.org (Moses Gunesch) Date: Sun, 23 Mar 2008 14:18:05 -0400 Subject: [Golist] cycles design continued... In-Reply-To: References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> Message-ID: Here's one more little puzzle piece on this: I'm thinking that sometimes people might want to repeat tweens from the start, not cycle them back and forth. Since this gets pretty elaborate and clutters LinearGo's code quite a bit, it might be prudent to create some kind of cycle handling class that could be instantiated by the tween on start if cycles isn't 1..? This would solve a bunch of problems in that we could condense cycles, easeOnCycle and extraEasingParamsOnCycle and this looping option in one place. So maybe both LinearGo and Sequence could accept a parameter like repeater : Repeater, which would clean up both of those classes dramatically. Of course it's a tad more direct to just set mySequence.repeatCount = 2; than do something like mySequence.repeater.count = 2.... I'll look into this option though, I sorta like it because it encapsulates some of the messy iterator mechanics that are cluttering up my next build of LinearGo, both in update() and skipTo().... opinions? -m On Mar 23, 2008, at 2:01 AM, Jan m. Danielsson wrote: > Go (!) for the complete version! > Like Michael Avila wrote - since you subclass it anyhow, the amount of > parameters doesn?t really matter. But contrary to him, I like when > there > are a lot of parameters to fiddle around with. > > And, btw, thank you for an awsome tweening system. So far I?ve only > used > LinearGo, but I do love it. Keep up the good work! > > ///JmD > > _______________________________________________ > 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/20080323/9ea1933d/attachment.html From go at tweego.org Sun Mar 23 11:58:44 2008 From: go at tweego.org (Sebastian Weyrauch) Date: Sun, 23 Mar 2008 19:58:44 +0100 Subject: [Golist] cycles design continued... In-Reply-To: References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> Message-ID: <005601c88d17$eb262910$c1727b30$@org> Hi, think this is a good idea. A good and tidy structure is more important than a "easier" assignment. Besides my question in the last mail: I read you implemented a pause and resume event in 0.4.5. For the whole sequence and the single steps, right? Will there also be an update event for the whole sequence? (I know how to implemented, but a Go event would be nicer) sebastian Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im Auftrag von Moses Gunesch Gesendet: Sonntag, 23. M?rz 2008 19:18 An: Mailing list for the Go ActionScript Animation Platform Betreff: [Golist] cycles design continued... Here's one more little puzzle piece on this: I'm thinking that sometimes people might want to repeat tweens from the start, not cycle them back and forth. Since this gets pretty elaborate and clutters LinearGo's code quite a bit, it might be prudent to create some kind of cycle handling class that could be instantiated by the tween on start if cycles isn't 1..? This would solve a bunch of problems in that we could condense cycles, easeOnCycle and extraEasingParamsOnCycle and this looping option in one place. So maybe both LinearGo and Sequence could accept a parameter like repeater : Repeater, which would clean up both of those classes dramatically. Of course it's a tad more direct to just set mySequence.repeatCount = 2; than do something like mySequence.repeater.count = 2.... I'll look into this option though, I sorta like it because it encapsulates some of the messy iterator mechanics that are cluttering up my next build of LinearGo, both in update() and skipTo().... opinions? -m On Mar 23, 2008, at 2:01 AM, Jan m. Danielsson wrote: Go (!) for the complete version! Like Michael Avila wrote - since you subclass it anyhow, the amount of parameters doesn?t really matter. But contrary to him, I like when there are a lot of parameters to fiddle around with. And, btw, thank you for an awsome tweening system. So far I?ve only used LinearGo, but I do love it. Keep up the good work! ///JmD _______________________________________________ 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/20080323/071851be/attachment.html From moses at goasap.org Sun Mar 23 14:59:56 2008 From: moses at goasap.org (Moses Gunesch) Date: Sun, 23 Mar 2008 17:59:56 -0400 Subject: [Golist] update event for sequence / playablegroup? In-Reply-To: <005601c88d17$eb262910$c1727b30$@org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <005601c88d17$eb262910$c1727b30$@org> Message-ID: <00049850-6D1B-42B5-80A9-E32B6910B657@goasap.org> Thanks for the feedback on the cycles design Sebastian... > Will there also be an update event for the whole sequence? You mean a pulse-based update event? I don't know, and I'm not really sure it's feasible to be honest. :( Here are the problems involved: 1. Typically you don't want a group's UPDATE to fire until all children have updated first. Say you're running a complicated sequence with lots of parallel groups of tweens ? whatever your update listener is doing, you normally don't want to end up with a case where only some of the child tweens have updated when your event fires or your code can't check each child's position accurately. 2. Syncing is really complex. Any IUpdatable can specify its own pulseInterval so it's complicated... what if one tween has a pulse of 33 and another has a pulse of 100? By default the group wouldn't fire update until the 100 pulse completed ? so now the tracking has to not just count child updates, it has to track exactly which children have updated too. 3. SequenceCA adds more complexity. SequenceCA tracks "trailing tweens" in a private group, which would have to be factored into this system. So over all, an accurate UPDATE event would require really quite a bit of extra code in the core classes. 4. Events are slow. LinearGo gets around this by not firing events unless there are listeners for them. Update events are worst, they truly do affect performance. I'd like to avoid a situation where every child tween has update events subscribed in groups. Callbacks are slightly faster but it's still an issue. - Here's an alternative: We could subclass addEventListener() in PlayableGroup and SequenceBase and instantiate a very simple private IUpdatable instance when UPDATE is subscribed. This instance could accept an update callback and be used to fire the UPDATE event from the group or sequence. The docs would have to mention though, that this UPDATE would not necessarily be synced with child items, and may fire before all items have updated. - Thoughts? Sorry this is such a pain but, as you can see there are reasons why it's omitted. :) -m On Mar 23, 2008, at 2:58 PM, Sebastian Weyrauch wrote: > Hi, > think this is a good idea. A good and tidy structure is more > important than a "easier" assignment. > > Besides my question in the last mail: > I read you implemented a pause and resume event in 0.4.5. For the > whole sequence and the single steps, right? > Will there also be an update event for the whole sequence? (I know > how to implemented, but a Go event would be nicer) > > sebastian > > > > Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im > Auftrag von Moses Gunesch > Gesendet: Sonntag, 23. M?rz 2008 19:18 > An: Mailing list for the Go ActionScript Animation Platform > Betreff: [Golist] cycles design continued... > > Here's one more little puzzle piece on this: > > I'm thinking that sometimes people might want to repeat tweens from > the start, not cycle them back and forth. > > Since this gets pretty elaborate and clutters LinearGo's code quite > a bit, it might be prudent to create some kind of cycle handling > class that could be instantiated by the tween on start if cycles > isn't 1..? > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080323/27b93da0/attachment.html From go at tweego.org Mon Mar 24 00:02:35 2008 From: go at tweego.org (Sebastian Weyrauch) Date: Mon, 24 Mar 2008 08:02:35 +0100 Subject: [Golist] update event for sequence / playablegroup? In-Reply-To: <00049850-6D1B-42B5-80A9-E32B6910B657@goasap.org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <005601c88d17$eb262910$c1727b30$@org> <00049850-6D1B-42B5-80A9-E32B6910B657@goasap.org> Message-ID: <006b01c88d7d$0b6388c0$222a9a40$@org> Ok, I understand the problems. I'm not sure what's better: The alternative or leaving this away. If it is not to complicate, you can implement this, else: let it be :) Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im Auftrag von Moses Gunesch Gesendet: Sonntag, 23. M?rz 2008 23:00 An: Mailing list for the Go ActionScript Animation Platform Betreff: [Golist] update event for sequence / playablegroup? Thanks for the feedback on the cycles design Sebastian... Will there also be an update event for the whole sequence? You mean a pulse-based update event? I don't know, and I'm not really sure it's feasible to be honest. :( Here are the problems involved: 1. Typically you don't want a group's UPDATE to fire until all children have updated first. Say you're running a complicated sequence with lots of parallel groups of tweens ? whatever your update listener is doing, you normally don't want to end up with a case where only some of the child tweens have updated when your event fires or your code can't check each child's position accurately. 2. Syncing is really complex. Any IUpdatable can specify its own pulseInterval so it's complicated... what if one tween has a pulse of 33 and another has a pulse of 100? By default the group wouldn't fire update until the 100 pulse completed ? so now the tracking has to not just count child updates, it has to track exactly which children have updated too. 3. SequenceCA adds more complexity. SequenceCA tracks "trailing tweens" in a private group, which would have to be factored into this system. So over all, an accurate UPDATE event would require really quite a bit of extra code in the core classes. 4. Events are slow. LinearGo gets around this by not firing events unless there are listeners for them. Update events are worst, they truly do affect performance. I'd like to avoid a situation where every child tween has update events subscribed in groups. Callbacks are slightly faster but it's still an issue. - Here's an alternative: We could subclass addEventListener() in PlayableGroup and SequenceBase and instantiate a very simple private IUpdatable instance when UPDATE is subscribed. This instance could accept an update callback and be used to fire the UPDATE event from the group or sequence. The docs would have to mention though, that this UPDATE would not necessarily be synced with child items, and may fire before all items have updated. - Thoughts? Sorry this is such a pain but, as you can see there are reasons why it's omitted. :) -m On Mar 23, 2008, at 2:58 PM, Sebastian Weyrauch wrote: Hi, think this is a good idea. A good and tidy structure is more important than a "easier" assignment. Besides my question in the last mail: I read you implemented a pause and resume event in 0.4.5. For the whole sequence and the single steps, right? Will there also be an update event for the whole sequence? (I know how to implemented, but a Go event would be nicer) sebastian Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im Auftrag von Moses Gunesch Gesendet: Sonntag, 23. M?rz 2008 19:18 An: Mailing list for the Go ActionScript Animation Platform Betreff: [Golist] cycles design continued... Here's one more little puzzle piece on this: I'm thinking that sometimes people might want to repeat tweens from the start, not cycle them back and forth. Since this gets pretty elaborate and clutters LinearGo's code quite a bit, it might be prudent to create some kind of cycle handling class that could be instantiated by the tween on start if cycles isn't 1..? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080324/8a1b9524/attachment-0001.html From go at tweego.org Mon Mar 24 00:28:11 2008 From: go at tweego.org (Sebastian Weyrauch) Date: Mon, 24 Mar 2008 08:28:11 +0100 Subject: [Golist] update event for sequence / playablegroup? In-Reply-To: <006b01c88d7d$0b6388c0$222a9a40$@org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <005601c88d17$eb262910$c1727b30$@org> <00049850-6D1B-42B5-80A9-E32B6910B657@goasap.org> <006b01c88d7d$0b6388c0$222a9a40$@org> Message-ID: <007601c88d80$9e4d3750$dae7a5f0$@org> Btw: What is with an "Advance" event for the items? I know this is probably a problem, too. At the moment I had to listen to the sequence and delegate this to the lastStep items. Right? cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080324/389e3a3b/attachment.html From moses at goasap.org Mon Mar 24 08:42:33 2008 From: moses at goasap.org (Moses Gunesch) Date: Mon, 24 Mar 2008 11:42:33 -0400 Subject: [Golist] update event for sequence / playablegroup? In-Reply-To: <007601c88d80$9e4d3750$dae7a5f0$@org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <005601c88d17$eb262910$c1727b30$@org> <00049850-6D1B-42B5-80A9-E32B6910B657@goasap.org> <006b01c88d7d$0b6388c0$222a9a40$@org> <007601c88d80$9e4d3750$dae7a5f0$@org> Message-ID: <1D17C3D2-5612-46F3-96D4-49761A224D5B@goasap.org> Can you rephrase the question more clearly? I don't really understand what you're asking... - m On Mar 24, 2008, at 3:28 AM, Sebastian Weyrauch wrote: > Btw: What is with an "Advance" event for the items? I know this is > probably a problem, too. > > At the moment I had to listen to the sequence and delegate this to > the lastStep items. Right? > > cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080324/f5d4b972/attachment.html From go at tweego.org Mon Mar 24 09:11:19 2008 From: go at tweego.org (Sebastian Weyrauch) Date: Mon, 24 Mar 2008 17:11:19 +0100 Subject: [Golist] update event for sequence / playablegroup? In-Reply-To: <1D17C3D2-5612-46F3-96D4-49761A224D5B@goasap.org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <005601c88d17$eb262910$c1727b30$@org> <00049850-6D1B-42B5-80A9-E32B6910B657@goasap.org> <006b01c88d7d$0b6388c0$222a9a40$@org> <007601c88d80$9e4d3750$dae7a5f0$@org> <1D17C3D2-5612-46F3-96D4-49761A224D5B@goasap.org> Message-ID: <000601c88dc9$b33b25c0$19b17140$@org> Hi, LinearGo dispatches the events START, UPDATE, STOP, COMPLETE (in Go 0.4.5 PAUSE & RESUME, too, right?), but there is no ADVANCE event for LinearGo items (e.g. if not complete and skipped to the next). I'm not sure if this is necessary. But I wanted to implement a functionality like {onAdvance: func} in Fuse. Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im Auftrag von Moses Gunesch Gesendet: Montag, 24. M?rz 2008 16:43 An: Mailing list for the Go ActionScript Animation Platform Betreff: Re: [Golist] update event for sequence / playablegroup? Can you rephrase the question more clearly? I don't really understand what you're asking... - m On Mar 24, 2008, at 3:28 AM, Sebastian Weyrauch wrote: Btw: What is with an "Advance" event for the items? I know this is probably a problem, too. At the moment I had to listen to the sequence and delegate this to the lastStep items. Right? cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080324/598be29a/attachment.html From moses at goasap.org Mon Mar 24 10:11:13 2008 From: moses at goasap.org (Moses Gunesch) Date: Mon, 24 Mar 2008 13:11:13 -0400 Subject: [Golist] update event for sequence / playablegroup? In-Reply-To: <000601c88dc9$b33b25c0$19b17140$@org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <005601c88d17$eb262910$c1727b30$@org> <00049850-6D1B-42B5-80A9-E32B6910B657@goasap.org> <006b01c88d7d$0b6388c0$222a9a40$@org> <007601c88d80$9e4d3750$dae7a5f0$@org> <1D17C3D2-5612-46F3-96D4-49761A224D5B@goasap.org> <000601c88dc9$b33b25c0$19b17140$@org> Message-ID: <97B380EF-97DE-4471-9B8F-37D806A3B67A@goasap.org> Well that's because a single tween, on its own cannot "advance"... advance means "to the next step" which means... sequencing. :) That's why that event is in the sequencestep level. Any step of a sequence can advance and does fire that event if its tweens are stopped. (Remember that you can listen on tweens for STOP (stopped before finished) vs. COMPLETE.... maybe that helps?) There's no real need for {onAdvance:callback} because that callback would be fired as the next step started. Just put a start callback in the next action. I don't think fuse even had that parameter. Are you maybe thinking of fuse's feature {advance:1} ? If so that's there, in SequenceCA. On Mar 24, 2008, at 12:11 PM, Sebastian Weyrauch wrote: > Hi, > > LinearGo dispatches the events START, UPDATE, STOP, COMPLETE (in Go > 0.4.5 PAUSE & RESUME, too, right?), but there is no ADVANCE event > for LinearGo items (e.g. if not complete and skipped to the next). > > I'm not sure if this is necessary. But I wanted to implement a > functionality like {onAdvance: func} in Fuse. > > > Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im > Auftrag von Moses Gunesch > Gesendet: Montag, 24. M?rz 2008 16:43 > An: Mailing list for the Go ActionScript Animation Platform > Betreff: Re: [Golist] update event for sequence / playablegroup? > > Can you rephrase the question more clearly? > I don't really understand what you're asking... > > - m > > On Mar 24, 2008, at 3:28 AM, Sebastian Weyrauch wrote: > > > Btw: What is with an "Advance" event for the items? I know this is > probably a problem, too. > > At the moment I had to listen to the sequence and delegate this to > the lastStep items. Right? > > cheers > _______________________________________________ > 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/20080324/94aece9f/attachment-0001.html From go at tweego.org Mon Mar 24 10:26:41 2008 From: go at tweego.org (Sebastian Weyrauch) Date: Mon, 24 Mar 2008 18:26:41 +0100 Subject: [Golist] update event for sequence / playablegroup? In-Reply-To: <97B380EF-97DE-4471-9B8F-37D806A3B67A@goasap.org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <005601c88d17$eb262910$c1727b30$@org> <00049850-6D1B-42B5-80A9-E32B6910B657@goasap.org> <006b01c88d7d$0b6388c0$222a9a40$@org> <007601c88d80$9e4d3750$dae7a5f0$@org> <1D17C3D2-5612-46F3-96D4-49761A224D5B@goasap.org> <000601c88dc9$b33b25c0$19b17140$@org> <97B380EF-97DE-4471-9B8F-37D806A3B67A@goasap.org> Message-ID: <002001c88dd4$3aa0a990$afe1fcb0$@org> Well, I have thought "_fuseEvents" in FuseKitCommon are the events for the single actions. But they seem to be the global event types. -> Canceled from the list :) Thanks (At the moment I improve the special properties, then Tweego is ready for the first public version. Maybe Wednesday :)) Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im Auftrag von Moses Gunesch Gesendet: Montag, 24. M?rz 2008 18:11 An: Mailing list for the Go ActionScript Animation Platform Betreff: Re: [Golist] update event for sequence / playablegroup? Well that's because a single tween, on its own cannot "advance"... advance means "to the next step" which means... sequencing. :) That's why that event is in the sequencestep level. Any step of a sequence can advance and does fire that event if its tweens are stopped. (Remember that you can listen on tweens for STOP (stopped before finished) vs. COMPLETE.... maybe that helps?) There's no real need for {onAdvance:callback} because that callback would be fired as the next step started. Just put a start callback in the next action. I don't think fuse even had that parameter. Are you maybe thinking of fuse's feature {advance:1} ? If so that's there, in SequenceCA. On Mar 24, 2008, at 12:11 PM, Sebastian Weyrauch wrote: Hi, LinearGo dispatches the events START, UPDATE, STOP, COMPLETE (in Go 0.4.5 PAUSE & RESUME, too, right?), but there is no ADVANCE event for LinearGo items (e.g. if not complete and skipped to the next). I'm not sure if this is necessary. But I wanted to implement a functionality like {onAdvance: func} in Fuse. Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im Auftrag von Moses Gunesch Gesendet: Montag, 24. M?rz 2008 16:43 An: Mailing list for the Go ActionScript Animation Platform Betreff: Re: [Golist] update event for sequence / playablegroup? Can you rephrase the question more clearly? I don't really understand what you're asking... - m On Mar 24, 2008, at 3:28 AM, Sebastian Weyrauch wrote: Btw: What is with an "Advance" event for the items? I know this is probably a problem, too. At the moment I had to listen to the sequence and delegate this to the lastStep items. Right? cheers _______________________________________________ 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/20080324/21f5099a/attachment.html From moses at goasap.org Mon Mar 24 13:08:11 2008 From: moses at goasap.org (Moses Gunesch) Date: Mon, 24 Mar 2008 16:08:11 -0400 Subject: [Golist] cycles design continued... Message-ID: <96479FE3-1B1A-4D66-AEA3-4521A8494DF4@goasap.org> Okay here's what I've cooked up: A couple of simple iterator utils that sit in the managers package, Repeater & LinearGoRepeater. This has allowed me to condense the cycles feature of LinearGo quite a bit... the class no longer contains properties cycles, easeOnCycle or the two properties that were still needed, extra easing params for easeOnCycle and an option to play the tween multiple times forwards instead of cycling back-and-forth. All of that has been neatly encapsulated so you can now do, mytween.repeater.cycles = 2; mytween.repeater.reverseOnCycle = false; // play fwd both times Let me know what you think of this implementation, the release including useFrames is pretty much ready now. -moses Class Repeater Constant Defined by INFINITE : uint = 0 [static] Makes code more human-readable, like new Repeater(Repeater.INFINITE); Repeater Property Defined by currentCycle : uint [read-only] Current cycle starting at 0, which will continue to increase up to cycles or indefinitely if cycles is set to Repeater.INFINITE (zero). Repeater cycles : uint Number of times the Repeater will iterate, which can be set to zero or Repeater.INFINITE for indefinite repeating. Repeater done : Boolean [read-only] True if cycles is not infinite and currentCycle has reached cycles. Repeater Class LinearGoRepeater direction : int [read-only] Current play direction depending on reverseOnCycle and currentCycle. LinearGoRepeater easingOnCycle : Function Storage for optional secondary easing to use on reverse cycles. LinearGoRepeater extraEasingParams : Array Additional parameters to use with easingOnCycle if the function accepts more than four. LinearGoRepeater reverseOnCycle : Boolean Whether tween direction should reverse every other cycle. LinearGoRepeater Class LinearGo LinearGo(delay:Number, duration:Number, easing:Function = null, extraEasingParams:Array = null, repeater:LinearGoRepeater = null, // new! useRelative:Boolean = false, useRounding:Boolean = false, useFrames:Boolean = false, // new! pulseInterval:Number) repeater : LinearGoRepeater [read-only] A LinearGoRepeater instance that defines options for repeated or back-and-forth cycling animation. Class SequenceBase repeater : Repeater [read-only] The sequence's Repeater instance, which may be used to make the sequence loop and play more than one time. SequenceBase (replaces repeatCount & currentCount properties for Sequence & SequenceCA) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080324/0d6eb2e3/attachment.html From moses at goasap.org Mon Mar 24 15:48:36 2008 From: moses at goasap.org (Moses Gunesch) Date: Mon, 24 Mar 2008 18:48:36 -0400 Subject: [Golist] upcoming Go version 0.4.5... In-Reply-To: References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> Message-ID: <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> So .... should I post this build? Thing is, it will break / force you to change your subclasses. Should probably make a branch huh. ... From moses at goasap.org Mon Mar 24 20:50:35 2008 From: moses at goasap.org (Moses Gunesch) Date: Mon, 24 Mar 2008 23:50:35 -0400 Subject: [Golist] Go version 0.4.5 :: useFrames & Repeater In-Reply-To: <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> Message-ID: go 0.4.5 currently this is in a branch only, here: http://goasap.googlecode.com/svn/ branches/ goasap045/ Includes docs. Look up managers.Repeater & LinearGoRepeater, and check LinearGo... the constructor has changed and some settings have been moved to the new repeater property, plus there is now useFrames functionality. SequenceBase / Sequence / SequenceCA are also affected, they also have a repeater property. Really would like everyone's feedback on this build. I'd like to get community support before merging this build to trunk since the constructor has changed and it will mean changing your subclasses just a little bit. So really take a look at it, use it, and let me know if this is the way to go. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080324/f61f3bc0/attachment-0001.html From newsl at analogdesign.ch Tue Mar 25 00:55:33 2008 From: newsl at analogdesign.ch (Cedric M. analogdesign) Date: Tue, 25 Mar 2008 08:55:33 +0100 Subject: [Golist] cycles design continued... In-Reply-To: <96479FE3-1B1A-4D66-AEA3-4521A8494DF4@goasap.org> Message-ID: Hi, Excellent, I haven't tested it yet but it sounds clean and expandable: from the top of my head: easingOnCycle may be a list of easings to play randomly for example if easingOnCycleBehaviour is equal to Repeater .RANDOM: for example for a shining star, you may have five type of shining Tweens giving it a more natural life, than using the same easing back and forth. Every time a cycle is finished it jumps to another Tween. This option may be interesting for secondary animated elements to add depth to the main animation. Of course it may bring confusion, but it is and advanced feature... So would it be acceptable? By the way it is something that I've used in some past Fuse-projects with a home made implementation, so it sounds that it is something usable, at least to me ;), it would be very useful to put it into Goasap ;) Let me know what do you think about it... Best regards. Cedric M. (aka maddec) Interactive Creative Adobe Flash/Flex/AIR Specialist Since 1998 ---------------------------------------------------- http://analogdesign.ch http://analogdesign.ch/blog visual & interactive communication ---------------------------------------------------- _____ De : golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] De la part de Moses Gunesch Envoy? : lundi, 24. mars 2008 21:08 ? : Mailing list for the Go ActionScript Animation Platform Objet : Re: [Golist] cycles design continued... Okay here's what I've cooked up: A couple of simple iterator utils that sit in the managers package, Repeater & LinearGoRepeater. This has allowed me to condense the cycles feature of LinearGo quite a bit... the class no longer contains properties cycles, easeOnCycle or the two properties that were still needed, extra easing params for easeOnCycle and an option to play the tween multiple times forwards instead of cycling back-and-forth. All of that has been neatly encapsulated so you can now do, mytween.repeater.cycles = 2; mytween.repeater.reverseOnCycle = false; // play fwd both times Let me know what you think of this implementation, the release including useFrames is pretty much ready now. -moses Class Repeater Constant Defined by INFINITE : uint = 0 [static] Makes code more human-readable, like new Repeater(Repeater.INFINITE); Repeater Property Defined by currentCycle : uint [read-only] Current cycle starting at 0, which will continue to increase up to cycles or indefinitely if cycles is set to Repeater.INFINITE (zero). Repeater cycles : uint Number of times the Repeater will iterate, which can be set to zero or Repeater.INFINITE for indefinite repeating. Repeater done : Boolean [read-only] True if cycles is not infinite and currentCycle has reached cycles. Repeater Class LinearGoRepeater direction : int [read-only] Current play direction depending on reverseOnCycle and currentCycle. LinearGoRepeater easingOnCycle : Function Storage for optional secondary easing to use on reverse cycles. LinearGoRepeater extraEasingParams : Array Additional parameters to use with easingOnCycle if the function accepts more than four. LinearGoRepeater reverseOnCycle : Boolean Whether tween direction should reverse every other cycle. LinearGoRepeater Class LinearGo LinearGo (delay:Number, duration:Number, easing:Function = null, extraEasingParams:Array = null, repeater: LinearGoRepeater = null, // new! useRelative:Boolean = false, useRounding:Boolean = false, useFrames:Boolean = false, // new! pulseInterval:Number) repeater : LinearGoRepeater [read-only] A LinearGoRepeater instance that defines options for repeated or back-and-forth cycling animation. Class SequenceBase repeater : Repeater [read-only] The sequence's Repeater instance, which may be used to make the sequence loop and play more than one time. SequenceBase (replaces repeatCount & currentCount properties for Sequence & SequenceCA) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080325/e773c263/attachment.html From go at tweego.org Tue Mar 25 01:06:22 2008 From: go at tweego.org (Sebastian Weyrauch) Date: Tue, 25 Mar 2008 09:06:22 +0100 Subject: [Golist] Error in Go version 0.4.5 In-Reply-To: References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> Message-ID: <005c01c88e4f$1dee5ba0$59cb12e0$@org> Hi Moses, i get an error in the current version, if no easing function is defined. TypeError: Error #1009: Cannot access a property or method of a null object reference. at org.goasap.items::LinearGo/update() at org.goasap::GoEngine$/update() at flash.utils::Timer/_timerDispatch() at flash.utils::Timer/tick() The error is released by this line: _position = _currentEasing.apply(null, _easeParams); _currentEasing is undefined regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080325/96f16420/attachment.html From moses at goasap.org Thu Mar 27 23:09:59 2008 From: moses at goasap.org (Moses Gunesch) Date: Fri, 28 Mar 2008 02:09:59 -0400 Subject: [Golist] Go version 0.4.6 In-Reply-To: <005c01c88e4f$1dee5ba0$59cb12e0$@org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> <005c01c88e4f$1dee5ba0$59cb12e0$@org> Message-ID: <41D454DC-8AF0-46F3-AA07-EFC08DFFA4D5@goasap.org> (Sebastian, thanks very much for nabbing that easing bug!) Folks, this build again is in the /branches/ folder of the goasap repository and not uploaded as a zip yet. It is a branch because the constructor of LinearGo changed, and a new repeater property has been added now to LinearGo, SequenceBase and PlayableGroup -- meaning that you now have very tight control over looping all of those things, and with LinearGo tweens you can now choose whether to cycle back-and-forth or loop forwards. LinearGo also has useFrames support as of the previous release! PLEASE drop a comment here when you've used this build, I certainly don't want to just merge something that alters the LinearGo constructor and shaft everyone's subclasses. Thanks! ____________________________________________ Version 0.4.6. - Updates how easing and other defaults are treated by LinearGo. - Adds a repeater to PlayableGroup, which now also dispatches the full event set. A very minor change was also made to its addChild method, it now dispatches a START event when using the adoptChildState option. - Docs improved. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080328/7bceb1e8/attachment.html From go at tweego.org Sun Mar 30 01:26:16 2008 From: go at tweego.org (Sebastian Weyrauch) Date: Sun, 30 Mar 2008 10:26:16 +0200 Subject: [Golist] Go version 0.4.6 In-Reply-To: <41D454DC-8AF0-46F3-AA07-EFC08DFFA4D5@goasap.org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> <005c01c88e4f$1dee5ba0$59cb12e0$@org> <41D454DC-8AF0-46F3-AA07-EFC08DFFA4D5@goasap.org> Message-ID: <007201c8923f$b98e12f0$2caa38d0$@org> Seems to work fine, thanks. Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im Auftrag von Moses Gunesch Gesendet: Freitag, 28. M?rz 2008 07:10 An: Mailing list for the Go ActionScript Animation Platform Betreff: [Golist] Go version 0.4.6 PLEASE drop a comment here when you've used this build, I certainly don't want to just merge something that alters the LinearGo constructor and shaft everyone's subclasses. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080330/3f637d82/attachment.html From moses at goasap.org Sun Mar 30 09:49:00 2008 From: moses at goasap.org (Moses Gunesch) Date: Sun, 30 Mar 2008 12:49:00 -0400 Subject: [Golist] Go version 0.4.6 In-Reply-To: <007201c8923f$b98e12f0$2caa38d0$@org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> <005c01c88e4f$1dee5ba0$59cb12e0$@org> <41D454DC-8AF0-46F3-AA07-EFC08DFFA4D5@goasap.org> <007201c8923f$b98e12f0$2caa38d0$@org> Message-ID: <99AE8BDB-6E0D-47CC-B1DA-F5A476E2E39F@goasap.org> Cool thanks Sebastian. Anyone else out there have any LinearGo classes yet, that they can try with the new version? You'll need to adjust the constructor's super() call, and also unlike in earlier versions calling the constructor is mandatory because it now verifies default values and sets up the repeater. So yes, let me know if this works or not. -m On Mar 30, 2008, at 4:26 AM, Sebastian Weyrauch wrote: > Seems to work fine, thanks. > > Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] Im > Auftrag von Moses Gunesch > Gesendet: Freitag, 28. M?rz 2008 07:10 > An: Mailing list for the Go ActionScript Animation Platform > Betreff: [Golist] Go version 0.4.6 > > PLEASE drop a comment here when you've used this build, I certainly > don't want to just merge something that alters the LinearGo > constructor and shaft everyone's subclasses. Thanks! > > > _______________________________________________ > 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/20080330/ad8a4c90/attachment.html From moses at goasap.org Sun Mar 30 09:54:37 2008 From: moses at goasap.org (Moses Gunesch) Date: Sun, 30 Mar 2008 12:54:37 -0400 Subject: [Golist] Go to be featured in OS Flash book! Message-ID: <183DCFE8-98AF-4762-8C6C-BD5A657F3068@goasap.org> An upcoming book on open source Flash, going to press in just a couple of months, will feature a chapter on Fuse & Go. From richhauck at mandalatv.net Sun Mar 30 10:11:22 2008 From: richhauck at mandalatv.net (Rich Hauck) Date: Sun, 30 Mar 2008 13:11:22 -0400 Subject: [Golist] Go to be featured in OS Flash book! In-Reply-To: <183DCFE8-98AF-4762-8C6C-BD5A657F3068@goasap.org> Message-ID: Cool. I was impressed to see GoASAP linked in Learning Actionscript 3.0... > From: Moses Gunesch > Reply-To: Mailing list for the Go ActionScript Animation Platform > > Date: Sun, 30 Mar 2008 12:54:37 -0400 > To: Mailing list for the Go ActionScript Animation Platform > > Subject: [Golist] Go to be featured in OS Flash book! > > An upcoming book on open source Flash, going to press in just a couple > of months, will feature a chapter on Fuse & Go. > > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org From moses at goasap.org Sun Mar 30 12:28:08 2008 From: moses at goasap.org (Moses Gunesch) Date: Sun, 30 Mar 2008 15:28:08 -0400 Subject: [Golist] Go to be featured in OS Flash book! In-Reply-To: References: Message-ID: <93418682-09D8-42AF-9B9A-27779CFCB5EF@goasap.org> Oh did Mr. Shupe get that in there? Fantastic, I didn't know for sure!! Thanks! :) moses (PS Rich, I wonder why your email showed headers... this is bad because it exposes emails to spammers via the archives.) On Mar 30, 2008, at 1:11 PM, Rich Hauck wrote: > Cool. I was impressed to see GoASAP linked in Learning Actionscript > 3.0... > > >> From: Moses Gunesch >> >> An upcoming book on open source Flash, going to press in just a >> couple >> of months, will feature a chapter on Fuse & Go. >> From moses at goasap.org Sun Mar 30 12:54:32 2008 From: moses at goasap.org (Moses Gunesch) Date: Sun, 30 Mar 2008 15:54:32 -0400 Subject: [Golist] FlashBelt date change / Go Workshop Message-ID: <390882F6-E991-4165-94CB-21C5BFAF26CB@goasap.org> FlashBelt is going to shift their conference dates back two days due to a hotel booking issue. I will be speaking at FlashBelt on June 10th or 11th. We have consequently canceled our tie-in to the Go Animation workshop at Bricka Bracka, although the workshop is still on assuming any of you decided to sign up! :) For those who want to get some real learning in, this workshop will be invaluable. The problem with a 40-minute conference session is that by the time you've brought the whole audience up to speed on what you're presenting, you have little time to get into much more than a few examples. I took John Grden's PV3D workshop and felt it was worth every penny. Haven't really decided whether I should focus primarily on Go or be more general and cover all sorts of Animation tools for AS2 & AS3. But I'm certainly open to what you would want so feel free to make suggestions! Moses From robert at bennybula.com Mon Mar 31 07:43:11 2008 From: robert at bennybula.com (=?ISO-8859-1?Q?Robert_Sk=F6ld?=) Date: Mon, 31 Mar 2008 16:43:11 +0200 Subject: [Golist] Go version 0.4.6 In-Reply-To: <99AE8BDB-6E0D-47CC-B1DA-F5A476E2E39F@goasap.org> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> <005c01c88e4f$1dee5ba0$59cb12e0$@org> <41D454DC-8AF0-46F3-AA07-EFC08DFFA4D5@goasap.org> <007201c8923f$b98e12f0$2caa38d0$@org> <99AE8BDB-6E0D-47CC-B1DA-F5A476E2E39F@goasap.org> Message-ID: <857090D3-E16C-49DF-BB5C-E1DC0CAC608C@bennybula.com> Hey Moses, I've just tried to move to the new version, got revision 31 from the branch, and I'm getting this error: TypeError: Error #1009: Cannot access a property or method of a null object reference. at org.goasap.items::LinearGo/stop()[/Users/slaskis/Projects/ PublicClass/Saab/source/org/goasap/items/LinearGo.as:577] at org.goasap.utils::PlayableGroup/stop()[/Users/slaskis/Projects/ PublicClass/Saab/source/org/goasap/utils/PlayableGroup.as:309] at org.goasap.utils::SequenceStepCA/stop()[/Users/slaskis/Projects/ PublicClass/Saab/source/org/goasap/utils/SequenceStepCA.as:166] at org.goasap.utils::SequenceBase/stop()[/Users/slaskis/Projects/ PublicClass/Saab/source/org/goasap/utils/SequenceBase.as:228] at org.goasap.utils::SequenceCA/stop()[/Users/slaskis/Projects/ PublicClass/Saab/source/org/goasap/utils/SequenceCA.as:209] at org.goasap.utils::SequenceBase/start()[/Users/slaskis/Projects/ PublicClass/Saab/source/org/goasap/utils/SequenceBase.as:210] at org.goasap.utils::SequenceCA/start()[/Users/slaskis/Projects/ PublicClass/Saab/source/org/goasap/utils/SequenceCA.as:200] ... (and more, but it's not relevant i think) It seems like the _easeParams is set to null (i put a trace there in the LinearGo.stop() method). Is there something i need to do? I'm running super() in the constructor of the class that extends LinearGo, but would i have to run some other method as well? Cheers! /bob On Mar 30, 2008, at 18:49, Moses Gunesch wrote: > Cool thanks Sebastian. > > Anyone else out there have any LinearGo classes yet, that they can > try with the new version? > > You'll need to adjust the constructor's super() call, and also > unlike in earlier versions calling the constructor is mandatory > because it now verifies default values and sets up the repeater. > > So yes, let me know if this works or not. > > -m > > > > > On Mar 30, 2008, at 4:26 AM, Sebastian Weyrauch wrote: > >> Seems to work fine, thanks. >> >> Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] >> Im Auftrag von Moses Gunesch >> Gesendet: Freitag, 28. M?rz 2008 07:10 >> An: Mailing list for the Go ActionScript Animation Platform >> Betreff: [Golist] Go version 0.4.6 >> >> PLEASE drop a comment here when you've used this build, I certainly >> don't want to just merge something that alters the LinearGo >> constructor and shaft everyone's subclasses. Thanks! >> >> >> _______________________________________________ >> GoList mailing list >> GoList at goasap.org >> http://goasap.org/mailman/listinfo/golist_goasap.org > > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org From moses at goasap.org Mon Mar 31 13:52:25 2008 From: moses at goasap.org (Moses Gunesch) Date: Mon, 31 Mar 2008 16:52:25 -0400 Subject: [Golist] Go version 0.4.6 In-Reply-To: <857090D3-E16C-49DF-BB5C-E1DC0CAC608C@bennybula.com> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> <005c01c88e4f$1dee5ba0$59cb12e0$@org> <41D454DC-8AF0-46F3-AA07-EFC08DFFA4D5@goasap.org> <007201c8923f$b98e12f0$2caa38d0$@org> <99AE8BDB-6E0D-47CC-B1DA-F5A476E2E39F@goasap.org> <857090D3-E16C-49DF-BB5C-E1DC0CAC608C@bennybula.com> Message-ID: Ah yes, good one. Not sure why those weren't coming through in my tests but I see very clearly in the code that _easeParams is referenced before it's set. I have updated version 046 at the goasap repository, can you please let me know if this fixes the problem? thanks! (PS: you using Go for a Saab website?) On Mar 31, 2008, at 10:43 AM, Robert Sk?ld wrote: > Hey Moses, > > I've just tried to move to the new version, got revision 31 from the > branch, and I'm getting this error: > > TypeError: Error #1009: Cannot access a property or method of a null > object reference. > at org.goasap.items::LinearGo/stop()[/Users/slaskis/Projects/ > PublicClass/Saab/source/org/goasap/items/LinearGo.as:577] > at org.goasap.utils::PlayableGroup/stop()[/Users/slaskis/Projects/ > PublicClass/Saab/source/org/goasap/utils/PlayableGroup.as:309] > at org.goasap.utils::SequenceStepCA/stop()[/Users/slaskis/Projects/ > PublicClass/Saab/source/org/goasap/utils/SequenceStepCA.as:166] > at org.goasap.utils::SequenceBase/stop()[/Users/slaskis/Projects/ > PublicClass/Saab/source/org/goasap/utils/SequenceBase.as:228] > at org.goasap.utils::SequenceCA/stop()[/Users/slaskis/Projects/ > PublicClass/Saab/source/org/goasap/utils/SequenceCA.as:209] > at org.goasap.utils::SequenceBase/start()[/Users/slaskis/Projects/ > PublicClass/Saab/source/org/goasap/utils/SequenceBase.as:210] > at org.goasap.utils::SequenceCA/start()[/Users/slaskis/Projects/ > PublicClass/Saab/source/org/goasap/utils/SequenceCA.as:200] > ... (and more, but it's not relevant i think) > > It seems like the _easeParams is set to null (i put a trace there in > the LinearGo.stop() method). Is there something i need to do? I'm > running super() in the constructor of the class that extends LinearGo, > but would i have to run some other method as well? > > Cheers! > > /bob > > > On Mar 30, 2008, at 18:49, Moses Gunesch wrote: >> Cool thanks Sebastian. >> >> Anyone else out there have any LinearGo classes yet, that they can >> try with the new version? >> >> You'll need to adjust the constructor's super() call, and also >> unlike in earlier versions calling the constructor is mandatory >> because it now verifies default values and sets up the repeater. >> >> So yes, let me know if this works or not. >> >> -m >> >> >> >> >> On Mar 30, 2008, at 4:26 AM, Sebastian Weyrauch wrote: >> >>> Seems to work fine, thanks. >>> >>> Von: golist-bounces at goasap.org [mailto:golist-bounces at goasap.org] >>> Im Auftrag von Moses Gunesch >>> Gesendet: Freitag, 28. M?rz 2008 07:10 >>> An: Mailing list for the Go ActionScript Animation Platform >>> Betreff: [Golist] Go version 0.4.6 >>> >>> PLEASE drop a comment here when you've used this build, I certainly >>> don't want to just merge something that alters the LinearGo >>> constructor and shaft everyone's subclasses. Thanks! >>> >>> >>> _______________________________________________ >>> GoList mailing list >>> GoList at goasap.org >>> http://goasap.org/mailman/listinfo/golist_goasap.org >> >> _______________________________________________ >> GoList mailing list >> GoList at goasap.org >> http://goasap.org/mailman/listinfo/golist_goasap.org > > > _______________________________________________ > 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/20080331/111ec31f/attachment.html From robert at bennybula.com Mon Mar 31 15:23:01 2008 From: robert at bennybula.com (=?ISO-8859-1?Q?Robert_Sk=F6ld?=) Date: Tue, 1 Apr 2008 00:23:01 +0200 Subject: [Golist] Go version 0.4.6 In-Reply-To: References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> <005c01c88e4f$1dee5ba0$59cb12e0$@org> <41D454DC-8AF0-46F3-AA07-EFC08DFFA4D5@goasap.org> <007201c8923f$b98e12f0$2caa38d0$@org> <99AE8BDB-6E0D-47CC-B1DA-F5A476E2E39F@goasap.org> <857090D3-E16C-49DF-BB5C-E1DC0CAC608C@bennybula.com> Message-ID: <80AD595C-1C5D-435B-BB30-5CEE36F547FE@bennybula.com> Thanks Moses! It seems to work fine now! :) I'm having some other issues though and maybe some of you guys have some input for me. As i've said before in the list i've been working on a xml parser for Go, it's a very simple one really, i basically used Moses video "fuse- like" tutorial, and switched the object into a xml node, using attributes instead. So far it works great. But, as i'm creating these "animation-objects" from the xml, and then i apply them, by assigning an id to those xml nodes, to a target display object (unless the xml specified a certain target). And then the animation is "executed" from an event mostly. I also use sequencing/grouping (just like the tutorial). And it works, but not very stable while testing, as it sometimes seems to not run at all on some targets, or just stops in the middle of a tween sometimes. The events are called but the animation wont run sometimes as well. And also, the most weird bug, is that the durations of the tweens seems to get shorter by everytime, but not always. (the best kind of bugs :P) As the events for those tweens sometimes is called very often i added a static reference dictionary to all the running tweens (i couldn't find one in Go already) so i could stop it if it was already running. (didn't help really though) A thought occured to me, that maybe Go has some kind of "aggressive" garbage collection, so when an animation is finished (stopped or complete) it might throw away that "animation-object" created from the xml? Or it's just my implementation that sucks :P Anyway, thanks for an awesome platform, I'm sure it's the future of tweening! :) /bob On Mar 31, 2008, at 22:52, Moses Gunesch wrote: > Ah yes, good one. Not sure why those weren't coming through in my > tests but I see very clearly in the code that _easeParams is > referenced before it's set. > > I have updated version 046 at the goasap repository, can you please > let me know if this fixes the problem? > > thanks! > > _______________________________________________ > GoList mailing list > GoList at goasap.org > http://goasap.org/mailman/listinfo/golist_goasap.org From moses at goasap.org Mon Mar 31 15:41:40 2008 From: moses at goasap.org (Moses Gunesch) Date: Mon, 31 Mar 2008 18:41:40 -0400 Subject: [Golist] Go version 0.4.6 In-Reply-To: <80AD595C-1C5D-435B-BB30-5CEE36F547FE@bennybula.com> References: < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> <005c01c88e4f$1dee5ba0$59cb12e0$@org> <41D454DC-8AF0-46F3-AA07-EFC08DFFA4D5@goasap.org> <007201c8923f$b98e12f0$2caa38d0$@org> <99AE8BDB-6E0D-47CC-B1DA-F5A476E2E39F@goasap.org> <857090D3-E16C-49DF-BB5C-E1DC0CAC608C@bennybula.com> <80AD595C-1C5D-435B-BB30-5CEE36F547FE@bennybula.com> Message-ID: Hmm... well, GC is not aggressive. What we did was we had to "retain" objects while they are running. For tweens this is done by GoEngine. For PlayableGroup & Sequence it's done using an internal static property called _playRetainer. All of your issues sound like strange & ghostly apparitions. (I'm calling the GhostBusters now...) -m On Mar 31, 2008, at 6:23 PM, Robert Sk?ld wrote: > Thanks Moses! > > It seems to work fine now! :) > > > I'm having some other issues though and maybe some of you guys have > some input for me. > > As i've said before in the list i've been working on a xml parser for > Go, it's a very simple one really, i basically used Moses video "fuse- > like" tutorial, and switched the object into a xml node, using > attributes instead. So far it works great. > But, as i'm creating these "animation-objects" from the xml, and then > i apply them, by assigning an id to those xml nodes, to a target > display object (unless the xml specified a certain target). And then > the animation is "executed" from an event mostly. I also use > sequencing/grouping (just like the tutorial). > > And it works, but not very stable while testing, as it sometimes seems > to not run at all on some targets, or just stops in the middle of a > tween sometimes. The events are called but the animation wont run > sometimes as well. And also, the most weird bug, is that the durations > of the tweens seems to get shorter by everytime, but not always. (the > best kind of bugs :P) > > As the events for those tweens sometimes is called very often i added > a static reference dictionary to all the running tweens (i couldn't > find one in Go already) so i could stop it if it was already running. > (didn't help really though) > > A thought occured to me, that maybe Go has some kind of "aggressive" > garbage collection, so when an animation is finished (stopped or > complete) it might throw away that "animation-object" created from the > xml? > > Or it's just my implementation that sucks :P > > > Anyway, thanks for an awesome platform, I'm sure it's the future of > tweening! :) > > /bob > > > On Mar 31, 2008, at 22:52, Moses Gunesch wrote: >> Ah yes, good one. Not sure why those weren't coming through in my >> tests but I see very clearly in the code that _easeParams is >> referenced before it's set. >> >> I have updated version 046 at the goasap repository, can you please >> let me know if this fixes the problem? >> >> thanks! >> >> _______________________________________________ >> GoList mailing list >> GoList at goasap.org >> http://goasap.org/mailman/listinfo/golist_goasap.org > > > _______________________________________________ > 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/20080331/c669f3b6/attachment.html From jan at renderstormstudios.com Mon Mar 31 23:38:53 2008 From: jan at renderstormstudios.com (Jan m. Danielsson) Date: Tue, 01 Apr 2008 08:38:53 +0200 Subject: [Golist] Go version 0.4.6 In-Reply-To: References: < > < > < > <766255DF-152A-43E0-839A-1F61AB748A58@goasap.org> < > <40FD80AD-6FFF-400A-AE78-6E19EC7FC285@goasap.org> < > < > <5D2E8EDA-ED7E-4D34-8180-70FEA4685DC7@goasap.org> < > < > <005c01c88e4f$1dee5ba0$59cb12e0$@org> < > <41D454DC-8AF0-46F3-AA07-EFC08DFFA4D5@goasap.org> < > <007201c8923f$b98e12f0$2caa38d0$@org> < > <99AE8BDB-6E0D-47CC-B1DA-F5A476E2E39F@goasap.org> < > <857090D3-E16C-49DF-BB5C-E1DC0CAC608C@bennybula.com> < > < > <80AD595C-1C5D-435B-BB30-5CEE36F547FE@bennybula.com> Message-ID: Hi there Moses! First of all - awesome job on Go! I love this tweening system. Now to the problem - bob wrote about his problems when making a xml parser including Go. I have a similar (I think) problem. This is NOT only related to the new version with the repeater in linearGo. I had the issue with the former version of linearGo, and I have the issue when using the latest build of the branch. I?m making a gallery where thumbnails is placed in a rectangular grid. When you roll over a thumbnail wiith the mouse, the picture "comes closer" to the viewer, and then moves back in place when mouse rolles out. This is done using linearGo for tweening the movement, and using Papervision3D for the movement itself. There are also "category buttons" which, when rolled over, moves all thumbnails in that category closer to the viewer, and then back again when mouse rolles out of the button. The problem comes when clicking the category buttons. When a category button is clicked, all the thumbnails belonging to that category are moved to one place and "stacked" in front of each other. This is done using linearGo. The function cycles through the thumbnails, and if the thumbnail belongs to the clicked category, it is assigned a linearGo which will move it to the "stacking place". The linearGo instance will have a delay which is increased for every thumbnail, resulting in a successing movement of the thumbnails, rather all the thumbnails moving at ones. The problem is that if the duration property of the linearGo is too short, some thumbnails are "skipped" and not moved by the Go system. When I increase the duration to 0.4 this problem disappears. The thumbnails that are skipped varies; sometimes no thumbnails are skipped, mostly some are skipped, and they are mostly different ones every time - seems very random. The skipped thumbs always seem to be the ones in the beginning of the cycle though. Since I solved the problem by increasing the duration, I didn?t bother. But when bob wrote of his problem, I was reminded again. So I tried using the new version of linearGo, but there?s no difference. The total number of thumbnails in the gallery that are cycled thorugh are 90. The number in a clicked category varies between 40 and 80. As I said, the same number of thumbs are also moved when a category button is rolled over, but then no thumbs are ever skipped. The difference is that no delay is used. I tried to use a dealy on the roll over function, but no tweens were skipped even if I used the same delay and duration as when clicked. I use the same kind of eventlistener in both cases, so it seems quite strange. Hope this can give some clue to what (if anything) is failing. I am aware that it could be my implementation that is faulty, but since everything works fine when using longer durations, i don?t know .... And remember, I?m still totally impressed with this system. Go! ///JmD