Mailing-List: contact users-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of webdoublefx@hotmail.com
 designates 157.55.0.229 as permitted sender)
Message-ID: <DUB402-EAS8346ABC26783EAD6CDDB4B4310@phx.gbl>
From: =?iso-8859-1?Q?Fr=E9d=E9ric_THOMAS?= <webdoublefx@hotmail.com>
To: <users@flex.apache.org>
References: 
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F5205FC@EXMBX05.netplexity.local>
	<CAPxJ8xtWLNJyKR0CgpbPNwdi2vfz9Kbnf-CPxzutY2XqcQtw6w@mail.gmail.com>
	<522517A6.2050006@austrosoft.com.ec>
 <CAPxJ8xs+s-ZgQVxCQDJ3HQnTestdBC_2s+5MUz5gd3_cHy7odA@mail.gmail.com>
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F520648@EXMBX05.netplexity.local>
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F520687@EXMBX05.netplexity.local>
 <DUB402-EAS376B022A0F18A0F3A23E2AAB4310@phx.gbl>
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F520936@EXMBX05.netplexity.local>
In-Reply-To: 
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F520936@EXMBX05.netplexity.local>
Subject: RE: question on modules
Date: Tue, 3 Sep 2013 13:22:24 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: 
 AQABAgMEml3x+LDtR4PkBt1eD1w8VQAKSXYgAFZG9AwAQRX6pgAr6dBKAJjNshgAKwh1GgDQTpFcnTwckIA=
Content-Language: fr

Usually, Parsley:PopUp can only detect the context of a Class if this =
one
has been added to a context, generally its module context in case it =
stands
in a module, when you use fast inject instead of configure, the class is =
not
added to the context, so Parsley:PopUp should return its closer above
context, am I wrong ?

-Fred

-----Message d'origine-----
De=A0: Maurice Amsellem [mailto:maurice.amsellem@systar.com]=20
Envoy=E9=A0: mardi 3 septembre 2013 12:18
=C0=A0: users@flex.apache.org
Objet=A0: RE: question on modules

That's what parsley Popup tag is supposed to do for me (call
context.viewManager.addViewRoot and addPopup). =20
Anyway, I reverted to the original implementation of parsley Popup, and
popup injections are now working fine, even in modules.

Thanks again for the help.

Maurice
-----Message d'origine-----
De=A0: Fr=E9d=E9ric THOMAS [mailto:webdoublefx@hotmail.com] Envoy=E9=A0: =
mardi 3
septembre 2013 02:49 =C0=A0: users@flex.apache.org Objet=A0: RE: =
question on
modules

Not sure I understood what you want at the end but if you want to open a
popup contains in a module, either you know the popup class and call it =
via
a static show function and inside the show function, you add "
context.viewManager.addViewRoot(yourPopupInstance);" before calling "
PopUpManager.addPopUp" or you don't know the popup class and you can =
create
an event/command in the module that call it in the same way I described
before.

-Fred

-----Message d'origine-----
De=A0: Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoy=E9=A0: mardi 3 septembre 2013 02:24
=C0=A0: users@flex.apache.org
Objet=A0: RE: question on modules

Actually, from SamplePopup.mxml,  =
parentApplication.sampleModuleLoader.child
points to the module...

So if I KNOW that the component is in module X , this is how to get it.

The problem is that I need a generic mechanism, that would allow me to =
get
the module instance of any ui component, even if there are several =
modules,
or even if it belongs to  the top level application.

FYI, the purpose of this is to fix an issue in Cairngorm3/Parsley 2.4 =
Popup
tag (ie com.adobe.cairngorm.popup.PopupBase class and subclasses), that =
does
not seem to be module aware.
Actually,  PopupBase.getParent() always returns
FlexGlobal.topLevelApplication even if the Popup tag belongs to a =
module,
instead of the module instance.
The effect of this is that the context is not computed correctly ( =
returns
the topLevel application context, instead of the module child context),
Which in turn prevent  FastInject from working inside Popups that are
declared in modules.

Regards,

Maurice=20

-----Message d'origine-----
De=A0: Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoy=E9=A0: mardi 3 septembre 2013 01:56
=C0=A0: users@flex.apache.org
Objet=A0: RE: question on modules

I am new to modules, so not sure to understand what you wrote.

This is how I am using the module:

In main app:
<s:ModuleLoader id=3D"sampleModuleLoader"  url=3D"../SampleModule.swf"/>

The module itself is declared as follows:

SampleModule.mxml
<s:Module>
 ...
</s:Module>

Then I have somewhere else a popup defined in the module =
SamplePopup.mxml
<s:TitleWindow ...>
   <s:TextInput id=3D"ti" />
</s:TitleWindow>

So what is moduleComponentId in this case ?=20

Maurice=20

-----Message d'origine-----
De=A0: Mark Kessler [mailto:kesslerconsulting@gmail.com]
Envoy=E9=A0: mardi 3 septembre 2013 01:21
=C0=A0: Users@flex
Objet=A0: Re: question on modules

Would something like either of the following have any effect on the your
pathing for test purposes?

(parentApplication.moduleComponentId as
Modulename).ventana.variableName.text =3D "test";

or

(parentApplication.moduleComponentId as =
Object).ventana.variableName.text =3D
"test";


-Mark

On Mon, Sep 2, 2013 at 6:56 PM, Michael Astudillo <
mastudillo@austrosoft.com.ec> wrote:

> Hi,
> When you try to access to a popup trougth a module first you create a=20
> variable like TitleWindow and second assign the call at this, for =
example:
>
> public var ventana:TitleWindow =3D new TitleWindow(); function =
Sample()=20
> {
>                ventana =3D
> PopUpManager.createPopUp(this,**titleWindowSample,true)
> as TitleWindow;
>                 PopUpManager.centerPopUp(**ventana);
> }
>
> parentApplication.**moduleComponentId.ventana.**variableName.text =3D=20
> "";
>
>