There is a Class Hierarchy page for all packages, plus a hierarchy for each package. You can access this page by first going to the package, class or interface, then clicking on the USE link in the navigation bar. Given a class or interface A, its Use page includes subclasses of A, fields declared as A, methods that return A, and methods and constructors with parameters of type A. This page describes what packages, classes, methods, constructors and fields use any part of the given class or package. UseĮach documented package, class and interface has its own Use page. Packages and modules may contain pages with additional information related to the declarations nearby. This preserves the logical groupings established by the programmer. The summary entries are alphabetical, while the detailed descriptions are in the order they appear in the source code. The components of a record class are displayed as part of the declaration of the record class. Note: Annotation interfaces have required and optional elements, but not methods. Entries in each of these sections are omitted if they are empty or not applicable. Each of these pages has three sections consisting of a declaration and description, member summary tables, and detailed member descriptions. These pages may contain the following categories:Įach class, interface, nested class and nested interface has its own separate page. PackageĮach package has a page that contains a list of its classes and interfaces, with a summary for each. This page can also contain an overall description of the set of packages. The Overview page is the front page of this API document and provides a list of all packages with a summary for each. The following sections describe the different kinds of pages in this collection.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |