incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Harfleet <dharfl...@yahoo.com>
Subject Re: Why Spark? (was Re: s:Spacer (was Re: Missing Spark components))
Date Fri, 02 Mar 2012 18:21:14 GMT
+1 on the DI



________________________________
 From: Roland Zwaga <roland@stackandheap.com>
To: flex-dev@incubator.apache.org 
Sent: Friday, 2 March 2012, 17:46
Subject: Re: Why Spark? (was Re: s:Spacer (was Re: Missing Spark components))
 
>
> > One of the re-occurring discussions on this list has been the desire to
> break down components into smaller parts.
> >
> > The spark architecture goes some way to achieving this. Take scrolling,
> if you want it you wrap you group on a Scroller
> > and off you go. Same for layouts. In this way spark is far more flexible
> and superior to mx along with its skinning model.
> >
> > Spark is about writing smaller parts that can be put together to make a
> whole, instead of each component having all the
> > functionality for every scenario baked in.
> >
> > Tink
>
> I believe this paradigm is referred to as Aspect Oriented Programming
> (AOP), and IMHO, should be the way forward for Flex.
>

Hmmm, I think the right term would be composition-based design. In most
cases dependency injection would be the pattern to
use to configure the compositions.
Sorry for being a smart-ass by the way... :)

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