Even if you organize your code to some sort of internally formulated organization, you're already kind of using a framework - of your own creation.
The disadvantage to that IMO, as soon as you start writing one you now become responsible for documenting your particular approach and communicating it to developers who might also work on your project. If your project needs to scale, using a published framework gives you the ability to find resources who also know the framework, and gets them up to speed more quickly. I've been on projects (otherwise known as "nightmares") where the previous developer used no framework, and didn't document what they did. I remember one in particular where it was stated that it might take 6 months to get up to speed on the way the app was built. That's just a waste of time and money. All that said, I've used Cairngorm for years and the original version, while workable, is taking a back seat to IOC frameworks. I'm using Cairngorm 3 and Parsley and I really like the development model. Jeff ________________________________ From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Jake Churchill Sent: Wednesday, March 24, 2010 11:39 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Framework Choice I have never written an app using modules. I understand the logic behind it, I've just never had the need. Is there anything regarding modules that I should know before starting? On Wed, Mar 24, 2010 at 10:27 AM, valdhor <valdhorli...@embarqmail.com<mailto:valdhorli...@embarqmail.com>> wrote: I have an extremely large enterprise application (24 modules and counting) that does not use any framework. If you can discipline yourself in the way you organize your code, I don't really see the need for a framework. It just adds complexity in my view. I would recommend starting with modules if you see the need may be coming later on. I started with a monolithic app while I was learning Flex and had to change over to modules six months in. That was no fun I can tell you. Now that each part is in a module it makes it much easier for other team members to modify the code. It is also a lot easier to follow the logic. I would also recommend a versioning system - we use Subversion. --- In flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.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 >
