|
Hi Ben, I personally do not like circular
dependencies. In your case the ViewStack would know about its children and the
children also know about the ViewStack. If you later decide to hang your
children in a different container you will probably have to rewrite some code
in the children. It’s a tight integration. To communicate ‘downwards’
(from ViewStack to children) I use interfaces, which actually means that I can
call the methods of the children directly from the ViewStack. To communicate ‘upwards’ (from
the child to a ‘container’ which could be the ViewStack) I use
event handling. So, the container registers himself as listener for a child
custom event; once the child encounters a situation where it wishes to
communicate with the container, it fires the event and the container catches
it. HTH, Franck From:
[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of ben.clinkinbeard I have a ViewStack whose child elements each contain a
graph. I would -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com YAHOO! GROUPS LINKS
__,_._,___ |
- RE: [flexcoders] Best way to reference items in a parent ... Franck de Bruijn
- Re: [flexcoders] Best way to reference items in a pa... Sergey Kovalyov
- [flexcoders] Re: Best way to reference items in ... ben.clinkinbeard
- Re: [flexcoders] Re: Best way to reference i... Sergey Kovalyov
- RE: [flexcoders] Re: Best way to reference i... Franck de Bruijn
- RE: [flexcoders] Re: Best way to referen... Gordon Smith
- Re: [flexcoders] Re: Best way to re... Sergey Kovalyov
- RE: [flexcoders] Re: Best way to reference i... Gordon Smith
- [flexcoders] Re: Best way to reference i... ben.clinkinbeard

