Home > Store

Java Class Libraries, Volume 2, The: java.applet,  java.awt,  java.beans, 2nd Edition

Register your product to gain access to bonus material or receive a coupon.

Java Class Libraries, Volume 2, The: java.applet, java.awt, java.beans, 2nd Edition

Book

  • This product currently is not for sale.
Not for Sale

Description

  • Copyright 1998
  • Dimensions: 7-3/8x9-1/4
  • Pages: 1712
  • Edition: 2nd
  • Book
  • ISBN-10: 0-201-31003-1
  • ISBN-13: 978-0-201-31003-0

As the definitive reference to the Java 1.1.2 version class libraries from the creators of the Java technology at Sun, this book is an essential resource for both beginner and experienced Java programmers.

This volume provides comprehensive reference documentation for the development of applets, user interfaces, and Java beans. The information is presented in an easy-to-use, dictionary-like format. The packages covered in Volume 2 are:

java.applet java.awt.image
java.awt java.awt.peer
java.awt.datatransfer java.beans
java.awt.event

The extensive class and member descriptions contain details crucial for developing robust and professional applets and applications. Each description is supplemented by an example that demonstrates the class or member in a relevant context. The 20,000 lines of code in over 350 examples facilitate learning-by-example and provide useful code fragments for your projects. Each class description includes:

  • a class hierarchy diagram showing its connection to related classes
  • a detailed overview describing its purpose and key concepts
  • a convenient member summary that briefly describes each member and arranges the members into related groups
  • an example demonstrating the class in a "real-world" context
  • comprehensive descriptions and an example for each member


0201310031B04062001

Downloads

Source Code

Click below for Source Code related to this title:
examples.html

Extras

Web Resources

Click below for Web Resources related to this title:
More Information from java.sun.com

Sample Content

Table of Contents



Action Event.


Action Listener.


Active Event.


Adjustable.


Adjustment Event.


Adjustment Listener.


Applet.


Applet Context.


Applet Stub.


Area Averaging Scale Filter.


Audio Clip.


AWT Error.


AWT Event.


AWT Event Multicaster.


AWT Exception.


Bean Descriptor.


Bean Info.


Beans.


Border Layout.


Button.


Button Peer.


Canvas.


Canvas Peer.


Card Layout.


Checkbox.


Checkbox Group.


Checkbox Menu Item.


Checkbox Menu Item Peer.


Checkbox Peer.


Choice.


Choice Peer.


Clipboard.


Clipboard Owner.


Color.


Color Model.


Component.


Component Adapter.


Component Event.


Component Listener.


Component Peer.


Container.


Container Adapter.


Container Event.


Container Listener.


Container Peer.


Crop Image Filter.


Cursor.


Customizer.


Data Flavor.


Dialog.


Dialog Peer.


Dimension.


Direct Color Model.


Event.


Event Queue.


Event Set Descriptor.


Feature Descriptor.


File Dialog.


File Dialog Peer.


Filtered Image Source.


Flow Layout.


Focus Adapter.


Focus Event.


Focus Listener.


Font.


Font Peer.


Font Metrics.


Frame.


Frame Peer.


Graphics.


Grid Bag Constraints.


Grid Bag Layout.


Grid Layout.


Illegal Component State Exception.


Image.


Image Consumer.


Image Filter.


Image Observer.


Image Producer.


Index Color Model.


Indexed Property Descriptor.


Input Event.


Insets.


Introspection Exception.


Introspector.


Item Event.


Item Listener.


Item Selectable.


Key Adapter.


Key Event.


Key Listener.


Label.


Label Peer.


Layout Manager.


Layout Manager 2.


Lightweight Peer.


List.


List Peer.


Media Tracker.


Memory Image Source.


Menu.


Menu Bar.


Menu Bar Peer.


Menu Component.


Menu Component Peer.


Menu Container.


Menu Item.


Menu Item Peer.


Menu Peer.


Menu Shortcut.


Method Descriptor.


Mouse Adapter.


Mouse Event.


Mouse Listener.


Mouse Motion Adapter.


Mouse Motion Listener.


Paint Event.


Panel.


Panel Peer.


Parameter Descriptor.


Pixel Grabber.


Point.


Polygon.


Popup Menu.


Popup Menu Peer.


Print Graphics.


