**** BEGIN LOGGING AT Tue Dec 23 02:59:59 2014
Dec 23 15:32:37 <EricBlade1> gm all
Dec 23 16:07:22 <Cage1___> good morning!
Dec 23 16:12:12 <Semanticfire> hi
Dec 23 16:12:20 <Semanticfire> any1 experience with repeaters ?
Dec 23 16:17:45 <Cage1___> a little
Dec 23 16:17:48 <Cage1___> whats up
Dec 23 16:19:23 <Semanticfire> If I want multiple items I need to create a array right ?
Dec 23 16:19:25 <Semanticfire> ohw alarm
Dec 23 16:20:55 <EricBlade1> for a regular repeater, you can kind of set it up in any way  you choose, although i suspect an array is probably the easiest thing to work with
Dec 23 16:21:13 <EricBlade1> for a DataRepeater, you want a Collection, I think.
Dec 23 17:51:36 <sugardave> yes, DataRepeater uses enyo.Collection....which is an array-like structure of models.  You can pass an array directly to collection.add() to build it
Dec 23 17:52:34 <sugardave> in my not-so-humble opinion on this topic, I recommend using DataRepeater instead of Repeater going forward....it's just easier to deal with overall
Dec 23 18:00:56 <sugardave> same for List and DataList, in case anyone is wondering
Dec 23 19:29:05 <Semanticfire> I'm not sure if collections are not to much overhead for what I want to do
Dec 23 19:37:03 <Semanticfire> can I have other objects in collections ?
Dec 23 19:40:02 <dmanderson> You can have anything in a collection Semanticfire
Dec 23 19:40:29 <dmanderson> It’s just a collection of models
Dec 23 19:41:11 <Semanticfire> hi dmanderson
Dec 23 19:41:27 <dmanderson> Howdy!
Dec 23 19:41:36 <Semanticfire> so even complex stuff ?
Dec 23 19:42:32 <dmanderson> Yeah, I mean most of what a collection does is some generic interaction with a model
Dec 23 19:43:49 <Semanticfire> k
Dec 23 19:55:37 <Semanticfire> but the datarepeater does need field pointers to do the mapping
Dec 23 19:57:30 <Semanticfire> if you do the binding at least
Dec 23 19:58:10 <Semanticfire> I still need a setupitem to some complex stuff, is that also posible with a data repeater ?
Dec 23 20:07:18 <sugardave> there is no setupRow for DataRepeater...I usually offload the complexities to the models
Dec 23 20:08:40 <sugardave> actually, I offload the complexities to the kinds that will have the models mapped to them and which comprise the rows of the DataRepeater
Dec 23 20:11:51 <Semanticfire> hmm
Dec 23 20:12:53 <Semanticfire> so you add a binding form the full model , to a property in the kind ?
Dec 23 20:23:32 <sugardave> when the collection of a DataRepeater changes/is set, it generates whatever component you have in it for each model in the collection and also sets the model to it
Dec 23 20:23:58 <sugardave> so you don't need to specifically bind the model to the kind, it's auto-magic
Dec 23 20:24:17 <Semanticfire> you have fidle of that ?, the sample in the doc is to simple imho
Dec 23 20:24:36 <sugardave> then, in the kind you just set up bindings from model.whatever to $.foo.content, for example
Dec 23 20:24:58 <sugardave> Semanticfire: if not, I can cook one up...it will be a little while, though
Dec 23 20:26:06 <Semanticfire> so I create a seperate kind which just takes this full model ?
Dec 23 20:39:30 <sugardave> yes
Dec 23 20:39:37 <sugardave> let me see if I already have a simple one for that
Dec 23 20:43:50 <sugardave> Semanticfire: not exactly the simplest.  This is actually a DataRepeater with embedded DataList, but you can see what is going on.  The outer DataRepeater uses the form that's probably(?) in the sample, while the inner DataList uses a defined kind and sets no bindings
Dec 23 20:43:58 <sugardave> http://jsfiddle.net/sugardave/xmbJ8/
Dec 23 20:44:39 <sugardave> it's an older example so not using the bindings string syntax that you should use in 2.5.1 (getting rid of the preceding ., etc.)
Dec 23 20:59:23 <Semanticfire> okay I need to digest that one
Dec 23 20:59:54 <sugardave> just pay attention to the DataList part
Dec 23 21:10:50 <Semanticfire> I'm trying to :)
Dec 23 21:11:34 <sugardave> I'm making a slightly simpler one, hang on if you have a minute
Dec 23 21:11:52 <Semanticfire> I'm waiting for fires...
Dec 23 21:15:36 <sugardave> Semanticfire: http://jsfiddle.net/sugardave/wmpt285e/
Dec 23 21:15:40 <sugardave> this is just the repeater
Dec 23 21:16:00 <sugardave> it shows the item doing "complex operations" with a simple transform on the value it is getting from the model
Dec 23 21:17:53 <Semanticfire> okay
Dec 23 21:19:54 <Semanticfire> I'm trying to see if I can map this to the trick I try to pull :)
Dec 23 21:20:40 <sugardave> you can do it!
Dec 23 21:21:20 <Semanticfire> my tip for this example is the somewhat ambigious naming of kinds / components / attributes
Dec 23 21:24:13 <Semanticfire> so the 'model' magically apears in the kind ?
Dec 23 21:24:41 <sugardave> yeah, that is a good point...in some other examples I was working on way back when I had named some model properties "foo" and the component names where to render were "notFoo"
Dec 23 21:25:09 <sugardave> Semanticfire: yes, the DataRepeater or DataList will apply the model each time it renders that kind
Dec 23 21:31:48 <Semanticfire> so I could access the model from a constructor as well ?
Dec 23 21:33:01 <sugardave> perhaps, let's see
Dec 23 21:33:21 <sugardave> do you need it in the constructor, or is create sufficient?
Dec 23 21:33:39 <Semanticfire> create would probably work
Dec 23 21:37:29 <sugardave> Semanticfire: looks like in create, you can get at the model either before or after you would run the inherited call; for constructor, only after
Dec 23 21:38:54 <Semanticfire> that could do
Dec 23 21:39:13 <Semanticfire> I'll look into it the comming days
Dec 23 21:39:20 <Semanticfire> ( its too late here now ;) )
Dec 23 21:39:23 <sugardave> cool, let me know how it progresses :D
Dec 23 21:39:52 <sugardave> I love DataRepeater/DataList and how much more awesome it is than the old ones
Dec 23 21:40:02 <sugardave> s/it is/they are/
Dec 23 21:40:02 <synergybot> sugardave meant: I love DataRepeater/DataList and how much more awesome they are than the old ones
Dec 23 21:40:28 <sugardave> thanks synergybot!
Dec 23 21:42:35 <Semanticfire> :)
Dec 23 21:47:49 <Semanticfire> still there ?
Dec 23 21:49:16 <Semanticfire> is there a sample off datagridlist ?
Dec 23 21:49:40 <sugardave> that I don't have offhand
Dec 23 21:49:49 <sugardave> but it should follow a similar pattern
Dec 23 21:50:42 <Semanticfire> okay
Dec 23 21:50:47 <Semanticfire> I'll look into it
Dec 23 21:51:56 <Semanticfire> in you example, I can have components in the 'WidgetView' component in the enyo.datarepeater
Dec 23 21:52:42 <sugardave> yes, you certainly can
Dec 23 21:53:07 <Semanticfire> okay
Dec 23 22:16:43 <dmanderson> Sorry went to lunch, back now :D
Dec 23 22:17:09 <dmanderson> You also have the Parse method as well
Dec 23 22:31:11 <sugardave> baby steps ;)
Dec 23 23:11:31 <EricBlade1> sugardave: sadly, List and DataList act quite differently on the UI side.  And there's a PulldownList but no PulldownDataList :D
Dec 23 23:19:22 <sugardave> EricBlade1: how so on the UI difference?
Dec 23 23:19:48 <sugardave> you could try your hand at making PulldownDataList ;)
Dec 23 23:26:28 <EricBlade1> sugardave: hmm. i'd have to revert my code several revisions or build a new test to remember specifically.. something about the scrolling acts really different in DataList..
Dec 23 23:28:28 <EricBlade1> it might even be just some settings.  i'm pretty sure a list will do touchscroll even if you're using a mouse, datalist doesn't
Dec 23 23:28:33 <EricBlade1> there may be other things
Dec 23 23:28:34 <sugardave> intersting...I never noticed
Dec 23 23:29:15 <sugardave> it SHOULD behave the same way
Dec 23 23:29:58 <EricBlade1> it might be specifically the PulldownList that does that, though,
Dec 23 23:30:19 <EricBlade1> this app has gone from List -> PulldownList -> DataList, and I just remember it definitely acts differently.
Dec 23 23:30:49 <sugardave> personal app or company app?
Dec 23 23:30:52 <EricBlade1> Personal
Dec 23 23:31:06 <EricBlade1> when I drag a DataList, my items receive tap events, which is also different
Dec 23 23:31:22 <EricBlade1> and clicking in the scrollbar also generates tap events
Dec 23 23:33:00 <sugardave> you weren't using moon.DataList were you?
Dec 23 23:33:13 <EricBlade1> no
Dec 23 23:33:19 <sugardave> k
Dec 23 23:49:42 <Semanticfire> parse method ?
Dec 23 23:50:33 <sugardave> Semanticfire: yes, models and collections can set parse: true and then provide a parse method so that you can manipulate the data before the model is made
Dec 23 23:51:07 <Semanticfire> hmmm
Dec 23 23:52:58 <Semanticfire> but models are lightweight, so there is no kind infrastructure in there right, e.g. watterfallin will not work
Dec 23 23:53:22 <sugardave> right
Dec 23 23:53:28 <sugardave> it's not based on enyo.Object
Dec 23 23:53:46 <Semanticfire> okay, then the kind which interacts with the model works better in my use case
Dec 23 23:54:16 <Semanticfire> dmanderson, did you ever look in the left/right arranger issues with 2 panels ?
Dec 23 23:55:50 <sugardave> that has been around a LOOOOOONG time
Dec 23 23:56:16 <Semanticfire> yup:(
Dec 23 23:56:31 <sugardave> I used to force 3 components and then disallow going to the 3rd/reset index to the 2nd or whatever I needed it to do
Dec 23 23:56:56 <sugardave> it works okay unless you want to wrap:true :D
Dec 24 00:11:48 <dmanderson> Sorry got disconnected, no haven’t had a chance :(
**** ENDING LOGGING AT Wed Dec 24 02:59:59 2014