**** BEGIN LOGGING AT Tue Aug 14 02:59:59 2012 Aug 14 03:20:57 That sucks Aug 14 04:29:32 i know Aug 14 17:25:47 Woo hoo Aug 14 17:25:57 clientLayoutKind for MoreToolbar :) Aug 14 22:47:11 /msg NickServ VERIFY REGISTER olafura pubvfojadhuc Aug 14 22:56:35 /msg NickServ VERIFY REGISTER olafura Aug 14 22:56:52 /msg NickServ VERIFY REGISTER olafura pubvfojadhuc Aug 14 22:59:50 Hi I'm Olaf I'm hacking on some stuff with enyojs, I really like it but I'm doing some deep level stuff and my head is spinning a little :) If somebody knows a lot about enyo then I really would like to chat with him/her Aug 15 01:36:29 olafura: hello, I can chat a little bit about some Enyo stuff...depends on how deep you want to go, though :) Aug 15 01:41:34 * rrix is resisting attempts to ghost him Aug 15 02:05:49 pwd Aug 15 02:05:53 oops Aug 15 02:07:32 #/irc/enyojs Aug 15 02:17:19 uhm, so http://www.webosnation.com/webos-gbu-become-quasi-independent-company-focused-user-experience-and-cloud-meet-gram Aug 15 02:17:22 what is this? Aug 15 02:18:45 as if anyone who knew anything would say anything Aug 15 02:25:47 sugardave: I've gotten pretty deep but I think I've crawled my way out. I'm making a pluggable database container for widgets. Aug 15 02:26:22 Now if Pouchdb didn't use callback so much :P Aug 15 02:27:55 I'm thinking about making a queue for actions that happen before I get the database back from Pouchdb. Aug 15 02:30:12 I might refactor the front end part of Pouchdb to suite enyo better. Then I can use the adapters from it and possible make more with replication between them. Aug 15 02:32:20 sugardave: I'm using the same model as UiComponent uses to load Layout, pretty neat. Aug 15 02:33:33 olafura: cool, that's something I haven't delved into yet, basing something on UiComponent Aug 15 02:34:42 sugardave: It doesn't take much, maybe I should write a tutorial after this Aug 15 02:35:12 yes, please! Aug 15 02:41:14 sugardave: I'm wondering it is bad conduct looking into container for children if I'm using a wrapper around them or should I have a wrapper around the children as they are laid out in different containers like FittableRows? Aug 15 02:43:38 So DataComponent-FittableRows-(input*) or FittableRows-DataComponent*-input Aug 15 02:45:40 they would have a special variable indicating that they were data aware Aug 15 02:46:02 to me, that looks like the difference between having multiple data components vs. a data component with multiple inputs Aug 15 02:49:16 sugardave: the problem is that I would write a recursive function that spawns a new instance if it finds a container otherwise checks for the variable in the first example. The second will have a lot more components but will not have a problem with digging down, just checks it's children. Aug 15 02:53:40 I think the first one is cleaner and does not exclude the other one, maybe people would have to mark the container also **** ENDING LOGGING AT Wed Aug 15 02:59:59 2012