Rogelio, I am not saying that the Flex SDK should have a lib for DI
(like Swiz or Mate). What I would like was to be able to configure the
mappings between the interfaces and objects, so I could easily replace
TabNavigator1 with TabNavigator2 touching in code as less as possible.
Part of the DI could even be handled at compiler level.
A similar approach was proposed at the Flex summit by Mike Labriola.
João Saleiro
On 04-01-2012 21:17, Rogelio Castillo Aqueveque wrote:
I agree on modularity, but I reckon dependency injection is a totally different
thing which has lots of very good libs out there... not sure if that should be
part of the SDK.
I believe that the focus should be on splitting the SDK into several
modules/libs, then think on interface design.
R
---
Rogelio Castillo Aqueveque
roge...@rogeliocastillo.com
On 4/01/2012, at 6:11 PM, João Saleiro wrote:
+1
I agree with reducing strong-coupled dependencies as the first priority.
I would also complement the use of interfaces with:
- using dependency injection when possible
- splitting the SDK into several libraries
- support and advocate the use of Maven for managing dependencies (or something
similar)
João Saleiro
On 04-01-2012 21:03, Michael Schmalle wrote:
Continuing the thread from "Committer duties and information"
about setting interface priority to #1 in the future development fo Flex.
Mike
