Organization

Approach(es)

The Java platform, now in version 1.5 (Java 5) is so complex that any text or trade book that attempts a broad coverage of the topic must employ a multitude of approaches. The many approaches employed in Java For Artists include the following:

Say what we’re gonna say; say it; then say what we said:   This approach is supported by the copious use of chapter learning objectives, chapter introductions, quick review sections, and comprehensive summaries.

Test to the learning objectives:   The material presented in each chapter is reinforced by end-of-chapter skillbuilding exercises, suggested projects, and self-test questions.

Repeat, repeat, repeat:   If we think something is especially important we will present it to you in several different ways in different chapters in the book.

Illustrate, illustrate, illustrate:   Pictures are worth a thousand words. To this end we tried to illustrate difficult concepts graphically where possible.

Demonstrate, demonstrate, demonstrate:   The results of running almost every programming example in this book are shown via a screen or console capture. The relationship between what you see in the code and what you see as a result of running the code is clearly explained.

Every programming example must work as advertised:   Nothing is more frustrating to a beginner than to enter a source code example from a book and try to compile it only to find that it doesn’t work. All source code in this book is compiled and tested repeatedly before being cut and pasted into the page layout software. Line numbers are automatically added so humans don’t mess things up.

Show real-world examples:   The later programming examples in this book are more complex than any provided in any competing Java text book. This approach is necessary to push you past the stage of simplistic Java programming.

Show complete examples:   At the risk of having too much source code we chose to provide complete examples to preserve the context of the code under discussion.

Include coverage of Java 1.4 and Java 5 programming techniques:   Although the Java platform has evolved, students should be still be exposed to Java 1.4 programming techniques for the simple fact that they may find themselves maintaining legacy Java code. It’s too early for textbooks to focus exclusively on Java 5. A student who understands Java 1.4 programming techniques will find it easier to make the move to Java 5 rather than the other way around.

Offer an advanced treatment of object-oriented design principles:   Students are better prepared to tackle complex projects when they’ve been introduced to advanced object-oriented programming concepts. If they try and design without it they are shooting from the hip.