On 2 February 2011 16:17, Thomas Broyer <[email protected]> wrote: > You can automate it by writing a linker that concatenates the CSS files into > a single one (same for JS ?) and emit a new artifact for the all-in-one > file. > There's no built-in solution for that, because the <script> and <stylesheet> > elements in gwt.xml files take URLs, not file paths; the URL can then just > happen to match a file that's in a "public" path, but there's no relation > between those apart from "naming convention". > > ...but you could also use ClientBundle to have the CSS inlined in the > compiled output (and make your widget take an instance of the bundle as > constructor argument so you can easily override the default style; which in > ClientBundle's world means the old, default CSS can be completely left out > of the compiled output).
Excellent. I've run into another issue, however. I'm now also including an image in the widget JAR. The image is at org.example.public and I can access it (in MyWidget's UiBinder) as src="MyWidget/my-image.png". However, once I reuse the widget in another widget (say, OtherWidget) the image is only found if I use OtherWidget/my-image.png. I'm guessing there's a better way to do this? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
