19.2. Using the Compile Report
Throughout the book, we’ve talked a lot about how the compiler generates a bunch of code for you, prunes out any code that isn’t called, creates several versions of that code specific to each browser, runs it through a Java-to-JavaScript conversion process, and then spits it out. You can dismiss it as magic, but dismissing it won’t help you understand what’s in there (and what isn’t).
Understanding the output is useful for a number of reasons. Perhaps you want to reduce the size of your compiled code and need to know what classes have been compiled into the output. Perhaps your users are complaining about a JavaScript error in a function named Cb, and you need to know to what Java method it corresponds. Or maybe ...
Get GWT in Action, Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
