Sams Teach Yourself Java 2 in 24 Hours

By Rogers Cadenhead

• Table of Contents
  • Copyright
  • About the Author
  • About the Technical Editor
  • Acknowledgments
  • We Want to Hear from You!
  • Reader Services
  • Introduction
  • Hour 1. Becoming a Programmer
  • Hour 2. Writing Your First Program
  • Hour 3. Vacationing in Java
  • Hour 4. Understanding How Java Programs Work
  • Part II: Learning the Basics of Programming
  • Hour 5. Storing and Changing Information in a Program
  • Hour 6. Using Strings to Communicate
  • Hour 7. Using Conditional Tests to Make Decisions
  • Hour 8. Repeating an Action with Loops
  • Part III: Working with Information in New Ways
  • Hour 9. Storing Information with Arrays
  • Hour 10. Creating Your First Object
  • Hour 11. Describing What Your Object Is Like
  • Hour 12. Making the Most of Existing Objects
  • Part IV: Programming a Graphical User Interface
  • Hour 13. Building a Simple User Interface
  • Hour 14. Laying Out a User Interface
  • Hour 15. Responding to User Input
  • Hour 16. Building a Complex User Interface
  • Part V: Creating Multimedia Programs
  • Hour 17. Creating Interactive Web Programs
    • Standard Applet Methods
    • Putting an Applet on a Web Page
    • A Sample Applet
    • The Java Plug-in
    • Sending Parameters from a Web Page
    • Receiving Parameters in the Applet
    • Workshop: Handling Parameters in an Applet
    • Summary
    • Q&A
    • Quiz
    • Activities
  • Hour 18. Handling Errors in a Program
  • Hour 19. Creating a Threaded Program
  • Hour 20. Reading and Writing Files
  • Part VI: Creating Multimedia Programs
  • Hour 21. Using Fonts and Color
  • Hour 22. Playing Sound Files
  • Hour 23. Working with Graphics
  • Hour 24. Creating Animation
  • Part VII: Appendixes
  • Appendix A. Tackling New Features of Java 2 Version 1.4
  • Appendix B. Using the Java 2 Software Development Kit
  • Appendix C. Programming with the Java 2 Software Development Kit
  • Appendix D. Using Sun ONE Studio
  • Appendix E. Where to Go from Here: Java Resources
  • Appendix F. This Book's Web Site

Q&A

1. Is there a reason why the CODEBASE attribute should be used in an <APPLET> or <OBJECT> tag?

   If all Java programs are grouped into their own subfolder, as indicated by CODEBASE, this structure might improve the way a Web site is organized, but there's no other reason why using CODEBASE is better than omitting it. The choice is a matter of personal preference.

2. What happens if the height and width specified for an applet don't leave enough room for the information that is displayed in the paint() method?

   The information will be drawn offscreen, beyond the edges of the applet window, and won't be visible at any point while the applet runs. Choosing the right dimensions for an applet is largely a matter of trial-and-error until you find the right size for both the HEIGHT and WIDTH attributes of the <APPLET> tag. You can't resize an applet window from within a Java program, so the only way to control its size is by using the HEIGHT and WIDTH attributes. Fortunately, you can change the Web page's HTML without having to recompile the Java program.

Share This