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)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: s:Spacer (was Re: Missing Spark components)
From: Arnoud Bos <arnoud@artim-interactive.nl>
In-Reply-To: 
 <CAEFz_vsikJg5mR98AUBPCDa+Sz1kLtuAOb_Vi7q6LR0HTEQF1A@mail.gmail.com>
Date: Thu, 1 Mar 2012 20:31:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <73F7A69D-C10E-4E65-935B-218E1E291DE8@artim-interactive.nl>
References: 
 <EB6F7A48D477254EAB8F675582F80CD7134972@DPSBS1.digitalprimates.local>
 <CB74F22D.3CFA2%aharui@adobe.com>
 <CAEFz_vtBkKZ1HYKtfKAo1Mh5ch=zMi4PvsP1bWuch6QQ0=eu+w@mail.gmail.com>
 <EB6F7A48D477254EAB8F675582F80CD7134D3C@DPSBS1.digitalprimates.local>
 <CAEFz_vujjvh=azSqkV3mL3yY+-L76jUmQn6EJK=KN=fPrWLPaQ@mail.gmail.com>
 <EB6F7A48D477254EAB8F675582F80CD7134DF7@DPSBS1.digitalprimates.local>
 <CAEFz_vsikJg5mR98AUBPCDa+Sz1kLtuAOb_Vi7q6LR0HTEQF1A@mail.gmail.com>
To: flex-dev@incubator.apache.org


>=20
> Fair enough, I was thinking about how inconsistent VGroup and HGroup =
were
> to a tighter lighter framework. Heh, it is what it is at this point.
>=20
> What if we put these convenience classes like s:TileList and
> s:LinkButton in another package, like spark.components.convenience, or =
some
> other name. We can then compile that into its own SWC and it can be an
> optional part of the framework you can choose, or choose not to, use.
>=20
> Either way, I think they have value. If they're rejected as a donation =
to
> the SDK I'll just throw them on GitHub.
>=20

Personally i like many components. If this bloats the SDK then i'm all =
for a split like
Flex and "Flex extended" or whatever. Of course people can make =
components like
SearchBox, AutoCompleteInputField, etc with the current available =
components, but
it's just more work. If there's a repo where those extensions are =
available i would be very happy.

For me it simply would speed up development. Choose the component that=20=

matches your needs closest and adapt in a minimal way. I use VGroup and =
HGroup
for example a lot. Shorter code, less typing and therefore easier to =
read. But i can understand
that here we want to focus on a rock solid core with a basic set of =
components.
But a central place for adding those convenience extensions would be =
great!

Met vriendelijke groet,

Arnoud Bos
Artim interactive
T +31 6 246 40 216
E arnoud@artim-interactive.nl