Glue 0.2

[Sean Clark Hess]

I've release Glue 0.2, with some small, but significant changes.

Basically I decided to start creating tags that make sense
semantically, even if they are the same under-the-hood. An example of
this is <Route> which is the same as <Observe> but is specifically
designed to route view events to a controller, while observe is now
designed to observe controllers.

I also added another example: Login - this demonstrates a login
overlay, and shows how glue can simplify some of the more tricky parts
of a login screen.

Please visit http://wiki.github.com/seanhess/glue for more
information.

[finelinestudio]

I've just taken a look through the sample code, and it looks very
interesting. I currently use Mate, and am much happier with that
approach than Cairngorm etc. but also have the same concerns as you
over lack of strong-typing. I'm definitely interested to try it out -
hopefully soon, although I've got a lot on the "to try out" list -
I'll let you know how I go.

[Sean Clark Hess]

That's great. Let me know when you've had a chance to try it. 

[finelinestudio]

Finally giving it a go, looks like a few things have changed since my
first look, a GlueMap is now a Controller, right? And the old
controllers have become services? (Memory's as bit vague on the last
bit). The main other thing on my "to try out" list was the Tide
framework of GraniteDS. I'm weighing up if Glue and Tide complement
each other (Glue helping move Tide context dependencies from views
into a central control domain) or just add complexity.

Some basic tag reference would be great. Not sure what the "model"
attribute of a Route is, for example. Also, not sure how to pass along
properties of an event? Seems like the "event" object available in a
Route is a flash.events.Event, with no payload capacity? Must we drill
into the view to grab any necessary data?

Good work, Sean, impressive stuff for an early cut.

On Apr 25, 5:07 am, Sean Clark Hess <seanh...@gmail.com> wrote:
> That's great. Let me know when you've had a chance to try it.
>
> On Fri, Apr 24, 2009 at 12:49 AM, finelinestudio

> <finelinestu...@gmail.com>wrote:

[Sean Clark Hess]

Ah, documentation, my favorite thing :) Yes, things have changed, and the examples should all be updated. Please visit the following link for the examples and a newly updated tag reference. Take a look at the Architecture page for my recommendations on architecture. 

http://wiki.github.com/seanhess/glue/documentation

Not sure what the "model"

attribute of a Route is, for example.

Um... it really shouldn't have one. Route current extends Observe under the hood, so it has it, but it shouldn't be used. I'll fix it so it doesn't have it. Meanwhile, the tag documentation is up to date. 

Also, not sure how to pass along

properties of an event? Seems like the "event" object available in a

Route is a flash.events.Event, with no payload capacity? Must we drill

into the view to grab any necessary data?

You have two options here. I prefer to drill in or expose the information needed to respond to an event (for example, update a variable on your view before firing a flash.events.Event), but you can also get info from the original event using scope. Look at CurrentScope in the docs. It looks like this:

<Route event="{CustomEvent.CUSTOM}" call="service.go(scope.event.whatever)"/>

As for tide, I haven't tried it, but I'd imagine that you could use Glue any number of ways to help improve other frameworks. 

Good work, Sean, impressive stuff for an early cut.

Thanks! I'm looking forward to more feedback from you. Let me know how it goes. 

[finelinestudio]

Thanks, I had missed the wiki link, that makes everything much
clearer.

Cheers, Tim

On May 13, 1:02 am, Sean Clark Hess <seanh...@gmail.com> wrote:
> Ah, documentation, my favorite thing :) Yes, things have changed, and the
> examples should all be updated. Please visit the following link for the
> examples and a newly updated tag reference. Take a look at the Architecture

> page for my recommendations on architecture.http://wiki.github.com/seanhess/glue/documentation

>
> Not sure what the "model"
>
> attribute of a Route is, for example.
>
> Um... it really shouldn't have one. Route current extends Observe under the
> hood, so it has it, but it shouldn't be used. I'll fix it so it doesn't have
> it. Meanwhile, the tag documentation is up to date.
>
> Also, not sure how to pass along
>
> properties of an event? Seems like the "event" object available in a
>
> Route is a flash.events.Event, with no payload capacity? Must we drill
>
> into the view to grab any necessary data?
>
> You have two options here. I prefer to drill in or expose the information
> needed to respond to an event (for example, update a variable on your view
> before firing a flash.events.Event), but you can also get info from the
> original event using scope. Look at CurrentScope in the docs. It looks like
> this:
>
> <Route event="{CustomEvent.CUSTOM}"
> call="service.go(scope.event.whatever)"/>
>
> As for tide, I haven't tried it, but I'd imagine that you could use Glue any
> number of ways to help improve other frameworks.
>
> Good work, Sean, impressive stuff for an early cut.
>
> Thanks! I'm looking forward to more feedback from you. Let me know how it
> goes.
>