I also gave a thought to your method, but in the end opted out... but
I guess it's where you are heading.

In the same way that the View implements Display, an interface defined
in the Presenter class, Presenter could implement Execute, an
interface defined in the View class.

The View should have a method allowing injection of the Execute
object; the Presenter would this "self injection" in its constructor.

Then, whenever any event happened, the View handler would do getExecute
( ).someMethod( ).

You would do away with all anonymous classes, and each class (View,
Presenter) would implement an interface defined in the other class.

The symmetry breaks down a bit because you cannot inject each object
in the other through their constructors (obviously!)

Is this along the lines you were thinking?

--

You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.


Reply via email to