15.07.2013 Views

jgrasp handbook

jgrasp handbook

jgrasp handbook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

DRAFT, February 18, 2003, Page 5<br />

Program Documentation. For Java programs, users can automatically generate documentation in the<br />

style of an application programmer interface (API). jGRASP calls the javadoc utility, included with the<br />

J2SDK, to create a complete hyperlinked document within a few seconds. This can be done on a file-byfile<br />

basis or for a complete project as shown in Figure 5 below. Note, in this example, even though no<br />

JavaDoc comments were included in the source file, the generated documentation is still quite useful<br />

since it provides hyperlinks to all classes in the project, plus links to the fields, constructors, and methods<br />

of each class. However, for even more useful results, JavaDoc formal comments should be included in<br />

the source code. When the documentation is generated for an individual file, it is stored in a temporary<br />

directory for the duration of the jGRASP session. For projects, the documentation files are stored in a<br />

directory that becomes part of the project, and therefore, persists from one jGRASP session to the next.<br />

If any changes are made to a project source file (and the file is resaved), jGRASP will indicate that the<br />

documentation needs to be regenerated; however, the user may choose to view the documentation files<br />

without updating them.<br />

Figure 5. Project documentation for Java

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!