My opinion is that Apache Flex should be only what Flex was in Adobe's era. A simple SDK that contains only the necessary code to create an RIA. FlexUnit, FlexCover are already projects set on google code. BlazeDS will be somewhere in the future donated by Adobe as different project. And I don't see why I will need a MVC framework directly implemented in Flex SDK, when sometime for a simple application you may not need the advantages that a framework may offer. Each project should have it's own purpose, because anyone who uses Flex may not necessarily use FlexUnit, or BlazeDS. We already have Apache Flex (as core) and extensions (each project with his own purpose).
On Thu, Mar 1, 2012 at 4:59 PM, João Fernandes < joaopedromartinsfernan...@gmail.com> wrote: > I wonder if the Apache Flex couldn't be splitted in core and extensions? > > In the core we could have what we have now as the SDK + compiler, what is > required to get the job done (primary project target) and extensions could > be small projects that could be associated as enhancements of the project, > like FlexUnit, FlexCover, BlazeDS, etc, but aren't considered a requirement > to have a flex app running. > > Just my 2 cents. > > João Fernandes >
