Designing Applications: Tutorials

Total Page:16

File Type:pdf, Size:1020Kb

Designing Applications: Tutorials Designing Applications: Tutorials JBuilder® 2005 Borland Software Corporation 100 Enterprise Way Scotts Valley, California 95066-3249 www.borland.com Refer to the file deploy.html located in the redist directory of your JBuilder product for a complete list of files that you can distribute in accordance with the JBuilder License Statement and Limited Warranty. Borland Software Corporation may have patents and/or pending patent applications covering subject matter in this document. Please refer to the product CD or the About dialog box for the list of applicable patents. The furnishing of this document does not give you any license to these patents. COPYRIGHT © 1997–2004 Borland Software Corporation. All rights reserved. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of their respective owners. For third-party conditions and disclaimers, see the Release Notes on your JBuilder product CD. Printed in the U.S.A. JB2005designui-tutorials 6E5R0804 0405060708-987654321 PDF Contents Chapter 1 Step 15: Showing filename and state in User interface tutorials 1 the window title bar. 38 Step 16: Deploying the Text Editor application Documentation conventions . 2 to a JAR file . 41 Developer support and resources. 3 Overview . 41 Contacting Borland Developer Support . 3 Running the Archive Builder . 42 Online resources. 3 Testing the deployed application from World Wide Web . 4 the command line . 46 Borland newsgroups . 4 Modifying the JAR file and retesting Usenet newsgroups . 4 the application . 47 Reporting bugs . 4 Chapter 2 Chapter 4 Tutorial: Creating a simple Tutorial: Creating a UI with user interface 7 nested layouts 49 Step 1: Creating the UI project . 50 Creating the UI . 7 Using the Project wizard . 50 Using layouts . 8 Step 2: Generating the application source files . 51 Adjusting constraints. 9 Using the Application wizard . 51 Attaching events . 9 Step 3: Changing contentPane’s layout . 53 Chapter 3 Step 4: Adding the main panels . 54 Step 5: Creating toolbars . 56 Tutorial: Building a Java text editor 11 Step 6: Adding toolbar buttons. 57 What this tutorial demonstrates . 11 Step 7: Adding components to the Sample code for this tutorial . 12 middle panel . 59 Step 1: Setting up . 12 Step 8: Creating a status bar . 60 Creating the project . 13 Step 9: Converting to portable layouts. 61 Selecting the project’s code style options . 14 Step 10: Completing your layout. 63 Using the Application wizard. 14 Suppressing automatic hiding of JFrame . 16 Chapter 5 Setting the look and feel . 16 Tutorial: Creating a GridBagLayout Step 2: Adding a text area . 17 Step 3: Creating the menus. 20 in JBuilder 65 Step 4: Adding a FontChooser dialog. 22 Using GridBagLayout . 66 Setting the dialog’s frame and title properties . 22 What is GridBagLayout? . 67 Creating an event to launch the FontChooser . 22 What is the component’s display area?. 67 Step 5: Attaching a menu item event to the What are GridBagConstraints? . 69 FontChooser. 24 Why is GridBagLayout so complicated? . 69 Step 6: Attaching menu item events Why use GridBagLayout? . 70 to JColorChooser . 25 Simplifying GridBagLayout . 70 Step 7: Adding a menu event handler Sketch your design on paper first . 70 to clear the text area. 26 Use nested panels and layouts . 72 Step 8: Adding a file chooser dialog . 26 Use the JBuilder visual designer . 73 Internationalizing Swing components . 27 Prototype your UI in null or XYLayout . 75 Step 9: Adding code to read text from a file. 28 Creating a GridBagLayout in JBuilder . 76 Step 10: Adding code to menu items About the design . 76 for saving a file . 29 Step 1: Design the layout structure. 77 Step 11: Adding code to test if a file Step 2: Create a project for this tutorial . 81 has been modified. 31 Step 3: Add the components Step 12: Activating the toolbar buttons . 33 to the containers . 81 Specifying button tool tip text . 33 Add the main panel to the UI frame . 82 Creating the button events. 33 Create the left panel and add Creating a fileOpen() method . 34 its components. 82 Creating a helpAbout() method . 35 Create the right panel and add Step 13: Hooking up event handling to its components. 84 the text area . 36 Create the bottom panel and add Step 14: Adding a context menu to the text area . 37 its components. 85 i Step 4: Convert the upper panels Dragging the black sizing nibs into to GridBagLayout . 85 an adjacent empty cell . 106 Step 5: Convert the lower panel Adding components . 108 to GridLayout . 86 Miscellaneous tips . 109 Step 6: Convert the outer panel Switch back to XYLayout for to GridBagLayout . 86 major adjustments. 109 Step 7: Make final adjustments . 86 Remove weights and fill before making GridLayout panel . 88 adjustments . 109 Upper panels . 90 Making existing GridBagLayout code Conclusion . 94 visually designable . 110 Tips and techniques . 94 Differences in code . 110 Setting individual constraints in the designer . 94 Modifying code to work in the designer . 110 anchor . 94 Code generated by JBuilder in Part 2. 111 fill . 95 Other resources on GridBagLayout. 112 insets . 95 GridBagConstraints . 113 gridwidth, gridheight . 96 anchor . 113 ipadx, ipady . 97 fill . 113 gridx, gridy . 98 insets . 114 weightx, weighty . 98 gridwidth, gridheight . 114 Behavior of weight constraints . 99 ipadx, ipady . 115 Using drag and drop to edit constraints . 101 gridx, gridy . 115 Dragging a component to an empty cell . 102 weightx, weighty . 116 Dragging a component to Examples of weight constraints . 116 an occupied cell . 103 Dragging a large component into Index 119 a small cell . 105 ii Chapter 1 Chapter 1User interface tutorials These tutorials are designed to help you quickly get comfortable with using the visual designer. Each tutorial has a different emphasis, so you can choose the tutorial that most closely matches your needs. Here is a quick and simple tutorial to introduce you to the designer: I Chapter 2, “Tutorial: Creating a simple user interface” — Create a simple GUI, play with layouts and constraints, and hook up an event. These tutorials provide in-depth practice with important aspects of the designer: I Chapter 3, “Tutorial: Building a Java text editor” — Create and deploy a real application to load, edit, and save text files, hooking events up to buttons and menus. I Chapter 4, “Tutorial: Creating a UI with nested layouts” — Design a user interface with nested panels and layouts, converting between different layouts. I Chapter 5, “Tutorial: Creating a GridBagLayout in JBuilder” — Learn how to use GridBagLayout and GridBagConstraints. Create a GridBagLayout UI container in the designer. These tutorials assume you are familiar with Java and with the JBuilder IDE. For more information on these and other pertinent subjects, see below. See also I Java: Getting Started with Java I JBuilder IDE: “The JBuilder environment” in Getting Started with JBuilder I Using JBuilder features to improve ease of use for people with disabilities: Accessibility options section in the JBuilder Quick Tips Chapter 1: User interface tutorials 1 Documentation conventions Documentation conventions The Borland documentation for JBuilder uses the typefaces and symbols described in the following table to indicate special text. Table 1.1 Typeface and symbol conventions Typeface Meaning Bold Bold is used for java tools, bmj (Borland Make for Java), bcj (Borland Compiler for Java), and compiler options. For example: javac, bmj, -classpath. Italics Italicized words are used for new terms being defined, for book titles, and occasionally for emphasis. Keycaps This typeface indicates a key on your keyboard, such as “Press Esc to exit a menu.” Monospaced type Monospaced type represents the following: I text as it appears onscreen I anything you must type, such as “Type Hello World in the Title field of the Application wizard.” I file names I path names I directory and folder names I commands, such as SET PATH I Java code I Java data types, such as boolean, int, and long. I Java identifiers, such as names of variables, classes, package names, interfaces, components, properties, methods, and events I argument names I field names I Java keywords, such as void and static [ ] Square brackets in text or syntax listings enclose optional items. Do not type the brackets. < > Angle brackets are used to indicate variables in directory paths, command options, and code samples. JDK 5.0 uses angle brackets to denote generics. For example, <filename> may be used to indicate where you need to supply a file name (including file extension), and <username> typically indicates that you must provide your user name. When replacing variables in directory paths, command options, and code samples, replace the entire variable, including the angle brackets (< >). For example, you would replace <filename> with the name of a file, such as employee.jds, and omit the angle brackets. See “Using command-line tools” in Building Applications with JBuilder for more information. Note: Angle brackets are used in HTML, XML, JSP, and other tag-based files to demarcate document elements, such as <font color=red> and <ejb- jar>. The following convention describes how variable strings are specified within code samples that are already using angle brackets for delimiters. Italics, serif This formatting is used to indicate variable strings within code samples that are already using angle brackets as delimiters. For example, <url="jdbc:borland:jbuilder\\samples\\guestbook.jds"> ... In code examples, an ellipsis (…) indicates code that has been omitted from the example to save space and improve clarity. On a button, an ellipsis indicates that the button links to a selection dialog box. 2 Designing Applications: Tutorials Developer support and resources JBuilder is available on multiple platforms. See the following table for a description of platform conventions used in the documentation.
Recommended publications
  • Swing: Components for Graphical User Interfaces
    Swing: Components for Graphical User Interfaces Computer Science and Engineering College of Engineering The Ohio State University Lecture 22 GUI Computer Science and Engineering The Ohio State University GUI: A Hierarchy of Nested Widgets Computer Science and Engineering The Ohio State University Visual (Containment) Hierarchy Computer Science and Engineering The Ohio State University Top-level widgets: outermost window (a container) Frame, applet, dialog Intermediate widgets: allow nesting (a container) General purpose Panel, scroll pane, tabbed pane, tool bar Special purpose Layered pane Atomic widgets: nothing nested inside Basic controls Button, list, slider, text field Uneditable information displays Label, progress bar, tool tip Interactive displays of highly formatted information Color chooser, file chooser, tree For a visual (“look & feel”) of widgets see: http://java.sun.com/docs/books/tutorial/uiswing/components Vocabulary: Widgets usually referred to as “GUI components” or simply “components” History Computer Science and Engineering The Ohio State University Java 1.0: AWT (Abstract Window Toolkit) Platform-dependent implementations of widgets Java 1.2: Swing Most widgets written entirely in Java More portable Main Swing package: javax.swing Defines various GUI widgets Extensions of classes in AWT Many class names start with “J” Includes 16 nested subpackages javax.swing.event, javax.swing.table, javax.swing.text… Basic GUI widgets include JFrame, JDialog JPanel, JScrollPane, JTabbedPane,
    [Show full text]
  • View of XML Technology
    AN APPLICATION OF EXTENSlBLE MARKUP LANGUAGE FOR INTEGRATION OF KNOWLEDGE-BASED SYSTEM WITH JAVA APPLICATIONS A Thesis Presented to The Faculty of the Fritz J. and Dolores H. Russ College of Engineering and Technology Ohio University In Partial Fulfillment of the Requirement for the Degree Master of Science BY Sachin Jain November, 2002 ACKNOWLEDGEMENTS It is a pleasure to thank the many people who made this thesis possible. My sincere gratitude to my thesis advisor, Dr. DuSan Sormaz, who helped and guided me towards implementing the ideas presented in this thesis. His dedication to research and his effort in the development of my thesis was an inspiration throughout this work. The thesis would not be successful without other members of my committee, Dr. David Koonce and Dr. Constantinos Vassiliadis. Special thanks to them for their substantial help and suggestions during the development of this thesis. I would like also to thank Dr. Dale Masel for his class on guidelines for how to write thesis. Thanlts to my fellow colleagues and members of the lMPlanner Group, Sridharan Thiruppalli, Jaikumar Arumugam and Prashant Borse for their excellent cooperation and suggestions. A lot of infom~ation~1sef~11 to the work was found via the World Wide Web; 1 thank those who made their material available on the Web and those who kindly responded back to my questions over the news-groups. Finally, it has been pleasure to pursue graduate studies at IMSE department at Ohio University, an unique place that has provided me with great exposures to intricacies underlying development, prograrn~ningand integration of different industrial systems; thus making this thesis posslbie.
    [Show full text]
  • Programming Java for OS X
    Programming Java for OS X hat’s so different about Java on a Mac? Pure Java applica- tions run on any operating system that supports Java. W Popular Java tools run on OS X. From the developer’s point of view, Java is Java, no matter where it runs. Users do not agree. To an OS X user, pure Java applications that ignore the feel and features of OS X are less desirable, meaning the customers will take their money elsewhere. Fewer sales translates into unhappy managers and all the awkwardness that follows. In this book, I show how to build GUIs that feel and behave like OS X users expect them to behave. I explain development tools and libraries found on the Mac. I explore bundling of Java applications for deployment on OS X. I also discuss interfacing Java with other languages commonly used on the Mac. This chapter is about the background and basics of Java develop- ment on OS X. I explain the history of Java development. I show you around Apple’s developer Web site. Finally, I go over the IDEs commonly used for Java development on the Mac. In This Chapter Reviewing Apple Java History Exploring the history of Apple embraced Java technologies long before the first version of Java on Apple computers OS X graced a blue and white Mac tower. Refugees from the old Installing developer tan Macs of the 1990s may vaguely remember using what was tools on OS X called the MRJ when their PC counterparts were busy using JVMs. Looking at the MRJ stands for Mac OS Runtime for Java.
    [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]
  • Jquery: Animations
    jQuery: Animations ATLS 3020 - Digital Media 2 Week 9 - Day 2 jQuery Overview ● All HTML must be valid! ● Define elements in HTML ● Styling and presentation in CSS ● Add interactivity with javascript/jQuery jQuery Overview All jQuery must go inside of $(document).ready(function(){}) HTML <head> // meta, title, css <script src="http://ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js"> </script> <script> $(document).ready(function() { // your javascript and jQuery code goes here }); </script> </head> jQuery Overview You can only add jQuery variables with jQuery methods and javascript variables with javascript methods Javscript We have a function that changes function change_color() { the color of an element: // changes the color of something } We can use ONE of the two options. We cannot combine document.getElementById() with the click method. And we cannot combine $(selector) with the onclick method. Javscript jQuery var button; $("#button").click(change_color); button = document.getElementById("button"); button.onclick(change_color); Some jQuery animations jQuery Makes a hidden element fade into view $("#banner").fadeIn(); jQuery Hides an element by fading it out $("#banner").fadeOut(); jQuery Makes a visible element side out of view $("#banner").slideUp(); jQuery $("#banner").slideDown(); Makes a hidden element slide into view jQuery Alternates between hiding and showing the $("#banner").toggle(); “banner” id jQuery Alternates between hiding and showing the $("#banner").slideToggle(); “banner” id, while sliding in and out jQuery and CSS We can also edit CSS directly with jQuery: $(selector).css("property", "value"); jQuery $("#banner").css("font-size", "100px"); Changes the font-size of the banner element jQuery $("#banner").css("color", "#00f"); Changes the font color of the banner element Or change multiple properties at once: $(selector).css({ "attribute", "value", jQuery "attribute", "value" }); $("#banner").css({ "font-size", "100px", "color", "#00f" }); Exercise (pairs) 1.
    [Show full text]
  • The Abstract Window Toolkit (AWT), from Java
    Components Containers and Layout Menus Dialog Windows Event Handling The Abstract Window Toolkit (AWT), from Java : Abstract Window Toolkit Interface to the GUI Interface to platform's components: Layout: Placing GUI event keyboard, window system Buttons, text components handling mouse, … (Win, Mac, …) fields, … Uses operating system components Don't use these! . Looks like a native application . One must sometimes be aware of differences between operating systems… . Small set of components . , … – no table, no color chooser, … The Java Foundation Classes, from Java : Java Foundation Classes (JFC) Java : AWT, Swing More advanced Abstract Window Toolkit graphics classes Components based on pure Java "Painting on the screen" . Won't always look "native”, . The basis of Swing but works identically on all platforms components – and your own . Replaces AWT components, adds more . Discussed next lecture . We still use many other parts of AWT Components: JTable, JButton, … extending JComponent Containers: JFrame – a top level window; JPanel – a part of a window, grouping some components together Layout Managers: Decide how to place components inside containers Swing: Can replace the look and feel dynamically . Nimbus (current Java standard) . Metal (earlier Java standard) . Windows classic Running example: A very simple word processor Ordinary window in Swing: JFrame . A top-level container: Not contained in anything else ▪ AWT Base class for all Swing components Common implementation details Has two states, on/off Radio buttons: Only one per Standard button active at a time Checkbox, on / off Editing styled text: Abstract base class, HTML, RTF, common functionality custom formats A single line of text Multi-line text area Special formatting for Passwords are not shown dates, currency, … as they are entered .
    [Show full text]
  • Swingstates: Adding State Machines to Java and the Swing Toolkit Caroline Appert, Michel Beaudouin-Lafon
    SwingStates: Adding state machines to Java and the Swing toolkit Caroline Appert, Michel Beaudouin-Lafon To cite this version: Caroline Appert, Michel Beaudouin-Lafon. SwingStates: Adding state machines to Java and the Swing toolkit. Software: Practice and Experience, Wiley, 2008, 38 (11), pp.1149-1182. 10.1002/spe.867. inria-00538334 HAL Id: inria-00538334 https://hal.inria.fr/inria-00538334 Submitted on 25 Nov 2010 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. SwingStates: Adding state machines to Java and the Swing toolkit C. Appert∗ and M. Beaudouin-Lafon LRI (Universit´eParis-Sud & CNRS), INRIA, bˆat 490, 91405 Orsay, France. SUMMARY This article describes SwingStates, a Java toolkit designed to facilitate the development of graphical user interfaces and bring advanced interaction techniques to the Java platform. SwingStates is based on the use of finite-state machines specified directly in Java to describe the behavior of interactive systems. State machines can be used to redefine the behavior of existing Swing widgets or, in combination with a new canvas widget that features a rich graphical model, to create brand new widgets. SwingStates also supports arbitrary input devices to implement novel interaction techniques based, for example, on bi-manual or pressure-sensitive input.
    [Show full text]
  • GUI Programming in Java Using Swing  Junit Testing Exercise Is Due Now
    GUI programming in Java Using Swing JUnit Testing exercise is due now. Turn in your written problems from Assignment 6. You should be done BigRational, but I’ll extend due date until next class, so you can add extra unit tests or documentation. Try to finish earlier so you can get an early day and start GUI programming! Any questions about course material? Python provides an extensive GUI toolkit called Tkinter, which is built on top of the (not specific to Python) Tcl/Tk framework. ◦ http://www.python.org/doc/life-preserver/ ◦ www.tcl.tktktktk/software/tcltktktktk/ ◦ http://en.wikipedia.org/wiki/Tk_(computing) In CSSE120, we did not use Tkinter directly Instead used ZelleGraphics ◦ a simplified collection of classes for drawing on the screen. ◦ Hides details that would be confusing to beginners in OOP. In Java, we'll see "the real thing": Swing Appendices in the Weiss book (sketchy). Java Swing by Cole, Eckstein, et. al . ◦ This is a great Swing resource (for both learning and reference): ◦ Available for you to read on Safari Tech Books Online http://proquest.safaribooksonline.com/?uicode=rosehulman Then find the Java Swing book If that link does not work for you, go to the Logan Library page, and choose Safari from the Databases drop-down list near the top of the page, then click GoGoGo.Go SUN's Swing Tutorial at http://java.sun.com/docs/ books/tutorial/uiswing/index.html ◦ This one has great examples, but it tends to assume a deeper familiarity with Java than most of you have now. AWT (Abstract Windowing Toolkit) was part of the original Java release ◦ Many features are still used ◦ But users were dissatisfied … Swing was standardized with Java 2 (1999) ◦ The most widely used Java GUI toolkit.
    [Show full text]
  • Classjs Documentation Release 1.0
    classjs Documentation Release 1.0 Angelo Dini March 21, 2015 Contents 1 Requirements 3 2 Plugins 5 2.1 Cl.Accordion...............................................5 2.2 Cl.Autocomplete.............................................7 2.3 Cl.Carousel................................................8 2.4 Cl.Debug................................................. 10 2.5 Cl.Gallery................................................ 11 2.6 Cl.Lightbox................................................ 13 2.7 Cl.Mobilemenu.............................................. 16 2.8 Cl.Uniform................................................ 18 i ii classjs Documentation, Release 1.0 These plugins are aimed for professionals with extensive JavaScript knowledge. Each plugin follows a simplistic and a modular approach. All plugins have demos, tests and documentation regarding their options, methods, events and callbacks. The plugins are compatible with Firefox, Chrome, Safari and IE7+. We also support iOS, Android and Windows Phone to insure correct responsive behaviour with full accessible support according to the WCAG 2.0 standards. Each plugin requires at least class.js 1.0+ and jQuery 1.7+. The latest stable versions are available on github - https://github.com/finalangel/classjs-plugins Contents 1 classjs Documentation, Release 1.0 2 Contents CHAPTER 1 Requirements For additional information on how to run documentation or the examples locally, consult the docs/README.rst or the demo page’s FAQ section: http://finalangel.github.io/classjs-plugins/ 3 classjs Documentation, Release 1.0 4 Chapter 1. Requirements CHAPTER 2 Plugins 2.1 Cl.Accordion This is a list of all relevant options, methods, events and callbacks. 2.1.1 Options Options are set on initializing the accordion: new Cl.Accordion({ // your options ’index’:0, ’event’: ’mouseenter’ }); Option De- Description fault index null shows selected element[index] starting form zero.
    [Show full text]
  • 2008 Packt Publishing
    Swing Extreme Testing The Extreme Approach to Complete Java Application Testing Tim Lavers Lindsay Peters BIRMINGHAM - MUMBAI Swing Extreme Testing Copyright © 2008 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author(s), Packt Publishing, nor its dealers or distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: May 2008 Production Reference: 1260508 Published by Packt Publishing Ltd. 32 Lincoln Road Olton Birmingham, B27 6PA, UK. ISBN 978-1-847194-82-4 www.packtpub.com Cover Image by Vinayak Chittar ([email protected]) Credits Authors Project Manager Tim Lavers Abhijeet Deobhakta Lindsay Peters Project Coordinator Reviewers Lata Basantani Prabhakar Chaganti Valentin Crettaz Indexer Hemangini Bari Senior Acquisition Editor David Barnes Proofreader Angie Butcher Development Editor Ved Prakash Jha Production Coordinator Aparna Bhagat Technical Editor Himanshu Panchal Cover Work Aparna Bhagat Editorial Team Leader Mithil Kulkarni About the Authors Tim Lavers is a Senior Software Engineer at Pacific Knowledge Systems, which produces LabWizard, the gold-standard for rules-based knowledge acquisition software.
    [Show full text]
  • Introduction to Swing (PDF)
    1.00 Lecture 17 Introduction to Swing Reading for next time: Big Java: sections 9.7-9.11 Online hyperlinked Swing tutorial: http://download.oracle.com/javase/tutorial/uiswing/ Swing • Java package of user interface classes for windows, menus, scroll bars, buttons, drawing... • Independent of hardware and operating system (as long as they can paint a window) – Swing gains independence but loses performance by not relying on native drawing calls – Has Windows, Mac, other look and feel options • Supersedes Java Abstract Window Toolkit (AWT) though it still uses many non-drawing classes from that package. You will usually: import java.awt.*; import javax.swing.*; 1 The 3 Flavors of GUI Objects • Top Level Windows: – Containers that are not contained by any other containers – They can be iconified or dragged, and interact with the native windowing system – Example: JFrame, JDialog • JComponents: present information or interact with the user – Examples: labels (JLabel), buttons (JButton), text fields (JTextField) – JFrame and JDialog are not JComponents • Containers: – Some JComponents are designed to hold other components, not to present info or interact with the user – Examples: JPanel , JScrollPane, Container Anatomy of a JFrame Look and Feel, platform dependent Interacts with the window system JFrame has a contentPane, which is the Container that will hold your content © Oracle. All rights reserved. This content is excluded from our Creative Commons license. For more information, see http://ocw.mit.edu/fairuse. 2 Coordinates 0,0 y Screen
    [Show full text]
  • Learning Core Audio: a Hands-On Guide to Audio Programming For
    Learning Core Audio "EEJTPO8FTMFZ -FBSOJOH 4FSJFT 7JTJU LQIRUPLWFRPOHDUQLQJVHULHV GPS B DPNQMFUF MJTU PG BWBJMBCMF QVCMJDBUJPOT 5IF $GGLVRQ:HVOH\ /HDUQLQJ 6HULHV JTBDPMMFDUJPOPGIBOETPOQSPHSBNNJOH HVJEFT UIBU IFMQ ZPV RVJDLMZ MFBSO B OFX UFDIOPMPHZ PS MBOHVBHF TP ZPV DBO BQQMZXIBUZPVWFMFBSOFESJHIUBXBZ &BDI UJUMF DPNFT XJUI TBNQMF DPEF GPS UIF BQQMJDBUJPO PS BQQMJDBUJPOT CVJMUJO UIF UFYU 5IJT DPEF JT GVMMZ BOOPUBUFE BOE DBO CF SFVTFE JO ZPVS PXO QSPKFDUT XJUIOPTUSJOHTBUUBDIFE.BOZDIBQUFSTFOEXJUIBTFSJFTPGFYFSDJTFTUP FODPVSBHFZPVUPSFFYBNJOFXIBUZPVIBWFKVTUMFBSOFE BOEUPUXFBLPS BEKVTUUIFDPEFBTBXBZPGMFBSOJOH 5JUMFTJOUIJTTFSJFTUBLFBTJNQMFBQQSPBDIUIFZHFUZPVHPJOHSJHIUBXBZBOE MFBWF ZPV XJUI UIF BCJMJUZ UP XBML PGG BOE CVJME ZPVS PXO BQQMJDBUJPO BOE BQQMZ UIFMBOHVBHFPSUFDIOPMPHZUPXIBUFWFSZPVBSFXPSLJOHPO Learning Core Audio A Hands-On Guide to Audio Programming for Mac and iOS Chris Adamson Kevin Avila Upper Saddle River, NJ • Boston • Indianapolis • San Francisco New York • Toronto • Montreal • London • Munich • Paris • Madrid Cape Town • Sydney • Tokyo • Singapore • Mexico City Many of the designations used by manufacturers and sellers to distinguish their products Editor-in-Chief are claimed as trademarks. Where those designations appear in this book, and the publish- Mark Taub er was aware of a trademark claim, the designations have been printed with initial capital Senior Acquisitions letters or in all capitals. Editor The authors and publisher have taken care in the preparation of this book, but make no Trina MacDonald expressed or implied warranty
    [Show full text]