On Tue, Aug 4, 2009 at 4:24 PM, Dave Watts<dwa...@figleaf.com> wrote: >> The real point is that to call public methods, you have to know about the >> object whose method you want to call and you need to know about the method >> itself. When you broadcast an event, you don't need to know whose listening, >> your just indicating that something meaningful has happenned and perhaps >> also passing data that is meaningful. > > This is really the key. If you don't do this, you're baking > dependencies into your application.
And also potentially compilation dependencies, if, for example, you later decide to split your app into modules then you'd have to include the target of the method call across both the relevant modules (or do something with interfaces instead). Ian _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
