.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Michael Labriola
Sent: Friday, June 27, 2008 8:20 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: One custom component referring to another
Jason,
In an ideal world, component A would throw
Subject: RE: [flexcoders] Re: One custom component referring to another
My vote would be for changes in A to affect a central model. B would
watch the model change and reflect those changes. Everything B needs
from A would be reflected in the model. That's pretty much what Mike
said, except I'm
that makes a difference.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Nimer
Sent: Friday, June 27, 2008 10:36 AM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Re: One custom component referring to another
Be careful here
3 matches
Mail list logo
