...
[13:52:38 CDT(-0500)] <Bosmon> Thanks
[13:52:52 CDT(-0500)] <Justin_o> Bosmon: we can change the topic though, if you'd like to talk about that tomorrow
[13:53:08 CDT(-0500)] <Bosmon> No, next week works fine
[13:53:09 CDT(-0500)] <Justin_o> or anastasiac might want to do more documentation
[13:53:13 CDT(-0500)] <Justin_o> Bosmon: okay.. cool
[14:04:02 CDT(-0500)] <Justin_o> Bosmon, anastasiac: do we have any docs with the fully hydrated component trees still
[14:04:39 CDT(-0500)] <anastasiac> hm...
[14:04:42 CDT(-0500)] * anastasiac searches
[14:05:13 CDT(-0500)] <anastasiac> we have this page, Justin_o: http://wiki.fluidproject.org/display/docs/ProtoComponent+Types
[14:05:20 CDT(-0500)] <anastasiac> is that what you're looking for?
[14:06:23 CDT(-0500)] <Justin_o> anastasiac: not really sorry.. i want the old style.. before protocomponents
[14:06:30 CDT(-0500)] <anastasiac> ah
[14:06:31 CDT(-0500)] <anastasiac> hm
[14:06:58 CDT(-0500)] <Justin_o> Bosmon: do you know in the old style are children the only point of nesting where the nested object would have an ID and valuebinding
[14:07:22 CDT(-0500)] <anastasiac> how about this, Justin_o? http://wiki.fluidproject.org/display/Infusion13/Renderer+Component+Trees
[14:07:46 CDT(-0500)] <Bosmon> http://wiki.fluidproject.org/display/Infusion13/Fluid+Renderer+-+Background
[14:07:51 CDT(-0500)] <Bosmon> This page also describes them
[14:07:58 CDT(-0500)] <Bosmon> yes, "children" is the only route for nesting components
[14:09:32 CDT(-0500)] <Justin_o> Bosmon: thanks
[14:14:08 CDT(-0500)] <cindyli> Bosmon: in IoC testing system, can I pass an argument list to an event listener? for example,
[14:14:10 CDT(-0500)] <cindyli> sequence: [{
[14:14:10 CDT(-0500)] <cindyli> listener: "fluid.tests.checkTopComponents",
[14:14:10 CDT(-0500)] Wiki Markup <cindyli> event: "{fluid.tests.videoPlayerMediaPanels}.events.onReady"
[14:14:10 CDT(-0500)] <cindyli> }]
[14:14:52 CDT(-0500)] <cindyli> i tried to pass an "args" option but doesn't work
[14:15:38 CDT(-0500)] <Bosmon> cindyli - "doesn't work" is the classic terrible problem report
[14:15:48 CDT(-0500)] <cindyli> haha
[14:15:53 CDT(-0500)] <Bosmon> You can see some examples of "args" in the "TestingTest.js" test cases
[14:16:03 CDT(-0500)] <Bosmon> What kind of "doesn't work" did you experience?
[14:16:31 CDT(-0500)] <Bosmon> I guess there isn't an example of "args" with "listener" ....
[14:16:38 CDT(-0500)] <cindyli> i did, the test cases with "args" are all for modelChanged type of listener, not any for event listeners
[14:17:12 CDT(-0500)] <cindyli> well, modelChanged is an event too i guess, but perhaps being processed differently
[14:17:31 CDT(-0500)] <Bosmon> I see
[14:17:36 CDT(-0500)] <Bosmon> Actually, what would you want "args" to do in this case?
[14:17:43 CDT(-0500)] <Bosmon> I guess some boiling
[14:17:48 CDT(-0500)] <cindyli> exactly
[14:18:01 CDT(-0500)] <Bosmon> What in particular do you want to boil into the signature?
[14:18:06 CDT(-0500)] <cindyli> and "expectedResult", "testType"
[14:18:20 CDT(-0500)] <Bosmon> aha
[14:18:29 CDT(-0500)] <Bosmon> Yes, it seems this isn't implemented
[14:18:33 CDT(-0500)] <Bosmon> Would you like to implement it? : P
[14:18:54 CDT(-0500)] <cindyli> sure
[14:19:35 CDT(-0500)] <Bosmon> I'll be happy to review your pull
[14:19:35 CDT(-0500)] <cindyli> a bit scary to modify framework code but you will review it anyway
[14:19:54 CDT(-0500)] <Bosmon> Well, I think it's time for people to stop being scared
[14:20:04 CDT(-0500)] <cindyli> will give a try
[14:20:30 CDT(-0500)] <Bosmon> It should only take an "if" statement and a call to fluid.expandOptions...
[14:20:41 CDT(-0500)] <Bosmon> Actually my latest pull request with declarative change binding contains a good example of how to do this
[14:20:50 CDT(-0500)] <Bosmon> The current framework code for event boiling is very convoluted
[14:20:50 CDT(-0500)] <cindyli> ah ha
[14:20:57 CDT(-0500)] <Bosmon> But the change binding pull takes a much more direct approach
[16:01:44 CDT(-0500)] <yzen_> Bosmon: hi