Monday, August 31, 2015

Re: Why code ends up in Left over Soyc report? How to analyze?

Thanks @Jens for your quick response.
Complicated...... ;)

Its not really possible to keep Total really small because you compile everything into a single app.
Yes, I understand that, but it would be nice to configure what is shared/downloaded and when.

probably keep small in your Total app is the initial code download because everything else is behind a split point.
What do mean by this and how to do this? 
I don't understand what mean, as currently I put everything behind a split point, and it's far from small.
A little side note: The Total app will fire the HomeController that is lazy loaded through a general split point (the split point isn't shared currently). The total controller will then show the page with the 2 app-start buttons.

> IMHO you actually haven't won anything because both your app's split points have been merged by GWT 
> to minimize left over.
Yes, I understand what you mean, but I though that in GWT 2.7.0, GWT will create smaller code fragments that are shared between split points, and don't necessary be in the left over fragment (= initial download eventually).
So why does GWT not create a small left over for Total and then a big "left-over" shared code fragment that is shared between Ztoeslag and Declare and is loaded when one of these apps are loaded (as a left-over fragment), so it's not part of the initial left-over. 
This is for me the expected behavior, especially as Total is very little and hardly share any code with Ztoeslag and Declare like explained in the first post. 
What am I not understanding here?

I still don't understand why this class "InkomstenOverzichtCalculator2011" (as example) is contained in the initial left over as it's ONLY used by the Declare app... Why? :(

The only downside might be that the client downloads common GWT SDK code (widgets, etc.) multiple times.
Yes, that is one of the main  reasons I put them together.
BTW: the apps can still run completely independent and being deployed independently.

> Choose your poison ;)
So basically you are saying it's (currently) not possible to fine tune the current GWT lazy loading mechanism to have control on what is loaded and when?
In my case I would like to indicate on for example package level what is allowed to be shared. How can this be possible (hidden split point features maybe...)? 
And can I realize a better left over by changing the fragmentCount?

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment