DOCSLIB.ORG

Java Foundation Classes, Visit the Java Technology and Swing Connection Web Sites at And

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Java Foundation Classes, Visit the Java Technology and Swing Connection Web Sites at And Java Look and Feel Design Guidelines Frames version | No frames version | Reader Feedback Version 1.0.2 December 1999 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, CA 94303 USA, 650 960-1300 Copyright© 1999 Sun Microsystems, Inc. All Rights Reserved. Terms of Use | Privacy Policy. java.sun.com : Design Guidelines Previous | Next | Contents | Index | Search http://java.sun.com/products/jlf/dg/higtitle.alt.htm [05/06/2000 14:11:49] Design Guidelines: Preface Preface Java Look and Feel Design Guidelines provides essential information for anyone involved in creating cross-platform applications and applets in the JavaTM programming language. In particular, this book offers design guidelines for software that uses the JavaTM Foundation Classes (JFC) together with the Java look and feel. Who Should Use This Book Although the human interface designer and the software developer might well be the same person, the two jobs require different tasks, skills, and tools. Primarily, this book addresses the designer who chooses the interface components, lays them out in a set of views, and designs the user interaction model for an application. (Unless specified otherwise, this book uses "application" to refer to both applets and applications.) This book should also prove useful for developers, technical writers, graphic artists, production and marketing specialists, and testers who participate in the creation of Java applications and applets. Java Look and Feel Design Guidelines focuses on design issues and human-computer interaction in the context of the Java look and feel. It also attempts to provide a common vocabulary for designers, developers, and other professionals. If you require more information about technical aspects of the Java Foundation Classes, visit the Java Technology and Swing Connection web sites at http://java.sun.com and http://java.sun.com/products/jfc. The guidelines provided in this book are appropriate for applications and applets that run on personal computers and network computers. They do not address the needs of software that runs on consumer electronic devices. What Is in This Book Java Look and Feel Design Guidelines includes the following chapters: Chapter 1, "The Java Look and Feel," introduces key design concepts and visual elements underlying the Java look and feel and offers a quick visual tour of an application and an applet designed with the JFC components and the Java look and feel. Chapter 2, "The Java Foundation Classes,"provides an overview of the JavaTM Development Kit and the Java Foundation Classes, introduces the JFC components, discusses the concept of pluggable look and feel designs, and describes the currently available look and feel options. Chapter 3, "Design Considerations," discusses some of the fundamental challenges of designing Java look and feel applications and applets and of providing for accessibility, internationalization, and localization. Chapter 4, "Visual Design," suggests ways to use the Java look and feel theme mechanism to change colors and fonts, provides guidelines for the capitalization of text in the interface, and gives recommendations for layout and visual alignment. http://java.sun.com/products/jlf/dg/higa.htm (1 sur 8) [05/06/2000 14:15:51] Design Guidelines: Preface Chapter 5, "Application Graphics," discusses the use of cross-platform color, the creation of graphics that suit the Java look and feel, and the use of graphics to enhance corporate and product identity. Chapter 6, "Behavior," tells how users of Java look and feel applications utilize the mouse, keyboard, and screen and provides guidelines regarding user input and human-computer interaction, including drag-and-drop operations. Chapter 7, "Windows, Panes, and Frames," discusses and makes recommendations for the use of primary, secondary, plain, and utility windows as well as panels, scroll panes, tabbed panes, split panes, and internal frames. Chapter 8, "Dialog Boxes," describes dialog boxes and alert boxes, sets standards for dialog box design, and provides examples of typical dialog boxes in Java look and feel applications. Chapter 9, "Menus and Toolbars," defines and gives guidelines for the use of drop-down menus, contextual menus, toolbars, and tool tips and provides examples of typical menus in Java look and feel applications. Chapter 10, "Basic Controls," covers the use of controls such as command buttons, toggle buttons, checkboxes, radio buttons, sliders, and combo boxes; it also describes progress bars and provides suggestions for their use. Chapter 11, "Text Components," explains and makes recommendations for the use of the JFC components that control the display and editing of text: labels, text fields, text areas, and editor panes. Chapter 12, "Lists, Tables, and Trees," discusses and makes recommendations for the use of lists, tables, and tree views. Appendix A, "Keyboard Navigation, Activation, and Selection," contains tables that specify keyboard operations for the components of the Java Foundation Classes. Glossary defines important words and phrases found in this book. Glossary terms appear in boldface throughout the book. What Is Not in This Book This book does not provide detailed discussions of human interface design principles or the design process, nor does it present much general information about usability testing. For authoritative explications of human interface design principles and the design process, see Macintosh Human Interface Guidelines. For the classic book on usability testing, see Jakob Nielsen's Usability Engineering. For details on both of these valuable resources, see Related Books and Web Sites. Graphic Conventions Screen shots in this book illustrate the use of JFC components in applications with the Java look and feel. Because such applications typically run inside windows provided and managed by the native platform, the screen shots show assorted styles of windows and dialog boxes from the Microsoft Windows, Macintosh, and CDE (Common Desktop Environment) platforms. http://java.sun.com/products/jlf/dg/higa.htm (2 sur 8) [05/06/2000 14:15:51] Design Guidelines: Preface Throughout the text, symbols are used to call your attention to design guidelines. Each type of guideline is identified by a unique symbol. Java Look and Feel Standards Requirements for the consistent appearance and compatible behavior of Java look and feel applications. Java look and feel standards promote flexibility and ease of use in cross-platform applications and support the creation of applications that are accessible to all users, including users with physical and cognitive limitations. These standards require you to take actions that go beyond the provided appearance and behavior of the JFC components. Occasionally, you might need to violate these standards. In such situations, use your discretion to balance competing requirements. Be sure to engage in user testing to validate your judgments. Cross-Platform Delivery Guidelines Recommendations for dealing with colors, fonts, keyboard operations, and other issues that arise when you want to deliver your application to a variety of computers running a range of operating systems. Internationalization Guidelines Advice for creating applications that can be adapted to the global marketplace. Implementation Tips Technical information and useful tips of particular interest to the programmers who are implementing your application design. Related Books and Web Sites Many excellent references are available on topics such as fundamental principles of human interface design, design issues for specific (or multiple) platforms, and issues relating to accessibility, internationalization, and applet design. Design Principles The resources in this section provide information on the fundamental concepts underlying human-computer interaction and interface design. http://java.sun.com/products/jlf/dg/higa.htm (3 sur 8) [05/06/2000 14:15:51] Design Guidelines: Preface Baecker, Ronald M., William Buxton, and Jonathan Grudin, eds. Readings in Human-Computer Interaction: Toward the Year 2000, 2d ed. Morgan Kaufman, 1995. Based on research from graphic and industrial design and studies of cognition and group process, this volume addresses the efficiency and adequacy of human interfaces. Hurlburt, Allen. The Grid: A Modular System for the Design and Production of Newspapers, Magazines, and Books. John Wiley & Sons, 1997. This is an excellent starting text. Although originally intended for print design, this book contains many guidelines that are applicable to software design. IBM Human-Computer Interaction Group. "IBM Ease of Use." Available: http://www.ibm.com/ibm/easy. This web site covers many fundamental aspects of human interface design. Laurel, Brenda, ed. Art of Human-Computer Interface Design. Addison-Wesley, 1990. Begun as a project inside Apple, this collection of essays explores the reasoning behind human-computer interaction and looks at the future of the relationship between humans and computers. Mullet, Kevin, and Darrell Sano. Designing Visual Interfaces: Communication Oriented Techniques. Prentice Hall, 1995. This volume covers fundamental design principles, common mistakes, and step-by-step techniques for handling the visual aspects of interface design. Nielsen, Jakob. Usability Engineering. AP Professional, 1994. This classic covers international user interfaces (including gestural interfaces), international usability engineering, guidelines for internationalization, resource separation, and interfaces for more than one locale. Norman,
Load more

