Simply change AsyncProviderBinder template from
.append("com.google.gwt.core.client.GWT.runAsync(")
.append("new com.google.gwt.core.client.RunAsyncCallback() { \n")
to
.append("com.google.gwt.core.client.GWT.runAsync(").append(targetKeyName).append
(", new com.google.gwt.core.client.RunAsyncCallback() { \n")
which uses the other overload for GWT.runAsync that tags the split point with a
defined class name.
This way allows the user to set which split points should be loaded first in
the .gwt.xml module file and also makes the soyc report more human readable for
better understanding of the code size of each split point.
Original issue reported on code.google.com by triforc...@gmail.com on 3 Oct 2011 at 11:13
Original issue reported on code.google.com by
triforc...@gmail.com
on 3 Oct 2011 at 11:13