Re: One v.s N EventBus

2010-08-01 Thread ww
I have the same problem. I am now using the mvp framework of GWT 2.1.0 m2. My application has several modules, and in each module, it may have different layout. Hence I have multiple level of Activity and in each module, I have an ActivityManager and ActivityMapper to create an appropriate

Re: One v.s N EventBus

2010-07-31 Thread Sebastian Hoß
I've been using multiple EventBus instances together with Gin/Guice and named annotations. So for example each view that needs to communicate in some way with my REST server is attached to the @Server HandlerManager. That way each component can have multiple communication channels open and it is

Re: One v.s N EventBus

2010-07-31 Thread Gal Dolber
I am using one event bus across the whole app. The definition of eventbus implies that, but who knows, I've never though about having multiple eventbuses. Maybe you can find some benefit from doing that 2010/7/31 Sebastian Hoß m...@shoss.de I've been using multiple EventBus instances together

One v.s N EventBus

2010-07-30 Thread Dean S. Jones
Looking at finishing up an idea, and I have come across a thought in MVP: Global v.s a multiple/hierarchy of view/presenter EventBus's, and wondered if anyone had explored this avenue. The basics are there is the global EventBus, as is typical now, and a local EventBus for actions in the current