Hi fowleryj,
Why have the same problem here. And one solution for use a diferents commands you have to use diferentes names for each application, beacause the FrontController add a listener in a single "static var eventBroadcaster. But if your application is realy big I recommend to you rewrite some classes in the cairngorm framework. For example you can rewrite te EventBroadcaster and FrontController classes creating a FrontControllerLocator. This FrontControllerLocator can be implemented like the ViewLocator. You set IDs for each controller and use this IDs to call the EventBroadcaster. Did you understood? I did the same with the services creating a ServiceHelper and a ServiceLocator, and this can help you to implements the FrontControllerLocator.
I hope that can solve your problems.
Let me know if it`s works and sorry for my poor english.
Hugs.
On 1/16/06, fowleryj <[EMAIL PROTECTED]> wrote:
We have been developing a fairly large application using Flex 1.5 and
the Cairngorm framework, and have recently run across what could be a
large roadblock. Our application has many sub-applications the user
can choose to run from a menu in the main application. To implement
this we are dynamically creating the children the user selects in a
view stack. All of these sub-applications rely on a particular search
screen that allows the user to find a particular person in our
database. The problem is that the sub-applications are bound to the
selection the user makes in the search screen, and are all reacting to
the same events (which are broadcast from the search screen). We would
like the search screens to function as separate instances. For
example, if I broadcast a change event from the search screen, all of
the open sub-applications will catch the event and change all of their
displayed information to reflect that of the most recently selected
person. Our problem appears to stem from the way the EventBroadcaster
and FrontController are designed. All events are broadcast in the same
EventBroadcaster using the getInstance() method, thus everything is
listening for everything.
Can anyone who is familiar with the intricacies of Cairngorm propose a
way to deal with this problem? We would like to be able to return the
information about the selected person only to the sub-application that
invoked the search screen. Perhaps it is not possible to do this using
Cairngorm, and we would appreciate knowing that, too.
If anyone has a different/better solution, we'd love to hear about it.
Thanks in advance.
--
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
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
--
Bruno Gustavo Martins
Mobile: (55)(11)9585-9587
[EMAIL PROTECTED]
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
| Web site design development | Computer software development | Software design and development |
| Macromedia flex | Software development best practice |
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
ServiceHelper.as
Description: Binary data
ServiceLocator.as
Description: Binary data
