Comment by a.revolution.ultra.blue:
@nenchev You want to add the following annotation to your x/y repeating
images
@ImageOptions(repeatStyle=RepeatStyle.Horizontal)
This will generate up to three bundled images, one for vertical repeat, one
for horizontal repeat, and the last for static sizing. Of course, unless
you disable inlining, this will only be used for non-data URI IE compiles.
@shahidzaman, Nenchev is correct. Source files for bundles must be in
client-accessible packages. If you want to use the bundle, but you also
want to copy the images to /war for deployment purposes {redundant and I
don't like it, but that doesn't mean you don't have a good reason to do
so}, you can use a second .gwt.xml file which sets the client source path
to public, so files in that folder will be source files, AND copied to war.
I have stuff like
`<source path="shell"/>
<inherits name="x.y"/>
<source path="client"/>`
in most of my modules. x.y is where I put RPC classes to shorten the
Strings sent over the wire. You could do the same, just change shell to
public, and in the middle, you have to inherit something, preferably
something that sets source path="client" at the top of the module, or else
you might get weird errors. com.google.gwt.user.User is a good one.
For more information:
http://code.google.com/p/google-web-toolkit/wiki/ClientBundle
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
