Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of aharui@adobe.com designates
 64.18.1.25 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Thu, 5 Jan 2012 15:12:26 -0800
Subject: Re: Flex modularity through composition and interfaces (Dependency
 Injection)
Thread-Topic: Flex modularity through composition and interfaces (Dependency
 Injection)
Thread-Index: AczL83e6qFDExub0RTClVkhXTUHpZgADAU0U
Message-ID: <CB2B6E5A.39324%aharui@adobe.com>
In-Reply-To: <F0C99076-B966-45B4-BB67-EA4B626EB2B9@tink.ws>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 1/5/12 1:45 PM, "Tink" <flex@tink.ws> wrote:


>=20
> Couldn't we inject at compile time.As the compiler does with other
> metadata it could find injection points, and using Singletons hidden
> behind the scenes to give the correct values to the correct properties
> in the generated code? This would remove the current bottlenecks we
> have with DI.
>=20
> Tink
>=20
You can inject at compile time unless you can only determine what to inject
at runtime.  Like locales, automated testing engines, themes.

There are use cases for both.  A good DI implementation will support both.
I have a further goal that compile-time DI would be "legal ActionScript" in
that you could output the AS that is going to run. (Sort of like the
-keep-generated-actionscript option today).  That would make it a whole lot
easier to debug.

--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui