Comments for webspin.be

Comment on Building a GWT 1.6 application: Managing events with an eventBus by Rob

Rob — Tue, 03 Aug 2010 12:07:22 +0000

Having recently started to learn how to use GWT and after looking at the event bus presentation I still had a few questions but after reading your article I feel I now know how this is done.

Thank you for this great help.

Comment on Building a GWT 1.6 application: Managing events with an eventBus by Eddie Chan

Eddie Chan — Mon, 14 Sep 2009 11:19:22 +0000

This was the clearest explanation of the EventBus I’ve seen. Well done and thank you!

Comment on GWT 1.6 MVP and testing, part 1 by Francesco Pasqualini

Francesco Pasqualini — Wed, 02 Sep 2009 05:18:13 +0000

…I try again…

I correct my previous post, here is the possible refinement (remove lastClickHandler and MockClickEvent):

change

—
class MockHasClickHandlers implements HasClickHandlers {
public HandlerRegistration addClickHandler(ClickHandler handler) {
lastClickHandler = handler;
return new HandlerRegistration() {
public void removeHandler() { }
};
}
public void fireEvent(GwtEvent event) { }
}
–

–
class MockHasClickHandlers extends Widget implements HasClickHandlers){

public HandlerRegistration addClickHandler(ClickHandler handler) {
return addHandler(handler, ClickEvent.TYPE);
}
}
–

and change

mockWidget.save.lastClickHandler.onClick(new ClickEvent());

mockWidget.save.fireEvent(new ClickEvent());

—
every custom widget extends Widget and so inerits the magical fireEvent method

Comment on GWT 1.6 MVP and testing, part 1 by Francesco Pasqualini

Francesco Pasqualini — Wed, 02 Sep 2009 05:15:37 +0000

I correct my previous post, here is the possible refinement (remove lastClickHandler and MockClickEvent):

change

<<
class MockHasClickHandlers implements HasClickHandlers {
public HandlerRegistration addClickHandler(ClickHandler handler) {
lastClickHandler = handler;
return new HandlerRegistration() {
public void removeHandler() { }
};
}
public void fireEvent(GwtEvent event) { }
}
>>

and change

mockWidget.save.lastClickHandler.onClick(new ClickEvent());

mockWidget.save.fireEvent(new ClickEvent());

—
every custom widget extends Widget and so inerits the magical fireEvent method

Comment on GWT 1.6 MVP and testing, part 1 by Francesco Pasqualini

Francesco Pasqualini — Wed, 02 Sep 2009 04:37:47 +0000

Interesting !

I suggest a possible refinement:

change

“public class MockAddRowWidget implements AddRowWidgetInterface”

“public class MockAddRowWidget extends Widget implements AddRowWidgetInterface”

and then change

“mockWidget.save.lastClickHandler.onClick(new MockClickEvent());”

“mockWidget.fireEvent(new MockClickEvent());”

Comment on Building a GWT 1.6 application: Managing events with an eventBus by GWT Atchitecture anyone? « TechnoBuzz

GWT Atchitecture anyone? « TechnoBuzz — Mon, 17 Aug 2009 01:35:25 +0000

[...] see : Use MVP , MVP based Component Library, GWT MVP Sample, eventbus and mock [...]

Comment on GWT 1.6 MVP and testing, part 1 by GWT Atchitecture anyone? « TechnoBuzz

GWT Atchitecture anyone? « TechnoBuzz — Sat, 15 Aug 2009 21:26:47 +0000

[...] http://www.webspin.be/2009/06/gwt-1-6-mvp-and-testing-part-1/ Possibly related posts: (automatically generated)How to setup Ext js-GWT : GXT and Example on Eclipse Ganymede 3.4 [...]

Comment on Building a GWT 1.6 application: Managing events with an eventBus by DAvid

DAvid — Wed, 05 Aug 2009 21:07:46 +0000

Kudos on the good work representing gwt eventbus!
Its been quite difficult to find proper
eventbus examples to explain how to do this, and your’s is the best one i could find.
Thanks so much!

Comment on GWT 1.6: MVP and testing, part 2 by Duong BaTien

Duong BaTien — Fri, 03 Jul 2009 16:42:26 +0000

Excellent works. Few comments and suggestions for the next StockWatcher.
(1) StockWatcher has JSONP. It is better to isolate in a ‘hub’ responsible for receiving from Presenter (a) serverUrl, (b) queryAttributes, (c) sessionToken, and (4) handler from bound widget. The hub service does JSONP to serverUrl that set src handler to the bound widget handler
(2) Presenter takes the above 4 attributes, do the model jso and required processing before sending out the event using the hub service jsonRequest(…) that use getJson(.) as in the StockWatcher.
(3) The bound widget processes the response after receiving jso from the server.

The server inspects the token before providing the REST service. The bound widget inspect the token before processing the received response. The command pattern is modeled at the widget action level and somehow connected to action events for a roadmap to undo/redo, etc. This can be a lightweight framework. Manual DI for clear pattern before GIN

Comment on GWT 1.6: MVP and testing, part 2 by johan

johan — Thu, 02 Jul 2009 11:40:06 +0000

Thank you for a very comprehensive sample. I have been trying to understand Ray’s slides but unfortunately without luck. Could you make sure to include a command pattern RPC sample in your next post? Thanks