**** BEGIN LOGGING AT Mon Dec 29 02:59:58 2014
Dec 29 19:21:59 <Roy__> Semanticfire: You should be able to bind to enyo.input value.  I've done it many times
Dec 29 19:28:47 <Semanticfire> Roy__, yeah I figured out it was a different issue
Dec 29 19:29:23 <Semanticfire> Roy__, have a sec to look at jsfiddle for me ?
Dec 29 19:29:47 <Semanticfire> http://jsfiddle.net/6wsf0wmw/1/
Dec 29 19:32:48 <Semanticfire> from line 29 on
Dec 29 19:34:31 <dmanderson> Morning enyos!
Dec 29 19:35:58 <Semanticfire> ey dmanderson
Dec 29 19:38:50 <Roy__> Semanticfire: Looking..
Dec 29 19:39:17 <Semanticfire> so I want to do a I dynamic binding from within a kind, to one of its later add component
Dec 29 19:39:37 <Roy__> mmm
Dec 29 19:40:03 <Semanticfire> I ended up hacking the components / owner.$ properties to make my components available in the $ of my kind
Dec 29 19:40:11 <Semanticfire> it works flawlessly
Dec 29 19:40:40 <Semanticfire> ( In my code I use a recursive loop to go through the components tree )
Dec 29 19:40:50 <Roy__> That sounds horrible.
Dec 29 19:41:09 <Roy__> I'm still not sure what you want to accomplish here.
Dec 29 19:41:18 <Roy__> And with 2.5.1 you don't need the leading . in the bindings.
Dec 29 19:42:05 <Semanticfire> ohw okay
Dec 29 19:42:26 <Roy__> You want to bind to dynamic components?  Is that it?
Dec 29 19:42:30 <Semanticfire> yup
Dec 29 19:43:04 <Roy__> So, you probably just want to dynamically add a binding then
Dec 29 19:45:47 <Roy__> Just call .binding() after creating the new component.
Dec 29 19:45:59 <Roy__> As you're doing.  Is it not working?
Dec 29 19:46:12 <Semanticfire> okay I mis understood you
Dec 29 19:46:37 <Semanticfire> from my kind I want to allow bindings to components created inside my components structure at defenition time
Dec 29 19:47:23 <Roy__> dynamically created or defined in advanced?
Dec 29 19:48:10 <Roy__> Or are you saying you want a child to bind to its siblings?  Or to its parents?
Dec 29 19:49:54 <Semanticfire> what I do in my sample
Dec 29 19:49:59 <Semanticfire> I want to have a wrapper kind
Dec 29 19:50:24 <Semanticfire> so something which I can wrap around other default components
Dec 29 19:52:21 <Roy__> http://jsfiddle.net/6wsf0wmw/3/ ?
Dec 29 19:54:10 <Semanticfire> I know that works, but I want to define the logic in the binding in my wrapper kind
Dec 29 19:54:30 <Roy__> So...
Dec 29 19:54:34 <Roy__> You want the wrapper to
Dec 29 19:54:55 <Semanticfire> actually I'm pretty happy with my initial jsfiddle :)
Dec 29 19:55:31 <Roy__> do the binding to its children?
Dec 29 19:59:08 <Semanticfire> yup
Dec 29 20:04:11 <Roy__> How about this Semanticfire? http://jsfiddle.net/6wsf0wmw/4/
Dec 29 20:05:48 <Semanticfire> okay, the owner trick is actually pretty elegant
Dec 29 20:06:16 <Semanticfire> iow bindings can be everywhere
Dec 29 20:06:31 <Roy__> They're everywhere, man!
Dec 29 20:07:03 <Semanticfire> I get that :)
Dec 29 20:07:17 <Roy__> There may or may not be a big in bindings where you can't bind to a property elsewhere.
Dec 29 20:07:17 <Semanticfire> I was just assuming they need to be defined at the correct level
Dec 29 20:07:32 <Semanticfire> bug I presume :)
Dec 29 20:07:40 <Roy__> I tried this.binding({from: "myData", to: "owner." + this.bindTo}
Dec 29 20:07:55 <Roy__> But it didn't seem to work.
Dec 29 20:08:07 <Roy__> It -did- get set to z.
Dec 29 20:08:12 <Roy__> but it didn't get set to "hello world"
Dec 29 20:08:25 <Semanticfire> ok
Dec 29 20:08:49 <Semanticfire> I'll play with this
Dec 29 20:09:08 <Semanticfire> got my linked data wrapper working a lot better like this.
Dec 29 20:09:35 <Roy__> I still think the binding should be done at the owner level.  But I'm not entirely clear on your use case so, go with what works.
Dec 29 20:10:30 <Semanticfire> the reason I don't want that, is that I have rather complex and deep encapsulation ( component in component ) to work through linked data
Dec 29 20:11:14 <Semanticfire> if so it is hard to see where the bindings get defined etc. this way I can have the wrapper ( which gets data from a RDF source ) and its output close to one another
Dec 29 20:16:42 <Herrie|2> Hi all ;)
Dec 29 20:17:36 <Herrie|2> Seems we got a problem with input fields for LuneOS Enyo 2 apps after we upgrade from 2.3 to 2.5.1 (tested 2.5.3 Pre 5) as well. Problem is our VKB hides after every character
Dec 29 20:18:04 <Herrie|2> This happens with both onyx.Input and RichText kind
Dec 29 20:18:18 <Roy__> Semanticfire: Maybe you should move the data source into a model or source instead
Dec 29 20:18:34 <Herrie|2> Any ideas as to what might cause this or even better how to solve it
Dec 29 20:18:35 <Herrie|2> ?
Dec 29 20:19:23 <Semanticfire> Roy__, initially that is a good idea
Dec 29 20:19:32 <Herrie|2> Could be a focus issue on the fields somehow, but not sure
Dec 29 20:19:55 <Semanticfire> but with RDF that is close to impossible, since it is inherently unstructured
Dec 29 20:21:07 <Roy__> Herrie|2: Have you tried diffing Input between 2.3 and 2.5.1?
Dec 29 20:25:30 <Herrie|2> Roy__: Not yet
Dec 29 20:25:40 <Herrie|2> Should I look at the Enyo or Onyx Input or both?
Dec 29 20:29:11 <dmanderson> I thought we made some VKB changes in the last couple sprints, trying to remember/track down related changes.
Dec 29 20:29:22 <Herrie|2> Seems Onyx one doesn't do much
Dec 29 20:30:18 <Herrie|2> dmanderson we were on 2.3.0 RC4 previously and our LuneOS VKB (Malliit, we dropped EFIGS a while back) worked OK with that, but with 2.5.1 an 2.5.3 Pre 5 we have problems
Dec 29 20:31:01 <dmanderson> Sounds like basically somewhere along the introduction of Moonstone…
Dec 29 20:31:40 <Roy__> Herrie|2: Just enyo.input
Dec 29 20:31:54 <dmanderson> Also present in a 2.4 version Herrie|2?
Dec 29 20:32:08 <Herrie|2> Let me try that
Dec 29 20:35:29 <Roy__> Herrie|2: Actually, does it happen with enyo.Input?
Dec 29 20:35:40 <Roy__> Or only onyx.Input?
Dec 29 20:35:59 <Roy__> If only onyx, then look at differences in InputDecorator.
Dec 29 20:36:51 <Herrie|2> Trying 2.4 now, rebooting LuneOS ;)
Dec 29 20:37:40 <Herrie|2> 2.4 seems OK
Dec 29 20:38:57 <Herrie|2> Let me try something else, some bits in webos-lib were updated as well, just want to make sure that doesn't cause it
Dec 29 20:40:33 <dmanderson> \o/ ryanjduffy has entered the building!
Dec 29 20:40:45 <Roy__> dmanderson: They'll let anyone in this place.
Dec 29 20:40:50 <dmanderson> :D
Dec 29 20:41:57 <dmanderson> We’re passing 5% of the people they have in #emberjs! I call this success
Dec 29 20:42:34 <Herrie|2> OK the changes in webos-lib seem minimal, I doubt these would cause it? Anyone can have a look at these? https://github.com/micro-tech/webos-lib/commit/01e93e9d682b548673d2dd705ea7741a5b2728db
Dec 29 20:46:53 <ryanjduffy> @dmanderson happy ;)
Dec 29 21:05:14 <trex0051> I was wondering if you guys know of an enyo CDN that allows https?
Dec 29 21:14:46 <Roy__> trex0051: I have it on my list to look at CDNs now that 2.5.1 is released.
Dec 29 21:15:47 <Roy__> Any preferences?  I was looking at cdnjs.com.  Do they support https?
Dec 29 21:16:03 <trex0051> This article is VERY dated, but interesting : http://zoompf.com/blog/2010/01/should-you-use-javascript-library-cdns
Dec 29 21:16:08 <Roy__> it does.
Dec 29 21:16:12 <trex0051> Yes
Dec 29 21:16:49 <trex0051> Roy__: I was actually thinking just making http://enyojs.com/enyo-XX available via https would do the trick
Dec 29 21:19:38 <Roy__> Well, it might… but we'd have to buy an SSL certificate. :)
Dec 29 21:21:33 <trex0051> I usually get a 5 year for $7.95 a year from namecheap. :)
Dec 29 21:22:11 <trex0051> I figure the labor of updating it if you get shorter terms is not worth it :)
Dec 29 21:54:50 <Herrie|2> 2.5.0 is broken too, so something changed between 2.4.0 and 2.5.0 that broke it for us :S
Dec 29 22:32:35 <dmanderson> D:
**** ENDING LOGGING AT Tue Dec 30 02:59:58 2014