tag:robotlegs.tenderapp.com,2009-10-18:/discussions/problems/35-mediation-of-components-contained-within-a-flex-popupRobotlegs: Discussion 2018-10-18T16:35:08Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/8878022010-01-21T07:15:01Z2010-01-21T07:15:01ZMediation of components contained within a flex PopUp<div><p>I'm currently thinking of constructing the list object myself
within the PopUp's mediator and then adding it to the popup after
I've provided binding for the list data.<br></p>
<p>Even so I think I would still have to loop through the data and
manually create a mediator for each renderer needed to receive the
list. Am I wrong?</p></div>levi.stropetag:robotlegs.tenderapp.com,2009-10-18:Comment/8878022010-01-21T07:18:31Z2010-01-21T07:18:31ZMediation of components contained within a flex PopUp<div><p>I just don't see any good reason to mediate an item renderer
outside of convenience. Flex 3 item renderers are JACKED. If you
implement mx.controls.listClasses.IDropInListItemRenderer it is
easy to get at the list/grid and dispatch the events from there.
Item renderers are just so volatile... In the Signals/RL example I
posted recently I did inject a Signal into my renderers. That
worked well.</p>
<p>We need to make a Robotlegs PopupManager...</p></div>Joel Hookstag:robotlegs.tenderapp.com,2009-10-18:Comment/8878022010-01-21T07:33:08Z2010-01-21T07:33:08ZMediation of components contained within a flex PopUp<div><p>You guys never sleep! I'll take that to my team this morning, in
about 7 hours, and see if we can't figure this one out based on
your advice Joel.</p>
<p>I do find it funny you call my mediation of the item renderer
<code>convenient</code> :) I thought convenience would have me just
put all the logic in the renderer and be done with it! But based on
everything else you've said, that might be the lesser of the evils.
And you're absolutely right on all accounts - item renderers are
more like list obfuscators.<br></p></div>levi.strope