JAVA: SWING, DOCUMENTS AND PRINTING

The programming language is Java, and the language and its syntax and semantics fills obviously much, but the books have also largely focus on the process and how to develop good and robust applications. This book deals with Swing and how to use Swing to develop applications with a graphical user interface. I have also looked at the development of programs with a graphical user interface in the book Java 2, and this book is a continuation of Java 2, but with greater emphasis on details and how Swing works internally. Several of the chapters of the book include topics that are not used so often in practical programming, but on the other hand, topics that it is necessary to know in part to solve specific problems, and partly to develop user interfaces with focus on quality. After reading the book, the reader should be able to develop and maintain complex user interfaces written using Swing. The book requires knowledge of programming and Java throughout with special introductory knowledge of Swing corresponding to the contents of the book Java 2. The book ends with the development of an application, with primary focus on the graphical user interface. As the title says this series of books deals with software development, and the goal is to teach the reader how to develop applications in Java. It can be learned by reading about the subject and by studying complete sample programs, but most importantly by yourself to do it and write your own programs from scratch. Therefore, an important part of the books is exercises and problems, where the reader has to write programs that correspond to the substance being treated in the books. All books in the series is built around the same skeleton and will consist of text and examples and exercises and problems that are placed in the text where they naturally belongs. The difference between exercises and problems is that the exercises largely deals with repetitions of the substance that is presented in the text, and furthermore it is relatively accurately described what to do. Problems are in turn more loosely described, and are typically a little bigger and there is rarely any clear best solution. These are books to be read from start to finish, but the many code examples, including exercises and problems plays a central role, and it is important that the reader predict in detail studying the code to the many examples and also solves the exercises and problems or possibly just studying the recommended solutions.