diff --git a/src/main/markdown/doc/latest/DevGuideCompileReport.md b/src/main/markdown/doc/latest/DevGuideCompileReport.md index 2850fd5e6..4170a2ddc 100644 --- a/src/main/markdown/doc/latest/DevGuideCompileReport.md +++ b/src/main/markdown/doc/latest/DevGuideCompileReport.md @@ -1,7 +1,7 @@ -Compile Reports +Compilation Reports === -When programming in GWT, it can sometimes be difficult to understand the compiled output. This is especially true for users of code splitting: why are some fragments bigger, some smaller? Our answer to these questions are Compile Reports. Compile Reports let GWT programmers gain insight into what happens in their application during the compile: how much output their code leads to, what Java packages and classes lead to large JavaScript output, and how the code is split up during code splitting. With this information, you can then modify their application in a targeted way in order to reduce the size of the entire compiled application or the size of certain fragments. +When programming in GWT, it can sometimes be difficult to understand the compiled output. This is especially true for users of [code splitting](DevGuideCodeSplitting.html): why are some fragments bigger, some smaller? Our answer to these questions are Compile Reports. Compile Reports let GWT programmers gain insight into what happens in their application during the compile: how much output their code leads to, what Java packages and classes lead to large JavaScript output, and how the code is split up during code splitting. With this information, you can then modify their application in a targeted way in order to reduce the size of the entire compiled application or the size of certain fragments. A compile report can be produced during a regular GWT compile. It consists of a set of HTML pages that can easily be browsed and navigated and that provide a graphical representation of the application's compile.