**** BEGIN LOGGING AT Sun Jan 04 02:59:58 2015
Jan 04 19:35:46 <DougReeder_> For Inputs in a DataRepeater, how do I catch the onchange events?
Jan 04 19:39:09 <Semanticfire_2> maybe wrap it in a kind which handles the event ?
Jan 04 19:39:28 <Semanticfire_2> if you use bindings you could also attacht it to the underlying model
Jan 04 19:53:30 <DougReeder_> Apparantly, the event is passed to the child of the repeater.
Jan 04 19:54:03 <DougReeder_>  I don’t need to modify the model of the item, I need to add a (blank) item to the Collection under certain circumstances.
Jan 04 20:05:29 <Semanticfire_2> okay
Jan 04 20:07:02 <DougReeder_> I can obtain it from inSender.owner.owner.$.addressRepeater.collection, but that’s ugly.
Jan 04 20:09:20 <Semanticfire_2> I don't see why a kind wouldn't work in you case
Jan 04 20:10:17 <DougReeder_> You think the event can be caught by the DataRepeater?
Jan 04 20:20:03 <Semanticfire_2> if you create a datarepeater it will repeat its components, if you create a kind in that component then you would be able to catch the event
Jan 04 20:20:20 <Semanticfire_2> ( sorry for the delay )
Jan 04 20:21:30 <DougReeder_> A custom kind as the child of the DataRepeater? It looks like that would work
Jan 04 20:22:15 <DougReeder_> It would still need to use inSender.owner.owner.$.addressRepeater.collection to obtain the collection.
Jan 04 20:24:54 <Semanticfire_2> you could also use bubbleUp
Jan 04 20:25:04 <Semanticfire_2> to send a even up the chain
Jan 04 20:25:17 <DougReeder_> …or, it seems, this.ownder.$.addressRepeater.collection.
Jan 04 20:26:14 <DougReeder_> Shouldn’t they bubble up already?
Jan 04 20:26:41 <Semanticfire_2> I'm not enteryly sure what it is you want to do
Jan 04 20:27:09 <Semanticfire_2> a items in the data repeater should call back to the repeater to add a empty item to the collection of the data repeater ?
Jan 04 20:27:19 <DougReeder_> Eh, a gist would be more clear, but it would take too much time to boil down to a simpel gist.
Jan 04 20:27:30 <Semanticfire_2> I know that feeling :)
Jan 04 20:27:38 <Semanticfire_2> but in the end this helped me in this channel as well
Jan 04 20:28:07 <DougReeder_> Basically, the last item in the collection is blank. When it’s filled in, another item needs to be added to the end.
Jan 04 20:28:30 <DougReeder_> Like phone numbers in the webOS Contacts app.
Jan 04 20:30:41 <Semanticfire_2> ok
Jan 04 20:36:56 <dmanderson> morning enyos
Jan 04 20:37:00 <DougReeder_> Hey, http://enyojs.com/docs/latest/index.html#/kind/enyo.Collection has a link to http://enyojs.com/docs/latest/index.html#/kind/enyo.Collection:AddOptions - which doesn’t work.
Jan 04 20:37:05 * DougReeder_ waves hello
Jan 04 20:39:11 <Semanticfire_2> hi dmanderson
Jan 04 20:39:34 <dmanderson> bah broken docs, sorry DougReeder
Jan 04 20:39:37 <dmanderson> hey SemanticFire2
Jan 04 20:39:40 <dmanderson> *_3
Jan 04 20:39:44 <Semanticfire_2> :)
Jan 04 20:39:48 <dmanderson> ugh can't type today
Jan 04 20:39:55 * DougReeder_ nods “New doc tool, bound to be bugs”
Jan 04 20:40:04 <Semanticfire_2> :9
Jan 04 20:40:06 <Semanticfire_2> :)
Jan 04 20:40:48 <Semanticfire_2> DougReeder_, so you actually look for a hook into the collection from which your repeater is created
Jan 04 20:41:21 * DougReeder_ nods
Jan 04 20:41:31 <Semanticfire_2> btw is the this.$.addressRepeater not available in the kind created ?
Jan 04 20:43:11 <DougReeder_> Here’s a gist of my actual code: https://gist.github.com/DougReeder/c0b195db36a534dc706e
Jan 04 20:43:57 <Semanticfire_2> link doesnt work
Jan 04 20:44:56 <DougReeder_> BTW, all DataRepeater examples have a single child, which just contains the “real” child.  And they don’t work properly without the extra layer. Why is that?
Jan 04 20:45:14 <Semanticfire_2> uhm what do you mean with that ?
Jan 04 20:47:08 <dmanderson> ^^ yeah I'm not following?
Jan 04 20:48:02 <DougReeder_> Look at https://github.com/enyojs/enyo/blob/master/samples/DataRepeaterSample.js  The child of the DataRepeater does nothing except contain the “real” children.
Jan 04 20:48:50 <Semanticfire> I do not understand what you mean
Jan 04 20:54:17 <DougReeder_> I guess the child of the DataRepeater also has the bindings.
Jan 04 20:55:15 <dmanderson> The child of the data repeater is really just an item template, yea
Jan 04 20:58:04 <DougReeder_> I guess the issue is really that that chilren of a DataRepeater are handled differently than children of a Repeater, and the docs don’t mention that.
Jan 04 20:58:39 <DougReeder_> See https://github.com/enyojs/enyo/blob/master/samples/RepeaterSample.js for comparison.
Jan 04 21:00:03 <DougReeder_> Or, take a working Repeater example, change to a DataRepeater, set the Collection, and watch it not work.
Jan 04 21:00:08 <Semanticfire_2> I don't see the difference
Jan 04 21:01:39 <DougReeder_> The Repeater sample has a child (name:"item”) which contains the individual controls.
Jan 04 21:02:41 <DougReeder_> The corresponding control in the DataRepeater sample has classes: "name-wrapper" and no name.  But it’s not a direct child of DataRepeater. It’s a grandchild of DataRepeater.
Jan 04 21:02:45 <Semanticfire_2> the datarepeate has a anonymous child { classes: name-wrapper
Jan 04 21:03:30 <Semanticfire_2> data repeater creates a 'container' element
Jan 04 21:04:27 <Semanticfire_2> but I do not really see the issue with that
Jan 04 21:07:14 <DougReeder_> I’m not sure how to put it any more clearly.
Jan 04 21:08:08 <Semanticfire_2> why is the different handling a problem ?
Jan 04 21:08:09 <DougReeder_> Anyway, gotta go.  Thanks for listening!
Jan 04 21:08:21 <Semanticfire_2> ok :)
Jan 04 21:16:49 <Semanticfire> dmanderson, working sunday shifts ? :)
Jan 04 21:17:01 <dmanderson> getting caught up from holiday :)
Jan 04 21:17:56 <Cage1___> Any thoughts on what DougReeder_ was noting?
Jan 04 21:19:19 <dmanderson> I agree the use between the Repeater and the DataRepeater don't feel super natural, but I don't think they are too wildly different
Jan 04 21:28:27 <Semanticfire> I couldn't get it either
Jan 04 21:28:52 <Semanticfire> although i see his point on interacting with the collection from the repeated element a interesting one.
Jan 04 21:29:09 <Semanticfire> ( e.g. if I want to delete myself from the collection ? )
Jan 04 21:30:04 <Cage1___> i think his point was there is an extra layer between the repeater, container and children...therefore making it confusing to transition from Repeater to DataRepeater. and he (and i) aren't sure why it has to be so...or that it isn't documented thoroughly...
Jan 04 21:31:12 <Semanticfire> I agree as well
Jan 04 21:32:08 <dmanderson> It isn't really documented, and so I'm only guessing as well, as it was built before my time.
Jan 04 21:32:18 <dmanderson> But really it's just the binding directives are living outside of the item template.
Jan 04 21:32:23 <dmanderson> which is the extra layer
Jan 04 21:33:00 <dmanderson> datarepeater[bindings[item-template]] vs repeater[item-template[]]
Jan 04 21:35:10 <Cage1___> so would it be easier to change to be consistent, or easier to document that the difference exists for YY reason? :)
Jan 04 21:38:18 <dmanderson> lol at this point, documentation ;D
Jan 04 22:06:23 <Semanticfire_2> well if you expect enyo to pick up there needs to be some effort in there
Jan 04 22:12:49 <Semanticfire_2> anyhow gnight
**** ENDING LOGGING AT Mon Jan 05 02:59:58 2015