Om is pointing my main concern with Swiz donation. The main point here is that Swiz 2.0.0 Beta has many good and beautiful ideas about AOP that are very new to web client technologies. Something that people are using from long time in java could be first citizen in Flex making an huge difference. things like DI, IOC, etc... are the kind of things that would make sum positive points in a technology decision for a company.
For me is not about choose Swiz, RobotLegs, Parsley, PureMVC, Spring ActionScript or whatever, all are great frameworks totaly decouple from main flex-sdk. The opportunity here is learn from Chris AOP Swiz version and take it to the production stage (this will need people like Gordon and others since it implies compile time weaving as Roland exposed in his comment. For me Swiz should has the same opportunity like flexunit or other components donation, while it's not required to have in a project an continue as an optional library. Other frameworks can as walk the same route if people are interested. As Alex said, we should not expect too much mail traffic since the main swiz mailing list doesn't have it. Remember the main benefit here is AOP - compile time weaving and all advanced development techniques that Flex are designed to reach while other technologies nowadays does not even know that exist. 2013/5/28 carlos.velasco.blanco <carlos.velasco.bla...@gmail.com> > 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. > > Carlos. > > > > > Enviado desde Samsung tabletOmPrakash Muppirala <bigosma...@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 > obsolete. > > Thanks, > Om > > On Tue, May 28, 2013 at 10:25 AM, Greg Reddin <gred...@gmail.com> wrote: > > > On Tue, May 28, 2013 at 11:18 AM, Alex Harui <aha...@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 > > > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
