On Wednesday, April 4, 2012 9:32:06 AM UTC+2, Márcio Menezes wrote: > > Hi all. > I'm migrating all my views from the old style to @UiBinder based and I'm > facing some troubles > I used to have base views (Composite) in charge of adding common > components, ie: EditModelBaseView is in charge of adding the save and > cancel button, so that all the sub views will render those components by > inheritance. > I can't get it to work... I would need a sort of xml inheritance, besides > the the class inheritance, but this doesn't seem to be possible because the > compiler complains stating the inherited attributes aren't declared in the > subview ui.xml. How would this approach be matched with UiBinder based > views?
Could you give more information? How and where is the base view "adding widgets"? How and where child views add their own widgets? One thing is: you cannot use a single class hierarchy as the target for two UiBinders; that is, you cannot have a UiBinder<?,BaseView> and a UiBinder<?,ChildView> with ChildView extends BaseView. You can, for example, move your @UiFields from one of the classes to another class (e.g. declare an inner class in BaseView and move the @UiFields to that class, then use a UiBinder<?,BaseView.UiFieldHolder>; that way, the UiBinder<?,ChildView> won't conflict with the BaseView) But it's really hard to give advice as we don't know what you're trying to do, how you're trying to do it, and what's the problem (error message) exactly. -- 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/-/7svZNGfjvLIJ. 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.
