DOCSLIB.ORG

Manning Publications, Inc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Manning Publications, Inc Preface An “early technology adopter” (also known as a techno-geek) like myself is usually ready to evaluate an exciting new API the day it is released (if not sooner). In late 1994, while attending a software developers’ conference in California, I encountered a past acquaintance who, at the time, was employed by Sun Microsystems. As I am apt to do, I began complaining to him about the generally inadequate state of the business, and, in particular, the coding effort and portability weaknesses in languages such as C and C++. After listen- ing to my droning for a while, my friend told me about a particularly interest- ing programming language coming from Sun Microsystems in just a couple of months. A new language from Sun? Aren’t they a UNIX workstation com- pany? What does a hardware company know about building computer lan- guages? I was skeptical about trying to use any language produced by Sun Microsystems. The language my friend was referring to was Java 1.0, which, as he pre- dicted, was shipped at the beginning of 1995. In late January of 1995, I con- nected to Sun’s World Wide Web site, pulled down the first version of the Java Development Kit (JDK), and immediately began tinkering. Although I didn’t yet understand the overall vision of Java, I was impressed with the platform independence, and with the speed at which I could build relatively complex prototypes. In these early stages, I viewed Java as a replacement for Microsoft’s Visual Basic as a prototyping tool; however, I was soon to appreci- ate the capabilities of this new language. Java 1.0 was still far from that uto- pian software world that I was searching for, but it demonstrated some real promise as an object-oriented language, and Sun’s commitment to future xx PREFACE enhancements convinced me that Java was the language for me. In spite of the many skeptics around me, I was hooked. I continued to use Java 1.0, noting its weaknesses and doing my best to work around them. I eventually discovered some serious limitations in Java, but, when I was almost ready to give up on the language, Sun released Java 1.1 featuring a totally new event model and offering significant new features like internationaliza- tion and keyboard support. As an early technology adopter, I downloaded the 1.1 release, and my confidence in Java was renewed. Applications that crawled in the Java 1.0 Virtual Machine (VM) raced, once they were adapted to the new event model. However, like many other early adopters, I became exceedingly annoyed with the lack of power of Java’s Abstract Windowing Toolkit (AWT). Still, I per- sisted because, in my mind, Java’s potential was so great. My interest in Java continued, and, in April 1997, I attended my first JavaOne conference, quickly getting lost among the thousands of other attendees. The con- ference spanned all levels of developer expertise, and much of what I saw was famil- iar to me. However, I heard many people (mostly Sun and JavaSoft employees) talking about something code-named Swing. The (as yet) unreleased Swing was Sun’s attempt to improve Java’s AWT and standardize the user interface compo- nents for future versions of Java. Discarding my original plans for the conference, I attended every session concerning Swing so that I could learn more about Sun’s new Swing class library. Most of these sessions were primarily promotional, but a few of the Swing demos caught my eye. By June 1997, Sun finally made a public alpha release of Swing, which coincided with the start of a software project for which I wanted to employ Java. After consid- ering several user interface (UI) class libraries from third-party vendors and com- pletely disregarding Sun’s warnings that the API would change, I decided to take a big risk and use Swing for my project. Through several subsequent alpha and beta releases of Swing, my project paralleled its progress. Each time Sun offered a new release, I had to spend a day fixing my code broken by the changes they made. It was often frustrating, but I was steady in my resolve to integrate Swing into my application. My persistence paid off. My application shipped about the same time that Sun published the final release of Swing, and my work received a very positive response from my peers. While still basking in my success, I began to realize that I had invested a significant number of hours learning to make effective use of the Swing classes. So, as an early technology adopter who had successfully conquered the learning curve, I decided to share my knowledge with others, now that the Swing PREFACE xxi technology was in the mainstream. The results of my efforts are presented in this book, and it is my sincerest hope that it will help smooth out some of the bumps that developers may hit when starting to use Swing. In late February 1998, Sun shipped the finished Swing code; however, Swing is a significant part of a larger group of technologies named Java Foundation Classes (JFC). For developers using Java 1.1, JFC is available for downloading as a separate package from JavaSoft’s web site. Java 1.2 users will discover that JFC is integrated into the Java run time, so no additional installations will be required. Intended audience This book is intended to help Java developers who want to build user inter- faces with Java, regardless of their level of expertise. However, this book is not a Java tutorial, so, if you are a novice, you will certainly require some addi- tional references to assist with the basic language syntax. In the appendices of this book, you will find several good Java language resources. If you are an expert user, this book will serve as a resource which you can keep close at hand, referring to it when you hit a real snag. Regardless of your level of expertise, I will assume that you have some experience building simple applications and/or applets with version 1.1 (or later) of Java. One of the early chapters of this book is a Java AWT refresher course, but it is by no means a complete tutorial for the language. This chapter will serve only to help contrast Java, as it was with AWT, to Java as it now exists with Swing. Since the last chapter of this book will discuss optimization of Java code using multithreading, I will also assume that you have a solid understanding of how to write Java code with threads and of the inner workings of multithread- ing in general. Multithreading is a complex mechanism which can be either your most indispensable optimization tool or your worst debugging night- mare. You must use extreme caution when writing multithreaded applications, and, though we will examine multithreading from the Swing perspective, this book will not help you understand the pitfalls that multithreading can intro- duce into a Java application. Finally, I will assume that you possess a thirst to learn. Though this book will cover some advanced topics related to Swing, there will still be much to INTENDED AUDIENCE xxiii learn on your own. Swing is brimming with interesting classes that can save you hours of work, but to adequately describe each individual class would require a much larger book. Don’t be afraid to throw together some small test programs to test aspects of the Swing classes which you do not immediately understand. How this book is organized This book consists of three parts. We begin with a bit of background on Java and Swing, then look at the basic user interface functionality. Finally, we exam- ine some of the more advanced capabilities of Swing. I’ve also included a chapter to help you with optimization. The book is organized as follows: Part I contains all of the information you require to get started with Swing, including a description of the software packages you need and how to set them up. We will also have a quick Java refresher course for those who need it. Then, we will examine the architecture of Swing and start to talk about some of the advanced capabilities it offers. Part II contains details about the typical classes you will utilize in the pro- cess of creating your own Swing applications. We will look at each of the com- mon components and how to best use them, as well as techniques that can extend and enhance them to better suit your needs. In Part III, we look at more advanced topics. We will describe how to cre- ate components with a custom look-and-feel, and take a look at several ways to make your Java code run faster. NOTE: Throughout this book, you will see sections containing partial information regarding the Swing component APIs, including brief descrip- tions of the contents of significant groups of methods. Although you can find complete information in the online documentation provided with the JFC and JDK toolkits, the partial reference allows you to quickly review the API for a given class without requiring access to a computer. Conventions In order to present the information contained in this book in a consistent manner, the following conventions are used throughout: The text contains many guidelines, recommendations, and warnings to indicate where you might want to pay some special attention. For example: Though significant in scope, Swing represents only one of many parts of a larger technology group called Java Foundation Classes (JFC).
Load more

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]
  • 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]
  • 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]
  • 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]
  • 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]