On 22 oct, 19:50, David Chandler <[email protected]> wrote: > Hi Richard, > > We're still working on an official story for how best to use runAsync > with Activities and Places. In the mean time, feedback on your > experiences is welcome. GWT's AsyncProxy class or the AsyncProvider in > GIN trunk look promising as ways to wrap Activity creation with a > runAsync() call. > > If view creation is initiated only through the corresponding Activity, > then wrapping Activity creation with runAsync() will defer loading of > the view code also, and you'll be able to see this in the SOYC report. > > References: > http://code.google.com/webtoolkit/doc/latest/DevGuideCodeSplitting.html > http://code.google.com/webtoolkit/doc/latest/DevGuideCompileReport.html
Just so it doesn't get forgotten, see also http://code.google.com/p/google-web-toolkit/issues/detail?id=5129 I implemented the proposed ActivityAsyncProxy (see comment #4, as a concrete class, passing a GIN Provider<Activity> to the constructor) as a proof-of-concept but haven't used it yet (to tell the truth, not even tested it), so I cannot comment on how well/bad it works. -- 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.
