That's actually the example I've been using (I thought it was 2006, not 2007), but it's 2 years old, and my question still holds. Is this the best practice or is some other method being used with Cairngorm?
--- In [email protected], claudiu ursica <the_bran...@...> wrote: > > http://weblogs.macromedia.com/auhlmann/archives/2007/02/creating_a_popu.html#more > > This should give you some directions... > > Claudiu > > > > > ________________________________ > From: lampei <lam...@...> > To: [email protected] > Sent: Saturday, January 10, 2009 1:34:25 AM > Subject: [flexcoders] Cairngorm and ChangeWatcher > > > I have begun tinkering around with various frameworks and thought I > would start with Cairngorm. I am refactoring a small application to > use Cairngorm, but ran into a snag. All of the examples I found just > bound an item in the view to a property of the ModelLocator, and thus > automagically updated the value when the property of the ModelLocator > changed. However, I had one item that is waiting for a response from > a service, and needed to respond to that change (such as an error > message), rather than just display the updated data that is returned. > > I found an example that uses the ChangeWatcher class to watch the > property on the ModelLocator. This seemed to work fine, but I was > wondering if this is still best practice, as the example I found was > from 2006. > > Thanks. >
