Re: Do I always have to import the full path for new components in ui-binder?

As far as I know the XML spec does not support it. So its not really an UiBinder problem.

Maybe you should try to reduce the amount of packages you have. Try to not over-specify things.

So I would expect the following (note the use of singular and plural):

1.) my.app.client.component: Contains different things related to the concept of a component (e.g. ComponentBuilder, ComponentLayouter)

2.) my.app.client.components: Contains a lot of different components (e.g. Button, CheckBox, Header, Footer, ...)

3.) my.app.client.component.header: Contains different things related to the concept of a header component (e.g. HeaderBuilder, ..)

4.) my.app.client.components.headers: Contains a lot of different header components (e.g. AutoHideHeader, BlueHeader, TinyHeader, ...)

But in case of 4.) if you only have 1-3 header components in that package, its IMHO not worth it to put it into a headers package. So I would move it up into the components package.

Maybe this helps you to rearrange your packages a bit so you dont have to import lots of XML namespaces into your UiBinder file. 

-- J.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.