In IE, it's often loaded as external file.
In FF for example it's not external loaded but it's embedded as
base64.
Don't underestimate the advantages of the ClientBundle mechanism.
For example: the perfect caching is very important. Your included
images are unique and will be cached perfect such that the user won't
have to wait for the image next time it's loaded. Also it overcomes
caching problems when deploying a new version. I don't like to tell
my clients to first clear their browser cache... That is: if they
don't, they have a good change of seeing the old image for a few day's
more.. (it all depends on the proxies and browser being used)
- Ed
On Nov 25, 2:22 pm, kim young ill <khi...@googlemail.com> wrote:
> Hi,
>
> i want to use ClientBundle to put all images together,
>
> plain simple like this:
>
> @Source("img/priv.png")
> ImageResource priv();
>
> @Source("img/logo.png")
> ImageResource logo();
>
> @Source("img/back.png")
> ImageResource back();
>
> @Source("img/print.jpg")
> ImageResource printIcon();
>
> for unknown reason, when i set Image.setRecource(bundle.priv()), the image
> priv/png is loaded extra from /module/*****.cache.png.
> but it's not the purpose of using bundle, like this i could have use plain
> markup with url-property to get the image.
>
> did i do some thing wrong here ?
>
> thaxn
--
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.
No comments:
Post a Comment