[Golist] the possibilities of go

[Brett Coffin]

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 <moses at goasap.org> 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