Preface
Source Code
In addition to the new components, Swing makes three major improvements on the AWT.
- It's written entirely in Java, and creates its own components. This new approach should solve the portability problem.
- It's in control of the way components look on the screen, and gives you more control of how your applications look.
- Swing makes a very clear distinction between the data a component displays (the "model") and the actual display (the "view").
Chapter 1
Swing actually makes use of a simplified variant of the MVC design called the model-delegate. This design combines the view and the controller object into a single element that draws the component to the screen and handles GUI events known as the UI delegate.
Each Swing component contains a model and a UI delegate. The model is responsible for maintaining information about the component's state. The UI delegate is responsible for maintaining information about how to draw the component on the screen. In addition, the UI delegate (in conjunction with AWT) reacts to various events that propagate through the component.
Chapter 2
A JFrame has something in it called a "content pane"; when we add something to a JFrame, we usually want to add it to this content pane:
getContentPane().add(something);
In order to run the sample code ToolbarFrame4.java in Eclipse, you will have to move the image files to a separate folder in the project:
Internal frame