[gwt-contrib] Re: Fixes issue 6653: Activity interface should use the new EventBus (issue1786804)

2012-07-25 Thread manuel . carrasco . m
A bit of discipline maybe, but no pain at all (not for me at least). You are right s/pain/discipline/. When you use gin for places and activities you have to be aware of this circumstance to avoid multiple instances of the event bus, so you have to write a bit more code and replace

[gwt-contrib] Re: Fixes issue 6653: Activity interface should use the new EventBus (issue1786804)

2012-07-25 Thread t . broyer
On 2012/07/25 10:01:17, manolo.carrasco wrote: A bit of discipline maybe, but no pain at all (not for me at least). You are right s/pain/discipline/. When you use gin for places and activities you have to be aware of this circumstance to avoid multiple instances of the event bus, so

[gwt-contrib] Re: Fixes issue 6653: Activity interface should use the new EventBus (issue1786804)

2012-07-23 Thread manuel . carrasco . m
Agree, we should not introduce breaking changes. Actually people were forced in 2.4 to use both versions (gwt and bindering) unless they use deprecated methods (Places), and using mvp+gin is a pain. I have not introduced more changes like you suggest to avoid more breaks and just to fix the

[gwt-contrib] Re: Fixes issue 6653: Activity interface should use the new EventBus (issue1786804)

2012-07-20 Thread t . broyer
If we go that road, we should probably remove c.g.g.event.shared.EventBus completely. There's no reason to force people to move to the web.bindery version in some places (activities) but not others. This is something the Steering Committee should discuss (along with removing other deprecated