well - as FlexSDK is mostly "component kit", it would be IMHO beneficial, to have some optional packages, that could host these "extra" kind of components. (like data visualization is separate)
Your ideas, comments? On Thu, Mar 1, 2012 at 6:22 PM, Alex Harui <aha...@adobe.com> wrote: > > > > On 3/1/12 8:55 AM, "Antonio Hernández de la Rosa" <i...@knstudios.es> > wrote: > > > This is not a relevant / core functionality for flex sdk > > > I'm all for giving related code a home if it needs one. > > > El 01/03/2012, a las 17:51, andrei apostolache escribió: > > > >> Even if it might look like a interesting tool for enterprise > development, > >> having it in the Flex SDK will just make the SDK size bigger. > The SDK release doesn't have to include this code. > > >> > >> On Thu, Mar 1, 2012 at 4:34 PM, Rafael Santos > >> <rsan...@spectacompany.com.br>wrote: > >> > >>> What do think about integrating FlexCover in the Apache Flex code base? > >>> http://code.google.com/p/flexcover/ > >>> > >>> FlexCover is a great tool for test coverage, but as for today we need > to > >>> change Flex source and recompile to make it work. > >>> Regarding Enterprise systems it is a powerful tool. > >>> > It is pretty clear to me that we can't just choose to integrate other code > into the Apache Flex project. > > In general, code is "owned" by some entity and has to be donated by that > entity. We can't just copy code from any other open-source entity into > Apache Flex. > > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
