Conventions
The following font conventions are followed throughout this book:
- Italic
is used for filenames, file extensions, URLs, application names, and emphasis.
-
Constant width is used for Java class names, functions, variables, components, properties, data types, events, and snippets of code that appear in text.
We use tables throughout the book to present lists of properties (as
defined by the JavaBeans specification). Here’s an example from
the hypothetical JFoo class that shows how we use
these tables:
Table 1. Properties of the Fictional JFoo Class
|
Property |
Data Type |
get |
is |
set |
bound |
Default Value |
|---|---|---|---|---|---|---|
| See also properties from the JComponent class (Table 3.5). | ||||||
|
|
|
• |
• |
• |
• |
|
This table indicates that a JFoo object has a
read/write bound property named opaque, with the
data type boolean. This property has accessor
methods with the signatures:
public boolean getOpaque(); public boolean isOpaque(); public void setOpaque( boolean opaque );
These methods aren’t listed separately when we discuss the
class’s other methods. Because this is a bound property,
changing its value generates a
PropertyChangeEvent. JFoo has
also inherited properties from the JComponent
class; see the discussion of that class for these properties. The
asterisk after the property name indicates that the
opaque property is also inherited; it is listed
here because the JFoo class has changed the behavior of the property in some way—either by adding accessor methods ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access