Hi,
Was this problem resolved? I have Flex 3 MXML that defines:
<mx:Application>
...
<utils:FABridge bridgeName="foo"/>
...
</mx:Application>
In Flex 4, must this statement now appear inside an <fx:Declarations> element?
Even if there's no other fx namespace elements being used in the MXML?
On the JavaScript side, I've been referencing the bridge as:
FABridge.foo.root()
which works fine in Flex 3 but doesn't resolve the bridge in Flex 4. How is the
bridge referenced?
Thanks, Garry
--- In flexcoders@yahoogroups.com, "Brian J. Ackermann" <brian.ackerm...@...>
wrote:
>
> http://code.google.com/p/flex-iframe/source/browse/trunk/examples/IFrameCommTest/src/com/google/code/flexiframe/examples/IFrameCommTest.mxml
>
>
> lines 80 & 81
>
> in the original example, there was no ID
>
> Thanks
>
> ------------------------------
> Brian J. Ackermann
> brian.ackerm...@...
> 952.373.1626
> ------------------------------
>
>
>
>
>
> On Thu, Aug 26, 2010 at 3:27 PM, Alex Harui <aha...@...> wrote:
>
> >
> >
> > I just noticed you didn't specify an id="FABridge" in your
> > <fx:Declarations>
> >
> > What was the equivalent statement in Flex 3?
> >
> >
> >
> > On 8/26/10 10:45 AM, "Brian J. Ackermann" <brian.ackerm...@...>
> > wrote:
> >
> >
> >
> >
> >
> >
> > From my testing, I believe the problem is on the JS side of thing, and that
> > the FABridge doesn't 'live' in the same location in the DOM in flex4, as
> > compared with flex3.
> >
> > But we're both reasonably novice flex developers, so we could be
> > mis-interpreting what we're seeing. In another version of the project, I
> > have added some debugging to a text area on screen, and
> > "this.parent.FABridge" and "parent.FABridge" and "FABridge" all return
> > 'undefined'. Since that used to work just fine in flex3, it seems like
> > maybe I just need to find the new 'path' in the DOM....
> >
> > for example:
> >
> > this.parent.foo.bar.blah.FABridge
> >
> > Thanks,
> >
> > Brian
> >
> >
> > ------------------------------
> > Brian J. Ackermann
> > brian.ackerm...@...
> > 952.373.1626
> >
> > ------------------------------
> >
> >
> >
> >
> >
> > On Thu, Aug 26, 2010 at 12:38 PM, Alex Harui <aha...@...> wrote:
> >
> >
> >
> >
> >
> >
> > I don't have time right now to look and I don't deal much with FABridge,
> > but are you now saying that parent.FABridge is now the issue? The OP said
> > it was FABridge.flex. Is this on the JS side or AS side? In Flex 4, a
> > child component's parent is not the main app, they get shoveled down into
> > the skin. It think the document or parentDocument properties or
> > FlexGlobals.topLevelApplication can access the main app.
> >
> >
> >
> >
> > On 8/26/10 9:10 AM, "Brian J. Ackermann" <brian.ackerm...@... <
> > http://brian.ackerm...@...> > wrote:
> >
> >
> >
> >
> >
> >
> > I'm trying to get the IFrameCommTest example (from
> > http://code.google.com/p/flex-iframe/) to work in Flex 4, and, while the
> > IFrame itself works, the communication does not. In particular, I need to
> > get the included HTML page to call functions from the flex app (I already
> > have a way to get the Flex app to talk to the HTML).
> >
> > I've exported the project to facilitate your help.
> > http://www.mediafire.com/file/172448jkkgva4ki/iframeCommTest.fxp
> >
> > The problem, is that the "parent.FABridge" doesn't exist. My guess is that
> > something in flex4 changed with regard to how things are located in the DOM.
> >
> > (This post is directly related to the original. I just thought this would
> > be a clearer example of the problem. )
> >
> > Thanks,
> >
> >
> > ------------------------------
> > Brian J. Ackermann
> > brian.ackerm...@... <http://brian.ackerm...@...>
> > 952.373.1626
> >
> > ------------------------------
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Alex Harui
> > Flex SDK Team
> > Adobe System, Inc.
> > http://blogs.adobe.com/aharui
> >
> >
> >
>
