**** BEGIN LOGGING AT Wed Oct 03 02:59:59 2012
Oct 03 12:52:27 <dcramer> any reason why setupItem will not be called in a List ?
Oct 03 13:13:41 <fxspec06> count is set to zero
Oct 03 13:17:08 <dcramer> fxspec06: k, thanks
Oct 03 13:18:08 <dcramer> fxspec06: nope count is not 0
Oct 03 13:21:37 <fxspec06> the only other reason
Oct 03 13:21:44 <fxspec06> is that the list does not have a height property.
Oct 03 13:22:06 <fxspec06> you can confirm this by giving it a set height
Oct 03 13:22:18 <fxspec06> but proper is to make it work with fir
Oct 03 13:22:20 <fxspec06> fit*
Oct 03 13:23:49 <dcramer> fxspec06: nope, turns out I was subclassing List, if you do that you have to add a handlers: property
Oct 03 13:23:59 <dcramer> it can't be specified in the ctor
Oct 03 13:24:00 <dcramer> ???
Oct 03 13:24:31 <fxspec06> you're subclassing it? as in extending it? you don't have to have a handlers property
Oct 03 13:26:00 <dcramer> extending it
Oct 03 13:26:07 <dcramer> fxspec06: well I defined it like enyo.kind( {
Oct 03 13:26:08 <dcramer>                 name: "LogList",
Oct 03 13:26:09 <dcramer>                 kind: "List",
Oct 03 13:26:11 <dcramer>                 fit: true,
Oct 03 13:26:12 <dcramer>                 count: 100,
Oct 03 13:26:13 <dcramer>                 onSetupItem: "setupItem",
Oct 03 13:26:14 <dcramer>                 published: {data: [] },
Oct 03 13:26:15 <dcramer> and it didn't work
Oct 03 13:26:23 <dcramer> when I added a handler it worked
Oct 03 13:26:45 <fxspec06> that's not how you should be doing it though
Oct 03 13:26:48 <fxspec06> like
Oct 03 13:27:15 <fxspec06> you'd want to use list as its own component inside your own kind
Oct 03 13:27:42 <fxspec06> like enyo.kind({ name: "myspecialkind", components [....... ] ........ });
Oct 03 13:27:50 <fxspec06> and inside that components block you'd put
Oct 03 13:28:06 <fxspec06> { kind: "List", count: 100, onSetupItem: "setupItem" }
Oct 03 13:28:23 <fxspec06> then in your mysepcialkind add the setupItem: (s, e) {} function
Oct 03 13:28:44 <fxspec06> that's how it's supposed to work
Oct 03 13:29:22 <dcramer> fxspec06: ok, makes some sense, but there is no "supposed to " guide
Oct 03 13:29:29 <fxspec06> what you're doing is probably too advanced if you don't know what you're doing, i would say. handlers is a separate concept
Oct 03 13:29:31 <dcramer> no reason why it shouldn't work though
Oct 03 13:29:38 <fxspec06> well you're skipping the point of enyo
Oct 03 13:29:49 <dcramer> oh ?
Oct 03 13:29:58 <fxspec06> i mean i don't really know how to explain it
Oct 03 13:30:06 <dcramer> fxspec06: ok, thx
Oct 03 13:30:26 <fxspec06> just keep going, you'll probably see what i'm talking about after you play around some more
Oct 03 13:31:14 <fxspec06> handlers allows you to capture events INSIDE a kind
Oct 03 13:31:24 <fxspec06> what you are trying to do is capture the event OUTSIDE of the kind
Oct 03 13:31:32 <fxspec06> this is automatically done
Oct 03 13:32:24 <fxspec06> in the "List" kind, setupItem is already defined. therefore if you defined setupItem in a List kind that you subclassed, you'd be overriding it. which really isn't what you want to do if i'm not mistaken
Oct 03 13:33:15 <dcramer> ah, ok
Oct 03 13:33:16 <fxspec06> you could get around this by adding : "this.inherited(arguments);" in there, which would call the setupItem from the "List" code (inherited fucntions)
Oct 03 13:33:20 <dcramer> makes sense
Oct 03 13:33:44 <fxspec06> but again this is most best used for having your own custom List kind, like a camo list or something
Oct 03 13:33:52 <fxspec06> generalized
Oct 03 13:34:04 <fxspec06> best i can describe it in the morning
Oct 03 13:37:23 <dcramer> np,, thanks
**** ENDING LOGGING AT Thu Oct 04 02:59:58 2012