flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "carlos.velasco.blanco" <carlos.velasco.bla...@gmail.com>
Subject RE: Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
Date Tue, 28 May 2013 20:50:12 GMT
I do not agree to you. There are a lot of ways to approach an application development, some
may be of your liking others will not be. But there is no need to force one of them as the
Flex sdk one.

I would rather prefer to maintain all those as separate libraries for anyone to choose the
one he prefers.


Enviado desde Samsung tabletOmPrakash Muppirala <bigosmallm@gmail.com> escribió:I like
the donation of the Swiz framework.  I use both swiz(for work) and
parsley(personal projects) and I am ambivalent at this point.  What I would
really like to see the best part of these frameworks (and maeby others like
spring-actionscript, robotlegs, etc.) integrated into Flex.

I am talking about things like an IOC container, DI, autowiring,
message/event handling etc.

The way I see it, these frameworks came about to fill a void in the Flex
framework.  Now that we are Apache, there is nothing stopping us from
baking these paradigms into the framework, thereby making these frameworks


On Tue, May 28, 2013 at 10:25 AM, Greg Reddin <gredbug@gmail.com> wrote:

> On Tue, May 28, 2013 at 11:18 AM, Alex Harui <aharui@adobe.com> wrote:
> >
> > Greg, do you think donations like these need to have a goal of being
> > integrated with Apache Flex or becoming its own project?  Personally, I'd
> > be ok with Apache Flex being a warehouse of all kinds of Flex-related
> code
> > even if there is no active development for it.
> There's a couple of things to consider here:
> 1) The board does not favor "umbrella" projects. Jakarta was an umbrella
> project and it contained (at one time) Struts, Tomcat, Commons, JMeter, and
> a whole bunch of Java-related projects. It became clear that the Jakarta
> community was too fragmented to get consensus so it spun off all those
> projects into TLPs. That could easily start to happen here.
> 2) This mailing list is already too high-traffic to follow. Practically, we
> could probably already split up the Flex project into multiple projects. It
> seems to me that folks are starting to gel around different efforts, like
> getting new releases of the SDK, vs. compilers, etc. It could be that we
> need to form new PMCs or it could be that we just need to enact
> sub-projects. But we have to be careful with sub-projects to avoid point 1
> above.
> It's hard to know where the breaking point is. Probably it has to do with
> whether the community is having a hard time pushing out releases or just
> whether it "feels" fragmented. I'm not proposing that we break up now, but
> we should probably be thinking about whether the Falcon project, for
> example, has its own distinct community from the SDK.
> Greg
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message