Thanks Manish, I also found some documentation (updated) from Adobe. This wasn't part of the general doc set. I have since learned to keep an eye on the Flex Doc Team blog.
The method I found from the doc was the parentApplication property. It pretty much gives the module a handle to the parent object that called it. In my case my framework application. I could run a method from there to modify the viewstack during a method I call to handle a change (itemClick). Your answer gives another way to do this as well..thanks again Rodney --- In flexcoders@yahoogroups.com, "rodneyjlucas" <[EMAIL PROTECTED]> wrote: > > > I am new to modules but think the idea is great. However, I am trying > to modularize a prototype and get stuck. I would like to have a > simple framework Application with modular components for each major > piece of the application (banner, footer, left hand navigation, main > content..etc). > > The problem occurs when I have a need for module to module or module > to Application communication. For example if I have a > mx:ToggleButtonBar in the banner module. When a change event is fired > I want the viewstack to change the child it is showing and to handle > loading/unload other modules. > > What is the best way to handle this? Bubble events somehow? Pass the > banner/togglebuttonbar a handle to the application's viewstack? Other > ideas. Obviously part of the trick is to keep things loosely coupled > and reusable. > > Rodney >
