Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: Aaron Miller <amiller@learnatvivid.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Subject: RE: Why Spark? (was Re: s:Spacer (was Re: Missing Spark components))
Thread-Topic: Why Spark? (was Re: s:Spacer (was Re: Missing Spark
 components))
Thread-Index: AQHM+ADRUfrZwymuHEWh0tEziQrStpZXSYWA///wq1A=
Date: Fri, 2 Mar 2012 16:58:57 +0000
Message-ID: <E844DF84D5796A4397F2A8DE42242F120BA4D8F1@exchange.Vivid.local>
References: 
 <CAEFz_vuNuXuoJ3fMFmfGExutGy4T_8u9bUfBxQBkhsfHmdW9aw@mail.gmail.com>
 <E5A43F77-7AEA-4659-A77B-28A64644D4F0@tink.ws>
In-Reply-To: <E5A43F77-7AEA-4659-A77B-28A64644D4F0@tink.ws>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> One of the re-occurring discussions on this list has been the desire to b=
reak down components into smaller parts.
>=20
> The spark architecture goes some way to achieving this. Take scrolling, i=
f 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.
>=20
> Spark is about writing smaller parts that can be put together to make a w=
hole, instead of each component having all the=20
> 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.

-
Aaron