Cairngorm! we love it
February 4th, 2008
I think every flex developer has the same doubt: Should I move my application to Cairngorm? Should I start using Cairngorm? Should I learn how to use Cairngorm? The answer for all this questions and any other questions that you can imagine is YES.
If you have never heard about Design Patterns, this could be a really good moment to start thinking and looking for some information about it. In fact, I think you cannot be a good developer if you don’t know Design Patterns in a strong way.
If you still don’t know what are Design patterns, have a look at this:
http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29
http://en.wikipedia.org/wiki/Architectural_pattern_%28software_engineering%29
In case you feel familiar with all this terms, and you still don’t know Cairngorm, it should be now a good moment to have a look at this:
It’s a good repository, probably the best one, about Cairngorm. There you can find examples, documentation, tutorials, diagrams and everything related with Cairngorm.
Cairngorm provides you an easy, scalable, and reusable way to develop your applications, allowing your application to grow and grow without worrying about the future. If other developers join you on the development of your application, and they know Cairngorm, it will be extremely easy to have them working at their best straight away. If you don’t use Cairngorm, probably your poor new developer will be trying for weeks to understand your roller coaster application that you developed.
I insist: When you start with Cairngorm you will feel a little bit …..weird? A lot of stuff to learn, a lot of models, controllers, event dispatchers and delegates Business, but when you get inside it completely, you will never wanted to leave it.
Long live Cairngorm.
Check out a realy cool diagram explaining it here
and the application it talks of here
February 4th, 2008 at 9:43 pm
I’m happy to see you finally decided to go for it!!
Well done Emak Mafu team!!
March 2nd, 2008 at 7:13 pm
Lets say someone hooks up your FrontController, and you have lots of different UIComponents that dispatch a particular CairngormEvent it listens to. You then find that this CairngormEvent is getting fired too often (or at least not when it should). How do you then go about finding out why (i.e. finding out which UIComponent’s are dispatching the particular event). You now have to doing a ‘find’ in your code which isn’t great.
Cairngorm is great if you want to obfuscate your code for future developers.
Take the best parts of Cairngorm and build a framework around your projects, don’t build you projects around Cairngorm.