Thanks for all the feedback. I feel very comfortable with the solution.
Thanks!
On Wed, May 2, 2012 at 4:21 PM, Jens wrote:
> Thats what code splitting is for. But don't create 500 split points (each
> split point has some overhead), e.g. one for each screen! Make it more
> meaningful so you m
Thats what code splitting is for. But don't create 500 split points (each
split point has some overhead), e.g. one for each screen! Make it more
meaningful so you may end up with 20 split points or so.
As of today, when you introduce split points in your code you have to make
sure that the cod
On Wed, May 2, 2012 at 10:44 PM, Gal Dolber wrote:
> https://developers.google.com/web-toolkit/doc/latest/DevGuideCodeSplitting
Jupp. Gwt is made for that scenario :)
I'd recommend checking out the excellent gwtp project. Using gwtp you
get code splitting almost for free :)
http://code.google.c
https://developers.google.com/web-toolkit/doc/latest/DevGuideCodeSplitting
On Wed, May 2, 2012 at 5:38 PM, Blake McBride wrote:
> Greetings,
>
> Unless I misunderstand something, I just found out that GWT apps get
> transmitted to, and treated by, the client as a single web page - albeit
> with
Greetings,
Unless I misunderstand something, I just found out that GWT apps get
transmitted to, and treated by, the client as a single web page - albeit
with JavaScript code that clears sections and puts different content on it
to make it look like different pages are being loaded. This is cool i
