>> It is not an issue at all if they more or less couldn't work
>>without something doing the job of the other and few if any
replacement
>>options.
That's a strange point of view, I would love to see a good example of
that. If you've got a system designed that way, then you've got bigger
probl
sage-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Latcho
Sent: Wednesday, November 18, 2009 9:25 AM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] one class listening for another
classesdispatchedevent
If like you
Merrill, Jason wrote:
If that makes it so there would be too much code in one
class and the tasks so different, then they should be in separate
classes with events dispatched and listened to.
So you are basically saying that every single time you want to use
something in another class, you sh
3 matches
Mail list logo
