**** BEGIN LOGGING AT Thu Mar 28 02:59:58 2013
**** BEGIN LOGGING AT Thu Mar 28 11:23:01 2013
**** BEGIN LOGGING AT Thu Mar 28 11:31:15 2013
Mar 28 16:23:07 <madnificent> is there a way to say that the components that were supplied for the initialization should be created in one of my named components?  i thought there was, but i can't seem to find it.
Mar 28 16:26:20 <summatusmentis> when you create them, you can set their parent
Mar 28 16:27:20 <summatusmentis> this.$.named_component.createComponents();
Mar 28 16:27:32 <summatusmentis> basically, you say where you want to create them
Mar 28 16:27:39 <mephinet> madnificent: I think I remember that the RowServer uses this feature to inject content into the VirtualRepeater. Maybe check the docs for "controlParentName" or "client"...
Mar 28 16:28:41 <madnificent> mephinet: yeah, that sounds more or less like what i'm remembering, i'll search
Mar 28 16:29:24 <summatusmentis> or are you talking about when they're in the components: [] block?
Mar 28 16:29:27 <madnificent> summatusmentis: yeah, though i'd want it to happen more declaratively at the moment (so it works without me meddling with create)
Mar 28 16:29:36 <madnificent> summatusmentis: correct!
Mar 28 16:31:56 <summatusmentis> I think you're looking for the "owner" parameter?
Mar 28 16:32:12 <madnificent> no
Mar 28 16:32:29 <summatusmentis> why?
Mar 28 16:32:32 <madnificent> the owner just sets the owner, not where the component is to be rendered.
Mar 28 16:33:01 <summatusmentis> oh yes, you're right
Mar 28 16:34:14 <summatusmentis> so, your named component, will it also be created in your components: [] block?
Mar 28 16:34:23 <madnificent> what i want is something like this enyo.kind({name:"Mine",components:[{name:"foo"},{name:"bar"}],componentsTarget:"bar"}); and then somewhere create a new one of these and make the components block be rendered in bar.  something like new Mine({components:[{content:"bazinga!"}]});
Mar 28 16:35:05 <summatusmentis> I see
Mar 28 16:35:06 <madnificent> there should be support for something like this, as the documentation of Component puts the components block of the kind in kindComponents.
Mar 28 16:35:20 <madnificent> and i think i saw/heard/read/used a feature of this kind in the past.
Mar 28 16:37:23 <summatusmentis> http://enyojs.com/api/#enyo.Control::renderInto
Mar 28 16:38:11 <summatusmentis> is that what you're looking for?
Mar 28 16:38:38 <madnificent> no, if i would do it manually, i would be able to do this.$.named_component.createComponents(...).  that would do what i want, but then i'd do it at create (which is later than i want them to exist).
Mar 28 16:39:02 <madnificent> so renderInto would be a more primitive way of doing it, instead of a more abstract way
Mar 28 16:40:11 <summatusmentis> so, roughly, you want to be able to say: new Mine({components:[{content: "bazinga!"}], parent: "whatever"});
Mar 28 16:40:49 <madnificent> i want the kind definition of mine to be able to say that.
Mar 28 16:41:01 <summatusmentis> I see
Mar 28 16:41:12 <summatusmentis> interesting, so any Mine you would create would know what it's parent is
Mar 28 16:41:25 <madnificent> mephinet: where can i find the RowServer, the API isn't helping me out, and there's no file named RowServer either, it seems
Mar 28 16:41:55 <madnificent> summatusmentis: no.  mine knows that it should render the components block which it is given into a named component, instead of into itself.
Mar 28 16:42:35 <summatusmentis> hrm
Mar 28 16:43:56 <madnificent> this is such an obvious thing that it must be simple to do.  i'm surprised i can't find it.
Mar 28 16:45:22 <summatusmentis> a quick grep shows various internal stuff setting parentNode
Mar 28 16:45:28 <summatusmentis> which will set your DOM node parent
Mar 28 16:46:52 <summatusmentis> and parent
Mar 28 16:47:06 <mephinet> madnificent: there is a RowServer.js on my disk: /opt/PalmSDK/Current/share/framework/enyo/1.0/framework/source/base/list/RowServer.js
Mar 28 16:47:06 <mephinet> so it's enyo 1.0
Mar 28 16:48:01 <mephinet> https://github.com/enyojs/enyo-1.0/blob/master/framework/source/base/list/RowServer.js
Mar 28 16:48:34 <madnificent> mephinet: ahhhh, noooos.  i don't want it to be an Enyo1 feature :P
Mar 28 16:48:34 <summatusmentis> check out ln 684 of api/build/enyo.js
Mar 28 16:48:47 <summatusmentis> you can set the parent: attribute of a Kind
Mar 28 16:48:53 <summatusmentis> they do it in UiComponent
Mar 28 16:49:04 <summatusmentis> there's also a controlParentName
Mar 28 16:49:10 <mephinet> sorry, I'm so out of date...
Mar 28 16:49:20 <madnificent> the simplest i can find is overriding createComponent and overriding based on the isChrome property.
Mar 28 16:51:06 <madnificent> summatusmentis: that's a lot of manual work.  i will then need to figure out /when/ the component needs to be generated.  being both when a component is added to my component, or at create.  i would also need to check whether it would work correctly on destroy.  i don't want to be bothered by that, there's too much room for error.
Mar 28 16:52:19 <madnificent> anyways, i thought there was something cleaner.
Mar 28 16:52:46 <summatusmentis> I'm confused, weren't you looking for controleParentName ?
Mar 28 17:01:14 <madnificent> summatusmentis: where is that documented?
Mar 28 17:10:25 <madnificent> i've now implemented it by overriding and dispatching to the internal _createComponent of Component.  which is /exactly/ what i want to say (though not as clean as i'd want it).
Mar 28 17:10:43 <madnificent> how are patches to be submitted?  i have a gigantic meta-programming thing available still
Mar 28 17:11:10 <madnificent> (which should gain some attention before they want to accept it, i guess, but it really is helpful once you grok it)
Mar 28 17:14:14 <madnificent> BACKLOG SOLUTION: _createComponent:function(inInfo,moreInfo){ return moreInfo.isChrome ? this.inherited(arguments) : this.$.your_component_name._createComponent(inInfo,moreInfo); }
**** ENDING LOGGING AT Fri Mar 29 02:59:59 2013