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 >
