After joining UM and working with this I found the most kewlest slick part I like is the callback support in Cairngorm events. Uber sweet at helping you handle results and not bloating out your ModelLocator instances. Also, the sweet hook that easily sets up using dispatchEvent no matter if its a Cairngorm event or not. Concerning modules, err not the most entertaining subject in my book so I will not speak too much about it, but yeah, no example exists yet using the extensions for them TIKO, but we do use these day-to-day. The controllers added enable your modules to be part of the eco-system yet separate and pluggable. Consider a app that has module A and B loaded at run time. How does say a gesture in module B throw a Cairngorm event that module A reacts to? The modified controllers enable this. Peruse the inline comments in the com.universalmind.cairngorm.control package for some info.
DK On Fri, Apr 11, 2008 at 8:52 AM, ben.clinkinbeard < [EMAIL PROTECTED]> wrote: > Well, they would all point to the same Cairngorm/UM Cairngorm SWC > (that lives in the library project) but yes, you would have a model, > services, etc in each project. The resulting swf is built using > -link-report/-load-externs to optimize the inclusion of classes though > so you don't have unnecessary bloat. > > Having each module be self-contained (as much as a module can be) > isn't really possible if its relying on a base app for model, > services, etc. > > > Ben > > --- In [email protected] <flexcoders%40yahoogroups.com>, João > <[EMAIL PROTECTED]> wrote: > > > > Ben, > > > > but that would mean that I would have a lot of code duplicated for > > each module, right? In this case, the cairngorm source (or, at least, > > the singletons). Am I right? > > It doesn't seem a good practice to me... what do you think? > > > > João Saleiro > > > > > -- Douglas Knudsen http://www.cubicleman.com this is my signature, like it?
