Mmm yeah I guess you´re right. I´m probably trying a little to hard to mimic the Contacts example...
On 31 Jan, 04:04, Thomas Broyer <[email protected]> wrote: > On Jan 30, 11:22 pm, Dalla <[email protected]> wrote: > > > Would it be good practice to handle an event in both the controller > > aswell as in a presenter? > > > For example, let´s say that I want to respond to an event when a row > > in a table is clicked. > > I want to add a history token, aswell as update a second table based > > on what row was clicked in the first table. > > > The history token would be added in the app controller, but what about > > updating the second table. > > Should I handle the event in the presenter responsible for the second > > table, > > or would it be better to somehow expose that presenter in the > > controller and handle the > > event at the same time as adding the history token? > > Isn't that one of the goals of an event bus? -- 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.
