tag:robotlegs.tenderapp.com,2009-10-18:/discussions/robotlegs-2/759-mediating-textfieldsRobotlegs: Discussion 2013-02-07T16:22:02Ztag:robotlegs.tenderapp.com,2009-10-18:Comment/235564102013-01-07T18:58:49Z2013-01-07T18:58:49ZMediating TextFields ?<div><p>Hi Gustavo,</p>
<p>Are you using Robotlegs 2? If so, native flash objects are
filtered out for performance reasons:</p>
<p><a href=
"https://github.com/robotlegs/robotlegs-framework/blob/master/src/robotlegs/bender/extensions/viewManager/impl/StageObserver.as#L25">
https://github.com/robotlegs/robotlegs-framework/blob/master/src/ro...</a></p>
<p>If you're using RL1 you should almost certainly be able to
mediate text fields.</p></div>Shaun Smithtag:robotlegs.tenderapp.com,2009-10-18:Comment/235564102013-01-08T07:17:18Z2013-01-08T07:19:16ZMediating TextFields ?<div><p>Hi Shaun,</p>
<p>Thank you for the quick response.</p>
<p>I'm using RL2.... I see now the filter in the link you sent
me...</p>
<p>hmmm.. I'm still wondering if this idea (Mediate TextFields to
populate the .text property from external config files) would be a
good approach.</p>
<p>What do you think?</p></div>Gustavotag:robotlegs.tenderapp.com,2009-10-18:Comment/235564102013-01-08T08:10:43Z2013-01-08T08:10:43ZMediating TextFields ?<div><p>Hey Gustavo,</p>
<p>Populating text from external files is good, but doing it by
mediating such low level types sounds very fragile to me.</p>
<p>If you want to, you can create a copy of the StageObserver
without the filter, and install it instead of the default
StageObserver by creating your own bundle:</p>
<p><a href=
"https://github.com/robotlegs/robotlegs-framework/blob/master/src/robotlegs/bender/bundles/mvcs/MVCSBundle.as#L60">
https://github.com/robotlegs/robotlegs-framework/blob/master/src/ro...</a></p>
<p>I do wonder if forcing that filter on everyone is a good idea -
it might be helpful to make the filter configurable.</p></div>Shaun Smithtag:robotlegs.tenderapp.com,2009-10-18:Comment/235564102013-01-08T18:17:08Z2013-01-08T18:17:10ZMediating TextFields ?<div><p>I would vote for a configurable filter.</p>
<p>This would/could also be useful in extensive projects with large
teams and libraries, where the head dev's could predefine or limit
(again thinking about performance) the mediation of specific types
and/or packages.</p></div>Gustavo