DOCSLIB.ORG

Gadget: a Tool for Extracting the Dynamic Structure of Java Programs

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Gadget: a Tool for Extracting the Dynamic Structure of Java Programs Gadget: A Tool for Extracting the Dynamic Structure of Java Programs Juan Gargiulo and Spiros Mancoridis Department of Mathematics & Computer Science Drexel University Philadelphia, PA, USA e-mail: gjgargiu,smancori ¡ @mcs.drexel.edu Abstract Chava [6], would only reveal part of the complete design. Specifically, it would reveal the relationship between the Source code analysis and inspection does not provide client class and the Factory class but not between the client enough information to describe the structure of an object- and the objects that were created by the Factory at runtime. oriented program completely because there are components This paper describes a tool, called Gadget, to help soft- and relations that only exist during its runtime. ware engineers extract the dynamic structure of Java pro- This paper presents a tool, called Gadget, that helps grams. In the profiling phase the tool gathers runtime data software engineers extract the dynamic structure of object- from the executing program. This data captures class load- oriented programs written in the Java programming lan- ing, object creation, and method invocation events. In the guage. The tool uses program profiling, filtering, and graph analysis phase the tool uses filtering and abstraction tech- clustering techniques. niques to select classes of interest. The instances of these In this work we show how Gadget is used to analyze a classes and their runtime relations are then displayed as a standard graphical user interface library for Java, called graph. Swing. This library has a complex structure, part of which In general, one or more features of the target program is we expose using data gathered by Gadget during the execu- analyzed at a time (e.g., the Save feature of a word process- tion of a simple Java program that uses Swing. ing program). The recording of events that occur during the execution of a feature is called tracing, and the collection of trace data is called a profile. The profile is analyzed by 1. Introduction the tool and the dynamic structure of the objects and rela- tions involved in the trace is shown as a DDG (Dynamic As the size of a software system increases, so does the Dependency Graph). A DDG is a graph where nodes rep- complexity of its structure. The use of object-oriented (OO) resent classes or objects and edges represent relations (i.e., development techniques and languages helps programmers method invocation) between two objects or between a static manage this complexity by supporting data abstraction, en- class and an object. A method invocation can be an ob- capsulation, polymorphism, and reuse. However, the OO ject creation (i.e., call to a constructor method) or a sim- approach makes understanding the structure of these sys- ple method call. Gadget uses a tool from AT&T Research tems more difficult because of features such as dynamic called dotty [4] to display the DDGs. An example of a DDG binding and polymorphism. is shown in Figure 7. Understanding the dynamic structure of a system is help- Additionally, Gadget uses a clustering algorithm to par- ful during software maintenance. The dynamic structure of tition the DDGs, thus presenting the dynamic structures in an OO program shows which objects are created and what a modular fashion that is easier to understand. messages are sent between these objects at runtime. Dy- Figure 1 shows the architecture of Gadget, which con- namic analysis can be used to complement static source- sists of three main components: Control, Repository, and level inspection and analysis, which may not provide all of Profiler. The Control and Profiler components execute on the information software engineers need in order to under- different Java Virtual Machines (JVMs). The Control com- stand an OO system. For example, the Factory OO design ponent contains Gadget’s execution and analysis engines pattern [3] is used to “manufacture” objects and make these (i.e., Gadget Executor and Gadget Analyzer). The execu- objects accessible to client objects through an abstract in- tion engine is in charge of the execution of Gadget and has terface at runtime. Static analysis, using a tool such as some control of the execution of the target program being stantiation patterns during the execution of a program. His Target Application approach requires tracing the execution of the program be- ing analyzed and then visualizing the dynamic data captured Profiler by the trace. This work is concerned with searching for so- lutions to the problem of visualizing large data sets of run- SergProf JVMPI time data. It also focuses on detecting inconsistencies be- JVM2 tween the design and implementation of software systems. De Paw, Helm, Kimelman and Vlissides [12] have cre- Repository Profiling Data ated a library for extracting and animating the behavior (file) of OO systems. They present summary information about the execution of a program using a chart-like visualization. They also present techniques to instrument OO programs so Gadget Control Executor that their executions can be traced. Gadget Analyzer Richner, Duccasse and Wuyts [10] use logic program- JVM1 ming to filter data that is generated by execution traces. Their approach also requires code instrumentation. USER Shilling and Stasko [11], and later Stasko and Mukher- Figure 1. Software Architecture of Gadget. jea [9], worked on animating designs and algorithms, which can be helpful during the design process. Unlike the other analyzed. The analysis engine is in charge of managing work presented in this section, their work does not involve the analysis process logic. This includes the interaction program tracing and does not take a reverse engineering ap- with the repository and the interaction with the user inter- proach. face. Gadget’s repository is an external file that contains What distinguishes our work from the above research data about the execution of the target program. This file is the emphasis on filtering and clustering the trace data is first written by the profiler and then read by the analy- before producing design visualizations. Unlike Jerding’s sis engine. The Profiler component is in charge of running work, which tries to reduce complexity by providing better the target program through the SergProf profiling interface, visualizations, our approach attempts to reduce complexity which is our implementation of Sun Microsystem’s Java by filtering out only the runtime data that is relevant to the Virtual Machine Profiling Interface (JVMPI) [13]. SergProf program feature being analyzed. traces class loading, object allocation, method invocation and stack information at the time an object is allocated. Automatic clustering was identified by Belady and Evan- The structure of the rest of this paper is as follows: Sec- gelisti [1] as a means to produce high-level views of the tion 2 provides an overview of related research. Section 3 structure of software systems. We use the Bunch [8] clus- provides background information about the Pluggable Look tering system to group sets of objects and their interrela- and Feel (PLAF) feature of the Java Swing library. Sec- tions in order to produce a high-level “road map” of the tion 4 uses Gadget to extract the structure of the PLAF fea- dynamic software structure. Another distinguishing char- ture. This section presents the basic features of Gadget and acteristic is that our work does not rely on program in- shows screen captures of the tool, as well as the results of strumentation but rather on capturing trace data directly the PLAF feature’s analysis. Section 5 concludes with a from the Java virtual machine using the JVMPI [13]. Fi- summary of the paper, an outline of the contributions made, nally, we are treating this work as an ongoing project and a list of the limitations of the current version of Gadget. and hope to receive feedback from users. For this rea- son we provide a free copy of Gadget from our web page 2. Background (http://serg.mcs.drexel.edu/gadget) and in- tend to maintain the tool if a significant user community In this section we outline the body of work that is most materializes. closely related to the work presented in this paper. At the end of the section we state the distinguishing characteristics Before we show how Gadget is used to extract the struc- of our work. ture of Swing’s PLAF feature in Section 4, we briefly pro- Jerding’s [5] approach to supporting OO program under- vide some background material on this feature in the next standing is based on visualizing object interactions and in- section. 3. The Pluggable Look and Feel Feature of the The UI delegate is installed by the UIManager class, Swing Library which is a static class that has knowledge of the current LAF. The UIManager class makes use of the UIDe- faults class, which has methods for accessing specific Swing is a Java library to support the development of types of information about look-and-feel. The UIDe- graphical user interfaces for Java programs. One of Swing’s faults class includes, among other things, default values goals is to support multiple platforms while preserving a for presentation-related properties (such as color, font, bor- consistent look and feel. der, and icon) for each UI delegate. The Swing pluggable look-and-feel (PLAF) design is the Figure 3 shows the class diagram for a program that portion of a GUI component’s implementation that deals uses a JButton with a PLAF. This diagram describes with the presentation (the look) and event-handling (the Swing’s structure (for one component) showing the rela- feel). Note that the LAF can be changed at runtime [2]. tions between the different classes. Examples of inheritance Figure 2 shows three different GUI buttons, each with a dif- relations are the large edge relations between Motif- ferent LAF.
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]
  • 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]
  • Mac OS X for Java™ Geeks by Will Iverson
    [ Team LiB ] • Table of Contents • Index • Reviews • Reader Reviews • Errata Mac OS X for Java™ Geeks By Will Iverson Publisher : O'Reilly Pub Date : April 2003 ISBN : 0-596-00400-1 Pages : 296 Mac OS X for Java Geeks delivers a complete and detailed look at the Mac OS X platform, geared specifically at Java developers. Programmers using the 10.2 (Jaguar) release of Mac OS X, and the new JDK 1.4, have unprecedented new functionality available to them. Whether you are a Java newbie, working your way through Java Swing and classpath issues, or you are a Java guru, comfortable with digital media, reflection, and J2EE, this book will teach you how to get around on Mac OS X. You'll also get the latest information on how to build applications that run seamlessly, and identically, on Windows, Linux, Unix, and the Mac. [ Team LiB ] [ Team LiB ] • Table of Contents • Index • Reviews • Reader Reviews • Errata Mac OS X for Java™ Geeks By Will Iverson Publisher : O'Reilly Pub Date : April 2003 ISBN : 0-596-00400-1 Pages : 296 Copyright Preface Organization Conventions Used in This Book Comments and Questions Acknowledgments Chapter 1. Getting Oriented Section 1.1. All Those Confusing Names Section 1.2. Why Now? Chapter 2. Apple's Java Platform Section 2.1. Apple JVM Basics Section 2.2. Apple's JVM Directory Layout Section 2.3. Additional APIs and Services Section 2.4. Going Forward Chapter 3. Java Tools Section 3.1. Terminal Section 3.2. Code Editors Section 3.3. Jakarta Ant Section 3.4.
    [Show full text]
  • Java E La Grafica
    Linguaggi Corso di Laurea in Ingegneria delle Telecomunicazioni A.A. 2010-2011 Alessandro Longheu http://www.diit.unict.it/users/alongheu [email protected] Grafica in Java 1 A. Longheu – Linguaggi – Ing. Tlc. 2010 – 2011 Java e la grafica L’architettura Java è graphics-ready: Package java.awt il primo package grafico (Java 1.0) indipendente dalla piattaforma... o quasi! Package javax.swing Il nuovo package grafico (Java 2; preliminare da Java 1.1.6) scritto esso stesso in Java, realmente indipendente dalla piattaforma Swing definisce una gerarchia di classi che forniscono ogni tipo di componente grafico: finestre, pannelli, frame, bottoni, aree di testo, checkbox, liste a discesa, ecc. Programmazione “event-driven”: non più algoritmi stile input/elaborazione/output, ma reazione agli eventi che l’utente, in modo interattivo, genera sui componenti grafici ascoltatore degli eventi 2 Si può considerare un paradigma di programmazione a sé stante A. Longheu – Linguaggi – Ing. Tlc. 2010 – 2011 Java e la grafica: JFC Features of the Java Foundation Classes Swing GUI Includes everything from buttons to split panes to Components tables. Gives any program that uses Swing components a choice of look and feel. For example, the same Pluggable program can use either the Java or the Windows look Look-and-Feel and feel. As of v1.4.2, the Java platform supports the Support GTK+ look and feel, which makes hundreds of existing look and feels available to Swing programs. Enables assistive technologies, such as screen readers Accessibility and Braille displays, to get information from the user API interface. Enables developers to easily incorporate high-quality 2D graphics, text, and images in applications and Java 2D API applets.
    [Show full text]