I'm currently getting ready to begin a long journey in FLEX development for a bunch of systems here at work.
I've been reading up as much as i can on cairngorm and trying to figure out its value in FLEX and whether I should adopt it or plough on without it. So far I've watched Robin Hilliards Breeze preso, sampled some example cairngorm applications from both I2 guys and Robin. I've outlined some summary notes below, and would absolutely love it if someone here could correct them or expand on them to enable me to understand the cairngorm luv :) Heres what I've gathered so far: - formalised approach to command subscriptions, in that a controller is established which registers itself against commands for both Views and Models - but in a relatively simplified syntax (ie addCommand) - Seperating ViewPods from logic via "ViewHelpers". It appears that the framework allows a developer to add "behaviours" or "logic" to a view but in a way that its not coupled with that said view (ie i assume you could add a ViewHelper to other ViewPods? - yet all feed off the one instance/codebase). - Templated Command Objects : it seems to me that the whole Command concept has established a base template to work from, so that onResult, onFault and execute are automatically invoked per command? - then the developer can just fill in the blanks based on the event type? - ViewLocator - kind of reminds me of DHTML's document.getElementById() in that it appears each ViewHelper registers itself within cairngorm and the ViewLocator simply provides a dynamic bridge between the actual view and the object requesting its location? or something like that? Thats my note so far, and again I do apologise if its inaccurate in anyway but i'm trying to wrap my headspace into how it implements MVC and why its used. If this is Offtopic I do apologise but *poke* *prod* a "Getting Started Guide" would of been great ;) heheheheh -- Regards, Scott Barnes http://www.mossyblog.com
