**** BEGIN LOGGING AT Wed Dec 05 02:59:59 2012
Dec 05 08:27:54 <pulsation> good morning :)
Dec 05 08:34:53 <pulsation> I've got a stupid code design question with enyo2, and it's pretty sure some of you have had the same problem
Dec 05 08:35:34 <pulsation> there are some places in my code where there are calls to this.container.container etc
Dec 05 08:35:58 <pulsation> for example, if there's a popup list that will fill a parent's fields
Dec 05 08:36:29 <pulsation> would there be a cleaner way to fill these fields from a grand-grand-children callback?
Dec 05 08:37:44 <pulsation> I guess this kind of thing is the reason why callbacks (ontap for example) are defined in his container
Dec 05 08:38:33 <pulsation> maybe my gui structure is bad then?
Dec 05 08:39:39 <pulsation> in one of the cases, there's a form containing a popup containing a layout containing a list that has to update the form's fields.
Dec 05 08:43:31 <pulsation> maybe js' closures variables scopes would have fit in this case, but I'm not sure how it can be appliable concretely here.
Dec 05 08:45:00 <katratxo> pulsation: the main idea of components is encapsulation, your component shouldn't know anything about the parent container or its grandparent
Dec 05 08:45:35 <katratxo> pulsation: for achiving the behaviour container.containter, you should use events
Dec 05 08:46:25 <katratxo> your component emits an event, and some other component in the hierachy should capture and process it
Dec 05 08:47:03 <pulsation> katratxo: right. didn't even think about it "--
Dec 05 08:47:13 <katratxo> pulsation: https://github.com/enyojs/enyo/wiki/Event-Handling
Dec 05 08:48:17 <pulsation> katratxo: thanks.
Dec 05 08:48:39 <katratxo> remember that if you want to stop the event propagation in the hierarchy, your grand parent function should return true
Dec 05 08:51:24 <katratxo> there is other (perhaps outdated) document on event handling http://enyojs.com/docs/events.html
Dec 05 08:53:02 <pulsation> okay :)
Dec 05 08:59:10 <pulsation> katratxo: may I ask you about the difference between bubble and waterfall? does that mean that bubble would propagate to all the component's parents, and waterfall to all its children?
Dec 05 09:30:36 <katratxo> bubble as you may expect, emits the event and propagates up in the hierarchy
Dec 05 09:31:51 <katratxo> waterfall is the way for a 'parent' component to emit an event to all its child components, waterfall propagation is down in the hierarchy
Dec 05 09:33:15 <katratxo> pulsation: http://forums.enyojs.com/discussion/comment/4102/#Comment_4102
Dec 05 09:38:12 <pulsation> katratxo: ok, thank you
Dec 05 09:38:56 <katratxo> np
Dec 05 19:05:54 <ka6sox> anyone here?
Dec 05 19:07:00 <ka6sox> I've not figured out how to get a textfile to be displayed in a scroller...it just refuses to do so.
**** ENDING LOGGING AT Thu Dec 06 02:59:59 2012