fluid-work IRC Logs-2012-05-10

Owned by Fluid IRC Log Bot
Last updated: May 10, 2012Version comment
1 min read

[11:31:38 CDT(-0500)] <avtar> kasper: http://ec2-107-21-143-113.compute-1.amazonaws.com:8080/demos/Mammals.html

[11:31:41 CDT(-0500)] <avtar> (smile)

[11:32:49 CDT(-0500)] <kasper> avtar: cool! Will that be the URL we should use for the demo

[11:32:57 CDT(-0500)] <avtar> yes

[11:33:26 CDT(-0500)] <avtar> yura and i just tried it with his latest changes

[11:33:37 CDT(-0500)] <avtar> it resulted in a flurry of high fives

[11:45:30 CDT(-0500)] <kasper> awesome!!!! Thanks a lot avtar and yura1

[12:39:58 CDT(-0500)] <Justin_o> Bosmon: I think i figured out the problem.. I had two instances of "decapod.eventBinder" one was a direct subcomponent of and the other was subcomponent a level or two further down. When I wrote the demands block it added a listener to both of the "decapod.eventBinder" subcomponents which is why it was firing twice. I suppose with the namespace the second instance of it now just replaces the first.

[12:49:53 CDT(-0500)] <Justin_o> Bosmon: do you have a suggestion for a proper way around this… lower level component shouldn't be getting the listener. The only thing I could think of would be to write another demands block that is more specific to the lower level component to prevent it from matching. Is that the only way, or is there a better solution?

[12:52:40 CDT(-0500)] <Justin_o> Bosmon: I probably could have avoided this in general if invokers were naturally able to be called in the listeners block. Not sure if there are plans for that at all.