Print Job.


Property Change Event.


Property Change Listener.


Property Change Support.


Property Descriptor.


Property Editor.


Property Editor Manager.


Property Editor Support.


Property Veto Exception.


Rectangle.


Replicate Scale Filter.


RGB Image Filter.


Scrollbar.


Scrollbar Peer.


Scroll Pane.


Scroll Pane Peer.


Shape.


Simple Bean Info.


String Selection.


System Color.


Text Area.


Text Area Peer.


Text Component.


Text Component Peer.


Text Event.


Text Field.


Text Field Peer.


Text Listener.


Toolkit.


Transferable.


Unsupported Flavor Exception.


Vetoable Change Listener.


Vetoable Change Support.


Visibility.


Window.


Window Adapter.


Window Event.


Window Listener. 0201310031T04062001

Preface

How to Use This Book

This book is intended as a reference rather than a tutorial. Its format is similar to a dictionary's in that it is designed to optimize the time it takes for you to look up information on a class or class member. For a tutorial-style presentation of the class libraries, see The JavaTM Tutorial, by Mary Campione and Kathy Walrath. The JavaTM Class Libraries does not explain any part of the Java language. There are several books you can use to learn the language. These include The JavaTM Programming Language, by Ken Arnold and James Gosling, and The JavaTM Language Specification, by James Gosling, Bill Joy, and Guy Steele.

Following is an overview of this book.

Package Overviews

This part briefly describes each package and all of the classes in it. Also included are diagrams that show the inheritance hierarchy of the classes that appear in a package.

Alphabetical Reference of Classes

This part covers the alphabetical listing of the classes from the following packages:

java.applet
java.awt
java.awt.datatransfer
java.awt.event
java.awt.image
java.awt.peer
java.beans

Probably the most notable aspect about the structure of this book is the order in which the classes appear. Most Java books that contain an API alphabetically order the classes within a package and then alphabetically order the packages. The problem with this format is that it always takes two or more steps to locate a class. If you do not know which package contains the class you're looking for, you basically need to review each package looking for the class. If you do know which package, you first need to find the package and then find the class.

The classes in this book are ordered alphabetically without regard to package name. This makes looking up a class as straightforward as looking up a word in a dictionary.

Each class is described in its own chapter. Each chapter contains a picture of the class hierarchy, a class description, a class example, a member summary, and descriptions for every member in the class.

Class Hierarchy Diagrams

We include a class diagram for each class in the Java API. The class diagram shows all of the ancestors of the class, its siblings, its immediate descendents, and any interfaces that the class implements. In these diagrams, if a package name precedes a class or interface name, the class or interface is not in the same package as the current class.

In the diagrams, we visually distinguish the different kinds of Java entities, as follows:

  1. The interface: A rounded rectangle
  2. The class: A rectangle
  3. The abstract class: A rectangle with an empty dot
  4. The final class: A rectangle with a black dot
  5. Classes with subclasses: A rectangle with a small black triangle on the lower right corner

Most of these elements are shown in Figure i. The class or interface being described in the current chapter is shaded grey. A solid line represents extends, while a dotted line represents implements.

Class Descriptions

In the class descriptions, we describe all of the properties of the class. For example, the properties of the Graphics class include the current color, font, paint mode, origin, and clipping area. Describing in one place all of a class's available properties and how the properties behave makes learning all of the capabilities of a class much easier than if the property descriptions were scattered throughout the member descriptions.

Any terminology used in the member descriptions is introduced and described in the class descriptions. If you find that the member description lacks detail, go to the class description for more information.

Class Examples

Ideally, we would have included a unique example for every single member in the Java API. We simply did not have enough time. So we tried to make sure that every member appeared in at least one example.

We worked to make the examples as useful as possible so that they demonstrate the member as it would typically be used. For example, in the example for a button we not only show how a button is created; we also show how button events are handled. In some cases, we also try to demonstrate some other class in the Java API. For example, in the Graphics.draw-Oval() example, we demonstrate not only how to draw an oval; we also show how to use the BufferedReader class to read integers from standard input that are used to locate the oval. We feel that gently introducing other classes in the Java API is a good way to help you become aware of all available classes in the Java API, as long as the introduction does not confuse the example.

Member Summaries

