Core java tutorial for beginners
A tutorial blog which explains different core concepts related to Java along with programming examples

April 18, 2016 Categories: Swing. No Comments on Introduction to Swing

In this article we will look at introduction to swing which explains the importance of swings package in Java that is used to create GUIs.

 

Although Java already provides AWT for creating GUIs, due to several limitations of AWT, they developed swings package. One limitation of AWT is, AWT takes the help of native operating system to create a GUI control like button, checkbox etc. From operating system to operating system the look and feel of the component might vary. This contradicts with Java’s motto: Write Once Run Anywhere.

Java provides javax.swing package which does not need any help of the native operating system for creating GUI controls. Hence programs created using swings are portable.

awt-vs-swing

 

Features of Swings

Swings offers the following features:

Lightweight Components: The components created using swings package doesn’t need the help of native operating system. Swings is a part of Java Foundation Classes (JFC) which are purely developed in Java. Also swing components require less memory and CPU cycles than their counterpart AWT components. Hence swing components are called lightweight components.

Pluggable Look and Feel: Swings supports pluggable look and feel i.e., the appearance of a component can be separated from how the component behaves. This enables programmers to assign different look (themes) for the same component without changing its behavior.

Default look and feel of Java is metal. Java 8 also provides Nimbus look and feel. In windows operating system, windows look and feel is also available.

 

Differences between AWT and Swings

Following are the differences between AWT and Swings packages:

awt-vs-swing-differences

 

Model-View-Controller (MVC) Connection

MVC is an architectural pattern widely used in development of software. Every GUI control or component contains three aspects:

  1. The way the component looks (appearance) when rendered on the screen.
  2. The way the component reacts to the user.
  3. The state information associated with the component.

MVC can be used to separate the three aspects mentioned above. By separating them, each aspect can be modified independently without any changes to the remaining aspects.

In MVC terminology, model corresponds to the state information of a component. For example, a button might contain a field that might represent if it is pressed or released. The view corresponds to the look or appearance of the component when rendered on the screen. For example, a button is displayed as a rectangle. The controller determines how the component reacts to the user events. For example, when user presses a button, a new frame can be displayed.

The controller changes the model and the model notifies the state change to the view to be updated accordingly. Java Swings uses a modified version of MVC architecture, in which view and controller are combined into single entity called UIDelegate. This modified architecture is called as Model-Delegate architecture or Separable Model architecture.

 

Components and Containers

A swing GUI contains two main elements: components and containers. A component is an individual control like a button or label. A container is an object which can hold other components and containers.

 

Components

Swing components are derived from the class JComponent (except the four top-level containers). JComponent supports pluggable look and feel and supports the functionality common for all the components. JComponent class inherits the AWT classes Container and Component.

All swing components are represented as classes and are present in javax.swing package. Some of the components available in the Swings package are listed below:

swing-components

 

Containers

Swing provides two types of containers. First are top-level containers also called heavyweight containers. These are at the top in the containment hierarchy. The top-level containers are JFrame, JApplet, JWindow, and JDialog. All the containers inherit the AWT classes Component and Container.

Second are the lightweight containers which can be nested inside top-level containers. Lightweight containers are inherited from the class JComponent. Example of a lightweight container is JPanel.

 

Top-level Container Panes

Each top-level container defines a set of panes. At the top of the hierarchy is an instance of JRootPane. It is a lightweight container whose purpose is to manage other panes.

The panes that make up the JRootPane are: glass pane, layered pane, and content pane. The glass pane is a top level pane which lies above all components and covers all other panes. It can be used to manage mouse events over the entire container or to paint over any other component. Glass pane is a transparent instance of JPanel.

The layered pane is an instance of JLayeredPane which allows the components to be assigned a depth value (Z-order). The layered pane holds the content pane and the menu bar.

The content pane is the pane to which the visual components are added. The content pane is an opaque instance of JPanel.

 

Following are some of the swing packages:

swing-packages

 

Following code demonstrates a simple GUI application using JFrame:

Output of the above code is as shown below:

jframe-swing

 

Following code demonstrates a simple GUI application using JApplet:

Output of the above code is as shown below:

japplet-swing

Related Links:

Note: Do you have a question on this article or have a suggestion to make this article better? You can ask or suggest us by filling in the below form. After commenting, your comment will be held for moderation and will be published in 24-48 hrs.

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll Up