Granted, it is a pretty big project, it has about 800 activities, 150 EntityProxy types, 100 Request objects, and uses all the goodness of the RequestFactory and UiBinder for all of it. (There is a ton of inheritance so most of those activities are only 50-100 lines of code. Only the object-specific code in each remains, at least until http://code.google.com/p/google-web-toolkit/issues/detail?id=6794 is fixed)
The current split points are on each top-level domain object, each of which contain about 5-10 activities. Each generates about 50-150kb of JS when they work. The idea was that the user would have a small initial download, and then a slight delay each time they hit a new object type they hadn't used before. I guess I could move the splits to the package level in the object hierarchy and only have about 8 split points, each with about 100 activities. That should leave the initial download the same, but have a bigger run-time hit when the user crosses that boundary. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/FKtXxh5GrC0J. 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.