The Member Summary section for each class is intended to help the reader quickly grasp the key points of the class. It groups the members of the class into categories that are specific to that class. For example, in the List class the Selection Methods category lists all methods having to do with selections. It is meant to be a quick summary of the class's members, so it does not contain any syntax information other than the name of the member.

Member Descriptions

The member descriptions appear in alphabetical order within a class chapter regardless of what kind of method or field they are. This was done to make locating a member proceed as fast as possible.

Overloaded methods are placed together in one member description because they share very similar functionality. The different overloaded forms are typically provided as a convenience for the programmer when specifying parameters. For instance, some overloads eliminate parameters by providing common defaults. To describe overloads with missing parameters, we use a phrase of the form "if the parameter p is not specified, it defaults to the value 3.14." Other overloads take different representations of a value. For example, one overload could take a particular parameter as an integer, while another could take the same parameter as a string containing an integer.

Each member description contains some or all of the following fields:

PURPOSE A brief description of the purpose of this member
SYNTAX The syntactic declaration of this member
DESCRIPTION A full description of this member
PARAMETERS The parameters accepted by this member, if any, listed in alphabetical order
RETURNS The value and its range returned by this member, if any
EXCEPTIONS The exceptions and errors thrown by this member, if any, listed in alphabetical order
SEE ALSO Other related classes or members, if any, listed in alphabetical order
OVERRIDES The method that this member overrides, if any
EXAMPLE A code example that illustrates how this member is used. This is sometimes a reference to an example that illustrates the use of this method in another member example or class example.

Deprecation

A method or class is deprecated if its use is no longer recommended. A deprecated method appears in the Member Summary under the Deprecated Methods section. In the chapter body, the deprecated method is annotated by a "deprecated" tag in its method heading. For example, Component.size() is a deprecated method. It has the following method heading:

size() DEPRECATED

If not all of the overloaded forms of the method are deprecated, a "deprecated" tag appears beside the syntax of the deprecated forms. For example, one of the two forms of BorderLayout.addLayoutComponent() is deprecated. The second form shown below--the one with the "deprecated" tag--is deprecated.

SYNTAX public void addLayoutComponent(Component comp, Object location)
DEPRECATED public void addLayoutComponent(String location, Component comp)

The method description contains a deprecation section with instructions on how to replace the usage of the deprecated method, like this:

DEPRECATION   A description of how to replace the usage of this deprecated method

How to Access the Examples

All of the code examples in this book have been compiled and run on the FCS version of Java 1.1.2, either on Solaris or Windows NT or both. Most of the complete examples are available on-line. You can access them and other information about this book by using the URL

http://java.sun.com/docs/books/chanlee/second_edition/

Conventions Used in This Book

Lucida Sans Typewriter is used for examples, syntax declarations, class names, method names, values, and field names. Italic is used when defining a new term and for emphasis.

Acknowledgments

We want to thank the many people who made this book possible.

We want to thank all of the wonderful readers of our first edition who sent us nice comments and suggestions. You gave us the strength to do this second edition.

Mike Hendrickson, the Acquisition Editor for this book, assisted us throughout the production of the book, from formatting the raw manuscript, to finding us experts to help with PostScript and formatting, to performing numerous coordination tasks. Thanks Mike!

Lisa Friendly, the series editor and a wonderful friend, was extremely helpful in providing all kinds of assistance in JavaSoft.

Sarah Weaver, Laura Michaels, Rosemary Simpson, Tracy Russ, Chris Norum, Jason Jones, and Yvo Riezebos all played a part in the production of this book and were wonderful to work with.

Tomas G. Rokicki provided invaluable expert advice (and code) so that we could generate all of the class diagrams automatically. Joseph Newcomer provided us with helpful hints for dealing with FrameMaker. And Ramin Sedehi rescued a week's worth of words after our laptop went south.

The following people provided many helpful comments and information: Calvin Austin, Tom Ball, Amy Fowler, Jim Graham, David Holmes, Doug Kramer, Tim Lindholm, Tim Prinzing, Georges Saab, and Kathy Walrath.

Roselyn and Norman Chin spent countless hours entertaining our children while we worked on the book.

Patrick Chan
Rosanna Lee
Palo Alto, California
August, 1997

0201310031P04062001

Updates

Errata

Click below for Errata related to this title:
Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020