Some architectural pattern is going to be necessary if the app is of any size and has a team working on it. Otherwise, each developer will solve their problems in their own way and can lead to chaos. You can formulate the architectural pattern yourself or use a published framework. As you said, using a published framework in some ways might make it easier to bring developers on board. Frameworks are intended to be implementations of architectural patterns - the framework choice IMO is based upon what gives you the best balance of freedom to solve your problems as you choose, with ways of solving problems without having to reinvent the wheel all the time.
I've used Cairngorm a lot in the past, but I've kind of soured on it - doesn't solve enough problems, IMO. It is NOT module-friendly; in particular the ModelLocator singleton does not lend itself to unloading modules. I'm liking the direction that Cairngorm 3 is taking - it is less a proscriptive framework than a collection of best practices and libraries you can choose to use or not. It does use the capabilities of Parsley for wiring the application together and so far in my projects, it works great. -----Original Message----- From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of tntomek Sent: Wednesday, March 24, 2010 5:29 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Framework Choice Thumbs up for just using Flex SDK as the framework. Make good use of custom business interfaces and ensure all developers develop controls within some container vs Application/Module (leave the loading of their actual code to someone who really understands Flex). Also take the hit and wrap most Flex controls with your own, it will come in handy in future. -Tomek (http://tomek.me) --- In flexcoders@yahoogroups.com, Jake Churchill <reyna...@...> wrote: > > I have been tasked with architecting a large application for a company a > friend of mine works at. I will also do some of the coding and act as a > mentor, teaching people on staff the ins and outs of Flex. > > In the past, I've always used Cairngorm and Cairngorm w/ UM Extensions for a > framework. I wrote a very basic app w/ Mate once just to learn it and I > didn't really like it. So, my question to everyone here is what Framework > would you chose? Keep in mind, the people I'll be working with are > relatively new to flex and the application is going to end up being quite > large. Down the road it will likely have an AIR counterpart. We might use > modules but for now I'm staying away from that because it adds another layer > of complexity that in the initial stages is not needed. > > My thoughts on this are that Cairngorm would be easier to learn for them and > they had talked about brining more people on in the future for this > project. If that's the case, it would likely be easier to find people > familiar with Cairngorm than some of the alternatives. But, I don't want to > rule out any of the alternatives if they might actually be a better choice. > > > Opinions please. > > Thanks! > > -Jake Churchill > ------------------------------------ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Alternative FAQ location: https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links
