flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <carlos.rov...@codeoscopic.com>
Subject Re: [1/2] flex-asjs git commit: A temp way to get Application reference. Don’t like this solution and at minimum we should have a FlexGlobals.topLevelApplication or something like that
Date Thu, 19 Jan 2017 17:42:44 GMT
Hi Alex,

thanks for the code example. I'll return to it if is necessary, in the
meanwhile I'll left the mdl:Application since is how other was doing and in
MDL case we would not get rid of the mdl:Namespace, so it seems ok to to
have a mdl:Application.


2017-01-19 17:00 GMT+01:00 Alex Harui <aharui@adobe.com>:

> On 1/19/17, 12:40 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
> wrote:
> >Good suggestion Piotr,
> >
> >Maybe create a Application subclass only to get a static var is not the
> >best way. In the other hand is the way is implemented in other libs like
> >CreateJS, Express...
> >and could lead to be more MDL Specific... Right now both ways are ok for
> >me.
> IMO, the bead you are looking for could be coded something like this:
> public class GlobalApplicationReference implements Ibead
> {
>     public static var application:Application;
>     public function set strand(value:IStrand):void
>     {
>         application = value as Application;
>     }
> }
> The question is, what should the type of the application variable be?  If
> it is ApplicationBase, it can be used in many places, but it won't have
> the "initialView" property.  If you need to access variables declared on
> your specific MXML app, then you would need to cast it, or create a custom
> version of such a bead.
> Of course, I could be wrong...
> -Alex


Carlos Rovira
Director General
M: +34 607 22 60 05

Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message