Quote from Alex in another thread, "...not everything belongs in the Flex project. For example, we have already discussed that application frameworks probably don't belong in the Flex project."
I don't think the main Flex SDK should have every component in it but in today's world, developers have a wide range of hip new contemporary components being described in their projects. I think we should consider the option of having an official or "blessed" subsidiary SWC of components, classes and skins to address common needs. These could even be possible candidates for the main SDK. Something like the AS3Core lib. One thing I've liked about the Flex SDK is that the components do what they should but not more (some may disagree but follow me here). The Spark List, for example, doesn't have every layout built in but it uses the Strategy pattern to define a family of algorithms<http://en.wikipedia.org/wiki/Algorithm>, encapsulates each one, and makes the layouts interchangeable (- guess what type of book I was reading over the weekend - I'll give you a hint, it begins with design patterns). For example, an auto completing search field is almost standard now but there is nothing like this in the standard Flex component set. And to rub it in there's not just one kind. In iTunes there are two types of search inputs. In the iTunes *Store* the search has a magnifying glass icon on the left (that does nothing), the prompt "Search Store" and an icon constrained to the right edge that's visible when there is text in the search field. As you type a drop down appears that shows a list of exact matches (Google search shows possible matches). By default the drop down shows nothing. In the iTunes *library* the search has a magnifying glass icon on the left (that lets you choose to filter by artist, album, name or all), the prompt "Search" and an icon constrained to the right edge that's visible when there is text in the search field. As you type the music list is filtered. By default the music list shows everything. I know every permutation of a TextInput and Button component or TextInput and Button skin doesn't belong in the main component set or a sub component set. Some of what's needed are just examples. For example, I really like this, http://www.sencha.com/products/extjs/examples/ and http://jqueryui.com/demos/accordion/ (notice the options on the right as well).
