We use a slight various of Thomas' suggestion. We introduced a new interface / class called a "Broker" which we define all of our rpc calling methods in. Then be default we typically have the activity implement the Broker interface, but if need be we could have a new class implement it. We pass the Broker to the View so if the view needs access to rpc services it can call methods on the broker as need be. This still allows for the View to be stupid, but can help keep the activity code cleaner.
On Jul 13, 5:44 am, Thomas Broyer <t.bro...@gmail.com> wrote: > One of the goal of MVP is to make your presentation logic quickly & easily > testable (in GWT, that means using "pure JUnit" rather than the sluggish > GWTTestCase). As a result, you'd like to make you view as "dumb" as possible > (without necessarily pushing everything to presenter though, as it'd lose > readability and thus maintainability). So, you'd better put your RPC call in > your presenter (activity). -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
