**** BEGIN LOGGING AT Tue Jun 09 02:59:58 2015 Jun 09 14:45:28 Hey, does anyone here have any experience using the Intl.js polyfill? Jun 09 17:47:50 Well, I ran into a problem with scrolling that I can't seem to get out of. http://jsfiddle.net/ac8cca2u/ Jun 09 17:48:33 I'm trying to scroll using dragging (finger scrolling) but it won't scroll. If you uncomment the line at the bottom. it works. weird. Jun 09 17:50:31 What makes body work and div not work? Jun 09 17:57:11 Zectbumo: That *is* weird Jun 09 17:57:23 I'm not sure what is causing that. Jun 09 17:57:23 you see what I mean too right? Jun 09 17:57:32 you might want to try stepping through the code Jun 09 17:57:45 set some breakpoints in the TouchScrollStrategy kind Jun 09 18:30:23 Zectbumo: Yes, I see the problem you are describing Jun 09 18:30:40 chall: any idea what could be causing that problem that Zectbumo is seeing? Jun 09 18:44:25 GodGinrai, I haven't really used the touch scrolling at all, but I'll give it a look. Jun 09 19:10:17 GodGinrai, Zectbumo, I think I found the problem Jun 09 19:10:25 oh? Jun 09 19:10:33 in the fiddle, the body tag has 0 height by default Jun 09 19:10:36 that's why it doesn't work Jun 09 19:11:04 the body tag is the one that is working though Jun 09 19:11:14 it's the div that doesn't work Jun 09 19:11:19 yes, when you switch it to the body tag, it has its height set properly Jun 09 19:12:05 https://jsfiddle.net/ac8cca2u/1/ Jun 09 19:13:44 interesting. the body and the html have to both be set. leaving out one will go back to one not working Jun 09 19:15:18 a height problem was my first instinct. That's always been the problem whenever I had Scroller problems Jun 09 19:16:34 It was mine as well, but I never thought to mess with the HTML tag Jun 09 19:17:42 this just doesn't make sense to me. styling html tag that is. besides scrolling shouldn't be that finicky Jun 09 19:17:45 * Semanticfire_2 is looking for a way to dynamically create component Jun 09 19:18:06 that doesn't seem like it'd be too difficult Jun 09 19:18:11 or more specific, ad a new kind to components Jun 09 19:18:14 Semanticfire: createComponent() Jun 09 19:18:37 and how to add it to the components attribute ? Jun 09 19:18:57 Semanticfire: lets say you have a kind like this: Jun 09 19:19:20 enyo.kind({ name: "Test", kind: "enyo.Control" Jun 09 19:19:24 components: [ Jun 09 19:19:25 Semanticfire_2, use children instead of components Jun 09 19:19:34 { name: "hello" } Jun 09 19:19:35 ] Jun 09 19:19:39 I think it's children... Jun 09 19:19:40 }); Jun 09 19:19:59 then you can use this.$.hello.createComponent to add it as a component of "hello" Jun 09 19:20:11 okay Jun 09 19:20:30 and create component takes the kind notation ? Jun 09 19:20:41 http://enyojs.com/docs/latest/index.html#/kind/enyo.Component:createComponent Jun 09 19:21:13 Semanticfire: takes the same notation you would use in a components block Jun 09 19:22:04 let try :) Jun 09 19:30:25 as Jun 09 19:34:31 Semanticfire: remember to call render() on the component that you run createComponent from so that they show up Jun 09 19:37:29 okay, that works :) Jun 09 19:37:49 is there a way I can 'clone' a kind from itself onto its parrent ? Jun 09 19:38:48 e.g. enyo.kind({name:'foo', components: [{name: 'bar'}]}); Jun 09 19:38:52 what do you mean? Jun 09 19:39:05 from bar I want to create a clone of bar into foo Jun 09 19:39:12 foo.components Jun 09 19:40:00 so... you want foo [ {bar } ] to become foo [ { bar }, { bar } ]? Jun 09 19:41:15 yup, where I know that won'T work because of the double names Jun 09 19:41:32 e.g. enyo.kind({name:'foo', components: [{kind: 'bar'}]}); Jun 09 19:41:36 was a better example :) Jun 09 19:42:07 not really. Your example makes no sense to me. It's just a kind with a component in it Jun 09 19:45:05 This seems like an xyproblem Jun 09 19:45:22 Semanticfire_2: http://mywiki.wooledge.org/XyProblem Jun 09 19:48:34 I want the kind bar to be able to create a copy of itself in foo Jun 09 19:48:40 this is not a XY problem Jun 09 19:49:00 maybe lazy Jun 09 19:51:49 So you want foo to have bar as a child, and then when something happens in bar, for foo to make a second bar as a second child? Jun 09 19:52:18 What exactly does this enable for you? Jun 09 19:55:56 cardinallity of the element bar Jun 09 19:58:07 ? Jun 09 20:00:27 I use enyo to parse and display RDF / linked data, where the cardinality of graph nodes is not defined Jun 09 20:00:56 which means that property foo can have 0-n instances of objects bar Jun 09 20:01:15 wouldn't a repeater be simpler for that purpose? Jun 09 20:01:16 I can deal with that in 2 ways, either in bar or in foo, just investigating both Jun 09 20:01:40 btw, rule of encapsulation: parent handles children, not the other way around Jun 09 20:01:43 yes / no , its a bit overkill when cardinality [0,1] Jun 09 20:01:48 I know Jun 09 20:02:25 anyway, I g2g Jun 09 20:02:27 leaving work Jun 09 20:08:46 Semanticfire_2: http://jsfiddle.net/613vthzh/ Jun 09 20:09:56 nice :) Jun 09 20:11:05 but it creates a instance of the same kind, not a copy Jun 09 20:12:35 you would have to copy what you need I suppose. I tried this and it gets oop errors http://jsfiddle.net/613vthzh/2/ Jun 09 20:12:41 it still works though :P **** ENDING LOGGING AT Wed Jun 10 02:59:59 2015