Re: UiBinder view inheritance troubles
On 04/04/2012 09:32, Márcio Menezes wrote:
> 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?
As Thomas said, it is hard to see what is your exact problem, but for what it is worth,
you can declare UiBinder components and re-use them, like:
<ui:UiBinder
xmlns:ui='urn:ui:com.google.gwt.uibinder'
xmlns:g="urn:import:com.google.gwt.user.client.ui"
xmlns:our="urn:import:com.our.company.web.client"
>
then use it as:
<our:MenuBar/>
or
<our:subpackage.OtherComponent/>
The components must be quite autonomous, perhaps exposing an API for using from other
components.
--
Philippe Lhoste
-- (near) Paris -- France
-- http://Phi.Lho.free.fr
-- -- -- -- -- -- -- -- -- -- -- -- -- --
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home