[gwt-contrib] Re: ImageBundle pruning

[Bruce Johnson]

A great idea, and it's something Bob Vawter has been pushing for for ages
now. We do need to add some new architecture to make it possible. It might
be possible to hack it in by doing weird with generators and linkers working
in concert, but realistically, the right way will take a good bit of extra
work.

Bob can probably talk about it a lot more concretely.

On Thu, Mar 19, 2009 at 8:57 AM, Robert Hanson iamroberthan...@gmail.comwrote:


 Maybe I being naive, but is it be possible to use pruning with
 ImageBundles so that only referenced images are included in the
 compiled output?  In my case I have a bundle of 250 flags of the
 world, and all 250 are included in the compiled output even though I
 am only using a few of them.

 Maybe this planned?  Or maybe this is not possible with the current
 architecture?

 Just trying to understand the underlying mechanism.

 Thanks.

 


--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: ImageBundle pruning

[BobV]

The original idea was to have some kind of ReachabilityOracle that
could tell a Linker if some Java method were still contained in the
compiled JS output.  The Generator would create a task-list of
resources to add to the compiled output, and it would be the Linker's
responsibility to add that resource only if the referencing method
were still in the compilation.

SOYC as implemented today can fulfill the ReachabilityOracle
requirements, so the information is available, but we need to make
SOYC run faster and with less overhead so it can be turned on by
default.

-- 
Bob Vawter
Google Web Toolkit Team

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---