>
> 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.
>
> 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.
>
> Either way, I think they have value. If they're rejected as a donation to
> the SDK I'll just throw them on GitHub.
>
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
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