Generally speaking, you should prefer composition over inheritance. Separating your "superclass", into a "layout" widget (using @UiChild methods to allow adding child widgets when you use it in another ui.xml template) and a "presentation logic" code that you could possibly extend in a subclass, might help here. (hey, look, we just reinvented MVP ;-) )
-- 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/-/hGK4Tky1iMUJ. 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.
