> > I am asking beacause in my last project I had a lot of boiler plate code, > a View, ViewImpl, Activity & Place for every crud action (update + create / > list) on every entity that I had to work with.
Be flexible. I sometimes use a controller -> presenter -> view. But often, if I have hardly any presentation logic just controller -> view... But I always use a controller that get's it's information from the event bus through visitor pattern. Note: I prefer push "controller" events through visitor pattern, then pulling them through observer pattern as it's easy to create memory leaks when not cleaning up (global) listeners. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/MzACQefJyGMJ. 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.
