March 23, 2009 | In: cairngorm, design patterns, flex
Cairngorm++ Call me a junkie, that's fine, but this stuff works. I've said many times in the past that the whole purpose of using design patterns, code frameworks, and application architectures should be to reduce the code I write (as time progresses),...
March 18, 2009 | In: design patterns, flex, frameworks
Purpose My intended purpose for the AbstractCommand class in Cairngorm was two-fold: Implement a callback feature so that a view can specify another action to perform upon the successful completion of an event Make each Command class as lightweight...
March 18, 2009 | In: design patterns, flex, frameworks
Purpose My intended purpose for the AbstractEvent class in Cairngorm was three-fold: Reduce the number of files needed to manage business events by organizing Events into domains Implement a callback feature so that a view can specify another...
March 12, 2009 | In: design patterns, flex, frameworks
Purpose My intended purpose for the AbstractDelegate class in Cairngorm was two-fold: Reduce the number of files needed to manage business events by organizing Delegates into domains Make each domain Delegate class as lightweight as...
February 12, 2009 | In: AOP, coldfusion, coldspring, design patterns
Following up on my original post about ColdFusion performance hits on creating objects - it was suggested that I return an array of typed structures instead of an array of components. I already had a nice AOP class for each of these scenarios, so all I...