On 6 nov, 01:24, Nicolas Antoniazzi <[email protected]> wrote: > Hello, > > I am trying to use CodeSplitting with Activites on 2.1. > I read this very interresting > threadhttp://code.google.com/p/google-web-toolkit/issues/detail?id=5129and > T.Broyer says that the best approach is to use an AsyncProxy for Activities.
I certainly didn't say it's the best approach (just that Jarod's code wasn't adding anything to AsyncProxy). > It makes sense but I have problem with it since my "Activities" are binded > with Gin. AsyncProxy uses GWT.create() to instantiate the concrete types and > all my @Inject in my Activities are thus not initialized. That's probably the reason why GIN added AsyncProvider<?>s (unfortunately not released yet) > Does anyone tried to mix new Activity concepts with "Code Splitting" ? And > do you know if it could be compatible with "Gin activities" ? I started coding the ActivityAsyncProxy I talked about in the issue tracker (i.e. don't even call start() on the activity if it's cancelled before being "downloaded"), but haven't yet tried it. I think (read: I *suppose*) that for it to work with GIN, your concrete implementations would have to use GIN's AsyncProvider, or get the Activity from the Ginjector from within a GWT.runAsync. -- 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.
