If you've tried introducing multiple split points into your app, you might have found yourself cutting and pasting a lot. You might have tried getting rid of that cutting and pasting by introducing a common delay-loading abstraction. You probably discovered that this results in all the different split points you wanted, being mashed into one big one. So you went back to cutting and pasting.
At least that's the meandering path I (and several others on this list) took, before I discovered that you could use deferred binding to do all the dirty work for you, leaving your source nice and clean. I've tried to wrap up my efforts into a reusable package, which I've blogged about here: http://jcheng.wordpress.com/2010/02/16/elegant-code-splitting-with-gwt/ There is a steeper learning curve on this than I'd like, hence the length of the post. If you have any feedback on the approach, the code, or the writeup, I'm all ears... Thanks- Joe Cheng -- 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.