Recommended publications
  • A Java Implementation of a Portable Desktop Manager Scott .J Griswold University of North Florida
    UNF Digital Commons UNF Graduate Theses and Dissertations Student Scholarship 1998 A Java Implementation of a Portable Desktop Manager Scott .J Griswold University of North Florida Suggested Citation Griswold, Scott .,J "A Java Implementation of a Portable Desktop Manager" (1998). UNF Graduate Theses and Dissertations. 95. https://digitalcommons.unf.edu/etd/95 This Master's Thesis is brought to you for free and open access by the Student Scholarship at UNF Digital Commons. It has been accepted for inclusion in UNF Graduate Theses and Dissertations by an authorized administrator of UNF Digital Commons. For more information, please contact Digital Projects. © 1998 All Rights Reserved A JAVA IMPLEMENTATION OF A PORTABLE DESKTOP MANAGER by Scott J. Griswold A thesis submitted to the Department of Computer and Information Sciences in partial fulfillment of the requirements for the degree of Master of Science in Computer and Information Sciences UNIVERSITY OF NORTH FLORIDA DEPARTMENT OF COMPUTER AND INFORMATION SCIENCES April, 1998 The thesis "A Java Implementation of a Portable Desktop Manager" submitted by Scott J. Griswold in partial fulfillment of the requirements for the degree of Master of Science in Computer and Information Sciences has been ee Date APpr Signature Deleted Dr. Ralph Butler Thesis Advisor and Committee Chairperson Signature Deleted Dr. Yap S. Chua Signature Deleted Accepted for the Department of Computer and Information Sciences Signature Deleted i/2-{/1~ Dr. Charles N. Winton Chairperson of the Department Accepted for the College of Computing Sciences and E Signature Deleted Dr. Charles N. Winton Acting Dean of the College Accepted for the University: Signature Deleted Dr.
    [Show full text]
  • Java Programming Language, Java SE 6
    Java Programming Language, Java SE 6 Electronic Presentation SL-275-SE6 REV G.2 D61748GC11 Edition 1.1 Copyright © 2008, 2010, Oracle and/or its affiliates. All rights reserved. Disclaimer This document contains proprietary information, is provided under a license agreement containing restrictions on use and disclosure, and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except as expressly permitted in your license agreement or allowed by law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free. Sun Microsystems, Inc. Disclaimer This training manual may include references to materials, offerings, or products that were previously offered by Sun Microsystems, Inc. Certain materials, offerings, services, or products may no longer be offered or provided. Oracle and its affiliates cannot be held responsible for any such references should they appear in the text provided. Restricted Rights Notice If this documentation is delivered to the U.S. Government or anyone using the documentation on behalf of the U.S. Government, the following notice is applicable: U.S.
    [Show full text]
  • A Study on Advance Java with Database Management
    IJRDO - Journal of Computer Science and Engineering ISSN: 2456-1843 ENGINEERING A STUDY ON ADVANCE JAVA WITH DATABASE MANAGEMENT MONIKA JATIWAL , CHETNA ARORA , CHARU ARORA OUTLINE 1. Introduction 1.1 API 1.2 Applets 1.3 Swing 1.4 Java Software: Net beans 1.5 Features of advance java 2. Database Management 2.1 SQL as a Data Definition Language 2.2 JDBC 2.3 Microsoft ODBC 3. Database connectivity 4. Advantage of Advance Java 5. Conclusion 6. References ABSTRACT This paper gives a short description about the java and database connectivity. It describes the advance java features with database Volume-1 | Issue-1 | January, 2016 | Paper-1 1 IJRDO - Journal of Computer Science and Engineering ISSN: 2456-1843 JOURNAL OF COMPUTER SCIENCE AND ENGINEERING connectivity. It also describes the application programming interface with applets and swings. This paper explains about the java and its connectivity with database. It describes the structured query language as a data definition and data manipulation language. It also defines the java platform. 1. INTRODUCTION Java is a high-level object-oriented programming language developed by the Sun Microsystems. Though it is associated with the World Wide Web but it is older than the origin of Web. It was only developed keeping in mind the consumer electronics and communication equipment’s. It came into existence as a part of web application, web services and a platform independent programming language in the 1990s. Earlier, C++ was widely used to write object oriented programming languages, however, it was not a platform independent and needed to be recompiled for each different CPUs.
    [Show full text]
  • The GNOME Desktop Environment
    The GNOME desktop environment Miguel de Icaza ([email protected]) Instituto de Ciencias Nucleares, UNAM Elliot Lee ([email protected]) Federico Mena ([email protected]) Instituto de Ciencias Nucleares, UNAM Tom Tromey ([email protected]) April 27, 1998 Abstract We present an overview of the free GNU Network Object Model Environment (GNOME). GNOME is a suite of X11 GUI applications that provides joy to users and hackers alike. It has been designed for extensibility and automation by using CORBA and scripting languages throughout the code. GNOME is licensed under the terms of the GNU GPL and the GNU LGPL and has been developed on the Internet by a loosely-coupled team of programmers. 1 Motivation Free operating systems1 are excellent at providing server-class services, and so are often the ideal choice for a server machine. However, the lack of a consistent user interface and of consumer-targeted applications has prevented free operating systems from reaching the vast majority of users — the desktop users. As such, the benefits of free software have only been enjoyed by the technically savvy computer user community. Most users are still locked into proprietary solutions for their desktop environments. By using GNOME, free operating systems will have a complete, user-friendly desktop which will provide users with powerful and easy-to-use graphical applications. Many people have suggested that the cause for the lack of free user-oriented appli- cations is that these do not provide enough excitement to hackers, as opposed to system- level programming. Since most of the GNOME code had to be written by hackers, we kept them happy: the magic recipe here is to design GNOME around an adrenaline response by trying to use exciting models and ideas in the applications.
    [Show full text]
  • The Applet Class, Swings
    Module – 5 The Applet Class, Swings OOC 4th Sem, ‘B’ Div 2016-17 Prof. Mouna M. Naravani Swings - Introduction Differentiate between AWT and Swings. (Jan 2013, 5m) Sl. No Java AWT Java Swings 1 AWT stands for Abstract windows Swing is also called as JFC’s (Java toolkit. Foundation classes). 2 AWT components are platform- Java swing components are platform- dependent. independent. 3 AWT components are heavyweight. Swing components are lightweight. 4 AWT doesn't support pluggable look Swing supports pluggable look and and feel. feel. Sl. No Java AWT Java Swings 5 AWT provides less components than Swing provides more powerful Swing. components such as tables, lists, scrollpanes, colorchooser, tabbedpane etc. 6 AWT doesn't follows MVC(Model View Swing follows MVC. Controller) where model represents data, view represents presentation and controller acts as an interface between model and view. Two Key Swing Features (June 2012, 10m) 1. Lightweight components 2. Pluggable look and feel 1. Lightweight Components Swing components are lightweight as they are written entirely in Java and do not depend on native peers (platform specific code resources). Rather, they use simple drawing primitives to render themselves on the screen. The look and the feel of the component is not controlled by the underlying operating system but by Swing itself. Thus, they are not restricted to platform-specific appearance like, rectangular or opaque shape. 2. Pluggable Look and Feel Swing supports a pluggable look and feel (PLAF). Because each Swing component is rendered by Java code rather than by native peers, the look and feel of a component is under the control of Swing.
    [Show full text]
  • Java-Accessibility-Guide.Pdf
    Java Platform, Standard Edition Java Accessibility Guide Release 15 F32124-01 September 2020 Java Platform, Standard Edition Java Accessibility Guide, Release 15 F32124-01 Copyright © 1993, 2020, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition
    [Show full text]
  • GUI Object Level Architectures Recap
    GUI Object Level Architectures Recap • Lots of Input Devices – Basic input devices (keyboard, mouse, buttons, valuators) – Exotic input devices (3D Input, Gloves, Crosspads) – Research input devices (Peephole display, speech, touch) Recap • Handling input – Predefine all kinds of devices (too rigid, didn’t work too well) – Instead, organize everything as event or sampled devices – Handle everything in software as events Mouse Events Software Keyboard Software Today • Object-level architectures – Design patterns for GUIs – Model-View-Controller – Pluggable Look and Feel – Undo / Redo Internal Organization of Widgets • GUI widgets organized Model-View-Controller (MVC) – Basic idea: split widget into three separate objects – Each handles different aspect of widget Model-View-Controller • Model handles core functionality and data • Micro-level (internal to widget) – Scrollbar state – Checkbox state – What cell in table is currently highlighted • Macro-level (application) – Table data – Content in a document – Image in paint program Model-View-Controller • Model provides: – methods to edit data, which Controller can call – methods to access state, which View and Controller can request • Model has registry of dependent Views to notify on data changes • In Swing, listeners stored here Model-View-Controller • Model examples: – text editor: model is text string – slider: model is an integer – spreadsheet: collection of values related by functional constraints Model-View-Controller • View handles how the widget appears – Handles display of information
    [Show full text]
  • CDC: Java Platform Technology for Connected Devices
    CDC: JAVA™ PLATFORM TECHNOLOGY FOR CONNECTED DEVICES Java™ Platform, Micro Edition White Paper June 2005 2 Table of Contents Sun Microsystems, Inc. Table of Contents Introduction . 3 Enterprise Mobility . 4 Connected Devices in Transition . 5 Connected Devices Today . 5 What Users Want . 5 What Developers Want . 6 What Service Providers Want . 6 What Enterprises Want . 6 Java Technology Leads the Way . 7 From Java Specification Requests… . 7 …to Reference Implementations . 8 …to Technology Compatibility Kits . 8 Java Platform, Micro Edition Technologies . 9 Configurations . 9 CDC . 10 CLDC . 10 Profiles . 11 Optional Packages . 11 A CDC Java Runtime Environment . 12 CDC Technical Overview . 13 CDC Class Library . 13 CDC HotSpot™ Implementation . 13 CDC API Overview . 13 Application Models . 15 Standalone Applications . 16 Managed Applications: Applets . 16 Managed Applications: Xlets . 17 CLDC Compatibility . 18 GUI Options and Tradeoffs . 19 AWT . 19 Lightweight Components . 20 Alternate GUI Interfaces . 20 AGUI Optional Package . 20 Security . 21 Developer Tool Support . 22 3 Introduction Sun Microsystems, Inc. Chapter 1 Introduction From a developer’s perspective, the APIs for desktop PCs and enterprise systems have been a daunting combination of complexity and confusion. Over the last 10 years, Java™ technology has helped simplify and tame this world for the benefit of everyone. Developers have benefited by seeing their skills become applicable to more systems. Users have benefited from consistent interfaces across different platforms. And systems vendors have benefited by reducing and focusing their R&D investments while attracting more developers. For desktop and enterprise systems, “Write Once, Run Anywhere”™ has been a success. But if the complexities of the desktop and enterprise world seem, well, complex, then the connected device world is even scarier.
    [Show full text]
  • 100% Pure Java Cookbook Use of Native Code
    100% Pure Java Cookbook Guidelines for achieving the 100% Pure Java Standard Revision 4.0 Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, California 94303 USA Copyrights 2000 Sun Microsystems, Inc. All rights reserved. 901 San Antonio Road, Palo Alto, California 94043, U.S.A. This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Restricted Rights Legend Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.227-7013 (c)(1)(ii) and FAR 52.227-19. The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications. Trademarks Sun, the Sun logo, Sun Microsystems, Java, Java Compatible, 100% Pure Java, JavaStar, JavaPureCheck, JavaBeans, Java 2D, Solaris,Write Once, Run Anywhere, JDK, Java Development Kit Standard Edition, JDBC, JavaSpin, HotJava, The Network Is The Computer, and JavaStation are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and certain other countries. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. All other product names mentioned herein are the trademarks of their respective owners. Netscape and Netscape Navigator are trademarks of Netscape Communications Corporation in the United States and other countries. THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
    [Show full text]
  • 25 GUI Components: Part 2
    25 GUI Components: Part 2 An actor entering through the door, you’ve got nothing. But if he enters through the window, you’ve got a situation. —Billy Wilder ...the force of events wakes slumberous talents. —Edward Hoagland You and I would see more interesting photography if they would stop worrying, and instead, apply horse-sense to the problem of recording the look and feel of their own era. —Jessie Tarbox Beals Objectives In this chapter you’ll learn: ■ To create and manipulate sliders, menus, pop-up menus and windows. ■ To programatically change the look-and-feel of a GUI, using Swing’s pluggable look- and-feel. ■ To create a multiple- document interface with JDesktopPane and JInternalFrame . ■ To use additional layout managers. 25.1 Introduction 1001 25.1 Introduction 25.7 JDesktopPane and 25.2 JSlider JInternalFrame 25.3 Windows: Additional Notes 25.8 JTabbedPane 25.4 Using Menus with Frames 25.9 Layout Managers: BoxLayout and 25.5 JPopupMenu GridBagLayout 25.6 Pluggable Look-and-Feel 25.10 Wrap-Up Summary | Self-Review Exercises | Answers to Self-Review Exercises | Exercises 25.1 Introduction In this chapter, we continue our study of GUIs. We discuss additional components and layout managers and lay the groundworK for building more complex GUIs. We begin our discussion with sliders that enable you to select from a range of integer values. Next, we discuss some additional details of windows. You’ll learn to use menus that enable the user to effectively perform tasKs in the program. The looK-and-feel of a Swing GUI can be uniform across all platforms on which a Java program executes, or the GUI can be customized by using Swing’s pluggable look-and-feel (PLAF ).
    [Show full text]
  • Introduction to Swing Swing API Is a Set of Extensible GUI Components to Ease the Developer's Life to Create JAVA Based Front End/GUI Applications
    Introduction to Swing Swing API is a set of extensible GUI Components to ease the developer's life to create JAVA based Front End/GUI Applications. It is build on top of AWT API and acts as a replacement of AWT API, since it has almost every control corresponding to AWT controls. Swing component follows a Model-View-Controller architecture to fulfill the following criteria:- A single API is to be sufficient to support multiple look and feel. API is to be model driven so that the highest level API is not required to have data. API is to use the Java Bean model so that Builder Tools and IDE can provide better services to the developers for use. MVC Architecture Swing API architecture follows loosely based MVC architecture in the following manner. Model represents component's data. View represents visual representation of the component's data. Controller takes the input from the user on the view and reflects the changes in Component's data. Swing component has Model as a seperate element, while the View and Controller part are clubbed in the User Interface elements. Because of which, Swing has a pluggable look-and-feel architecture. Swing Features Light Weight − Swing components are independent of native Operating System's API as Swing API controls are rendered mostly using pure JAVA code instead of underlying operating system calls. Rich Controls − Swing provides a rich set of advanced controls like Tree, TabbedPane, slider, colorpicker, and table controls. Highly Customizable − Swing controls can be customized in a very easy way as visual apperance is independent of internal representation.
    [Show full text]
  • APPENDIX a the Java API Packages
    APPENDIX A The Java API Packages The JDK provides many packages (JDK 1.1 had 26 packages) and others are being developed (such as the 2D, 3D and Media packages). You must prefIx the names of the packages in Table A.I with "java.". TABLE A.1 The Java API packages PackaKe name Contents applet Applet related classes awt Platform-independent windowing classes awt.datatransfer Support for cut and paste style operations awt.event DeleKation event model classes awt.image Image manipulation classes awt.peer Native windowing facilities classes beans Beans facilities for developers io Input and output classes lang Basic Java classes lang. reflect Java reflection classes math BigDecimal and BigInteger classes net Java networking facilities rmi Remote method invocation classes rmi.dgc Distributed garbage collection rmi.registry Facilities for mapping names to remote objects rmi.server Facilities for the server side of RMI security Java Security for signed applets security.acl Access control list security. interfaces Digital Signature Algorithm interface specifIcations sql JDBC SQL interface classes text Internationalization facilities 428 Java and Object Orientation util General utili classes util.zip Java Archive (JAR) su ort classes For further information on these packages, see books such as Chan and Lee (1996) and Gosling and Yellin (1996). APPENDIXB The java.lang Package B.l INTRODUCTION The java. lang package contains the classes and interfaces which are the basis of the Java environment (as distinct from the Java language). For example, the class Obj ect (the root of all classes) is defined in this package. This package is automatically imported into every Java program (whether it is an application or an applet).
    [Show full text]