Re: SimpleEventBus : why such a non-predictive behavior implementation ?

2011-08-05 Thread Hilco Wijbenga
On 27 July 2011 08:48, david.herv...@gmail.com wrote: > Even if multithreaded my implementation is (normally)  done. > I really don't know why they have used such a mecanism... > There may be a use case I'm missing > > On 27 juil, 17:28, Sixin Zhang wrote: >> i feel alike, all new registrations a

Re: SimpleEventBus : why such a non-predictive behavior implementation ?

2011-07-27 Thread david.herv...@gmail.com
Even if multithreaded my implementation is (normally) done. I really don't know why they have used such a mecanism... There may be a use case I'm missing On 27 juil, 17:28, Sixin Zhang wrote: > i feel alike, all new registrations are delayed until the end of > firing (depth=0) .. so nothing will

Re: SimpleEventBus : why such a non-predictive behavior implementation ?

2011-07-27 Thread Sixin Zhang
i feel alike, all new registrations are delayed until the end of firing (depth=0) .. so nothing will happen if firing those new events before the end .. depth behaves like a lock for concurrency, but not really necessary for single-thread JavaScript .. On Jul 27, 9:58 am, "david.herv...@gmail.com

Re: SimpleEventBus : why such a non-predictive behavior implementation ?

2011-07-27 Thread david.herv...@gmail.com
thanks, committed patch here : http://gwt-code-reviews.appspot.com/1500804/ On 26 juil, 22:43, Gal Dolber wrote: > I am, but your post is too long to read :) > > For what I understood, I had a similar problem, and I solved it > encapsulating the "create widgetC" in a DeferredCommand (for your exa

Re: SimpleEventBus : why such a non-predictive behavior implementation ?

2011-07-26 Thread Gal Dolber
I am, but your post is too long to read :) For what I understood, I had a similar problem, and I solved it encapsulating the "create widgetC" in a DeferredCommand (for your example). Its really hard for me to understand the modification you purpose, maybe someone from google could see it. But I t

Re: SimpleEventBus : why such a non-predictive behavior implementation ?

2011-07-26 Thread david.herv...@gmail.com
No body concerned ? On 25 juil, 10:50, "david.herv...@gmail.com" wrote: > Hi, > > I'm facing a problem when using the simple implementation of the > EventBus. > > // register widget B to be notified when WidgetA trigger an event > register handler of WidgetB on WidgetA.EventType > > // dispatch (

SimpleEventBus : why such a non-predictive behavior implementation ?

2011-07-25 Thread david.herv...@gmail.com
Hi, I'm facing a problem when using the simple implementation of the EventBus. // register widget B to be notified when WidgetA trigger an event register handler of WidgetB on WidgetA.EventType // dispatch (firingDepth is incremented) WidgetA.fireEvent // my widget is really called !!! that's g