On Wednesday, September 19, 2012 5:30:46 PM UTC+2, Chris Lercher wrote: > > According to > https://developers.google.com/web-toolkit/doc/latest/DevGuideUiImageBundles, > multiple images in the same ClientBundle should usually be merged to a > composite image, quote: > > Multiple ImageResources are declared in a single ClientBundle, which is a >> composition of many images into a single image > > > And I remember, that I tried and confirmed this, when I first used it a > few years ago. But I don't see this happening anymore: > > - Either we get data URIs (for small images), > - or we get separate "*.cache.jpg" images for each ImageResource in the > ClientBundle (for large images, or if setting <set-property > name="ClientBundle.enableInlining" value="false"/>) > > Is this correct, or is it a bug? >
That's correct. As KevMo says, "spriting" is actually only used for IE6/7. > Can I maybe even rely on GWT not producing composite images anymore [*]? > > [*] This would allow me to use "new Image(imageResource.getSafeUri())", > which would be useful in certain circumstances (e.g. when printing the > page), as it uses a foreground image instead of a background image. > You shouldn't (not that I can think of anything that would make us change the way it is though; note however that technically it depends on the exact generator being used, so it's easy to break code that makes such assumptions by only changing the *.gwt.xml) If you want to do a "new Image(someResourceInAClientBundle.getSafeUri())", you'd better use a DataResource. -- 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/-/FJAKw94e1tIJ. 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.
