Standard Widget Toolkit

Standard Widget Toolkit

The Eclipse IDE, an SWT-based application
Developer(s) Eclipse Foundation
Stable release 4.4 / June 6, 2014
Development status Active
Operating system Cross-platform
Available in Multilingual
Type Widget toolkit for the Java platform
License Eclipse Public License
Website www.eclipse.org/swt/

The Standard Widget Toolkit (SWT) is a graphical widget toolkit for use with the Java platform. It was originally developed by Stephen Northover at IBM and is now maintained by the Eclipse Foundation in tandem with the Eclipse IDE. It is an alternative to the Abstract Window Toolkit (AWT) and Swing Java GUI toolkits provided by Sun Microsystems as part of the Java Platform, Standard Edition.

To display GUI elements, the SWT implementation accesses the native GUI libraries of the operating system using JNI (Java Native Interface) in a manner that is similar to those programs written using operating system-specific APIs. Programs that call SWT are portable, but the implementation of the toolkit, despite part of it being written in Java, is unique for each platform.

The toolkit is licensed under the Eclipse Public License, an open source license approved by the Open Source Initiative.[1]

History

AWT (the Abstract Window Toolkit) was the first Java GUI toolkit, introduced with JDK 1.0 as one component of the Sun Microsystems Java platform. The original AWT was a simple Java wrapper around native (operating system-supplied) widgets such as menus, windows and buttons.

Swing was the next generation GUI toolkit introduced by Sun in J2SE 1.2. Swing was developed in order to provide a richer set of GUI components than AWT. Swing GUI elements are 100% Java with no native code: instead of wrapping native GUI components, Swing draws its own components by using Java 2D to call low level operating system drawing routines.

The roots of SWT go back to work that Object Technology International, or OTI, did in the 1990s when creating multiplatform, portable, native widget interfaces for Smalltalk (originally for OTI Smalltalk, which became IBM Smalltalk in 1993). IBM Smalltalk's Common Widget layer provided fast, native access to multiple platform widget sets while still providing a common API without suffering the "lowest common denominator" problem typical of other portable graphical user interface (GUI) toolkits. IBM was developing VisualAge, an integrated development environment (IDE) written in Smalltalk. They decided to open-source the project, which led to the development of Eclipse, intended to compete against other IDEs such as Microsoft Visual Studio. Eclipse is written in Java, and IBM developers, deciding that they needed a toolkit that had "native look and feel" and "native performance", created SWT as a Swing replacement.[2]

Design

SWT is a wrapper around native code objects, such as GTK+ objects, Motif objects etc. Because of this, SWT widgets are often referred to as "heavyweight", evoking images of a light Java wrapper around a "heavy" native object. In cases where native platform GUI libraries do not support the functionality required for SWT, SWT implements its own GUI code in Java, similar to Swing. In essence, SWT is a compromise between the low level performance and look and feel of AWT and the high level ease of use of Swing.[3][4]

According to the Eclipse Foundation, "SWT and Swing are different tools that were built with different goals in mind. The purpose of SWT is to provide a common API for accessing native widgets across a spectrum of platforms. The primary design goals are high performance, native look and feel, and deep platform integration. Swing, on the other hand, is designed to allow for a highly customizable look and feel that is common across all platforms."[5]

It has been argued that SWT features a clean design, in part inspired by Erich Gamma of Design Patterns fame.[6]

SWT is a simpler toolkit than Swing, with less (possibly) extraneous functionality for the average developer.[7] This has led some people to argue that SWT lacks functionality when compared to Swing.[8]

James Gosling, the creator of the Java language, has argued that SWT is too simple, and that SWT is a difficult toolkit to port to new platforms for the same reason that AWT used to have porting problems: that it is too simple, too low level, and too tied to the Win32 GUI API, leading to problems adapting the SWT API to other GUI toolkits, such as Motif and OS X Carbon.[7]

Although SWT does not implement the popular model–view–controller architecture used in Swing and many other high level GUI toolkits, the JFace library, which is developed as part of the same Eclipse project, does provide a platform-independent, higher-level Model-View-Controller abstraction on top of SWT. Developers may choose to use JFace to provide more flexible and abstract data models for complex SWT controls such as trees, tables and lists, or access those controls directly as needed.

Look and feel

SWT widgets have the same "look and feel" as native widgets because they often are the same native widgets. This is in contrast to the Swing toolkit where all widgets are emulations of native widgets. In some cases the difference is distinguishable. For example the OS X tree widget features a subtle animation when a tree is expanded and default buttons actually have an animated pulsing glow to focus the user's attention on them. The default Swing version of these widgets do not animate.

Since SWT is simply a wrapper around native GUI code, it does not require large numbers of updates when that native code is changed, providing that operating system vendors are careful not to break clients of their API when the operating systems are updated. The same cannot be said of Swing: Swing supports the ability to change the look and feel of the running application with "pluggable look and feels" which enable emulating the native platform user interface using themes, which must be updated to mirror operating system GUI changes (such as theme or other look and feel updates).

SWT aims for "deep platform integration", the Eclipse reference to SWT's use of native widgets. According to Mauro Marinillia of developer.com, "whenever one needs a tight integration with the native platform, SWT can be a plus".[9] This deep integration can be useful in a number of ways, for example enabling SWT to wrap ActiveX objects on Microsoft Windows.

Programming

A simple GUI application using SWT running in a GTK+ environment

The following is a basic Hello World program using SWT. It shows a window (Shell) and a label.

import org.eclipse.swt.*;
import org.eclipse.swt.widgets.*;
 
public class HelloWorld 
{
   public static void main (String[] args) 
  {
      Display display = new Display();
      Shell shell = new Shell(display);
      Label label = new Label(shell, SWT.NONE);
      label.setText("Hello World");
      label.pack();
      shell.pack();
      shell.open();
      while (!shell.isDisposed()) 
      {
         if (!display.readAndDispatch()) display.sleep();
      }
      display.dispose();
   }
}

Contrary to Swing, a Display class is necessary to access the underlying operating system, and its resources must be explicitly disposed of when they are no longer used.

Platform support

Vuze, a BitTorrent client which uses SWT, running in a GTK+ environment

SWT must be ported to every new GUI library that needs supporting. Unlike Swing and AWT, SWT is not available on every Java-supported platform since SWT is not part of the Java release. There is also some evidence that the performance of SWT on platforms other than Windows is noticeably less efficient.[8] Since SWT uses a different native library for each platform, SWT developers may be exposed to platform-specific bugs.

SWT exposes developers to more low level details than Swing. This is because SWT is technically just a layer over native library provided GUI functionality, exposing the programmer to native GUI code is part of the design intent of SWT: "Its goal is not to provide a rich user-interface design framework but rather the thinnest possible user-interface API that can be implemented uniformly on the largest possible set of platforms while still providing sufficient functionality to build rich graphical user interface (GUI) applications."[10]

Since the SWT implementation is different for each platform, a platform-specific SWT library (JAR file) must be distributed with each application.

As of March 2012, SWT supports the following platforms and/or GUI libraries:

Performance

SWT was designed to be a "high performance" GUI toolkit; faster, more responsive and lighter on system resource usage than Swing.[11]

There has been some attempted benchmarking of SWT and Swing, which concluded that SWT should be more efficient than Swing, although the applications benchmarked in this case were not complex enough to draw solid conclusions for all possible SWT or Swing uses.[12] A fairly thorough set of benchmarks concluded that neither Swing nor SWT clearly outperformed the other in the general case.[13]

Extensibility and comparison to other Java code

Due to the use of native code, SWT classes do not allow for easy inheritance for all widget classes, which some people consider can hurt extensibility.[9] This can make customizing existing widgets more difficult to achieve with SWT than if one were using Swing.[14] Both toolkits support writing new widgets using only Java code, however in SWT extra work is needed to make the new widget work on every platform.[14]

SWT widgets, unlike almost any other Java toolkit, requires manual object deallocation, as opposed to the standard Java practice of automatic garbage collection. SWT objects must be explicitly deallocated using the "dispose" method, which is analogous to the C language's "free".[15] If this is not done, memory leaks or other unintended behavior may result. On this matter, some have commented that "explicitly de-allocating the resources could be a step back in development time (and costs) at least for the average Java developer" and that "this is a mixed blessing. It means more control (and more complexity) for the SWT developer instead of more automation (and slowness) when using Swing."[9] The need for manual object deallocation when using SWT is largely due to SWT's use of native objects. As these objects are not tracked by the Java JVM, the JVM is unable to ascertain whether or not these native objects are in use, and thus unable to garbage collect them at an appropriate time.

In practice, the only SWT objects which a developer must explicitly dispose are the subclasses of Resource, such as Image, Color, and Font objects.

Development

There is some activity to enable combining Swing and SWT. There are two different approaches being attempted:

Starting in 2006 there was a SWT-3.2 port to the D programming language called DWT.[18] Since then the project supports Windows 32-bit and also Linux GTK 32-bit for SWT-3.4. The DWT project also has an addon package that contains a port of JFace and Eclipse Forms.[19]

Uses

Applications (alphabetically sorted) using SWT include:

Recent open source efforts in the eclipse community have led to a porting of SWT (and JFace) into a widget toolkit appropriate for the web. The result has been the Eclipse RAP, which combines the qooxdoo AJAX library with the SWT API. Like other Java AJAX projects (such as Echo2, Vaadin and Google Web Toolkit), the usage of the SWT API allows developers to quickly develop applications for the web in much the same way as they would for the desktop.

See also

Notes

  1. ↑ Open Source Initiative. "Licenses By Name". Retrieved 2007-03-24.
  2. ↑ "FAQ: Why does Eclipse use SWT?". Retrieved 2007-03-24.
  3. ↑ Steve Northover. "SWT: Implementation Strategy for Java Natives". Retrieved 2001-03-22.
  4. ↑ Carolyn MacLeod and Steve Northover. "SWT: Managing Operating System Resources". Retrieved 2001-11-27.
  5. ↑ "FAQ: Is SWT better than Swing?". Retrieved 2008-02-16.
  6. ↑ Ben Galbraith. "An Introduction to SWT". Retrieved 2007-03-24.
  7. ↑ 7.0 7.1 Ella Morton. "James Gosling Q & A". Retrieved 2007-03-24.
  8. ↑ 8.0 8.1 "Performance Benchmarks of Nine Languages". Retrieved 2007-03-24.
  9. ↑ 9.0 9.1 9.2 Marinilli, Mauro. "Swing and SWT: A Tale of Two Java GUI Libraries". Retrieved 2006-11-07.
  10. ↑ "FAQ What is SWT". Eclipsepedia. eclipse.org. Retrieved 2009-10-16.
  11. ↑ Akan, Ozgur (November 19, 2004). "Why I choose SWT against Swing". Retrieved 2006-11-07.
  12. ↑ "Swing vs. SWT Performance — Have a Look at the Call Stacks". Javalobby.org. 2006-03-03. Retrieved 2009-10-16..
  13. ↑ Igor, Križnar (2005-05-10). "SWT Vs. Swing Performance Comparison". cosylab.com. Retrieved 2008-05-24. It is hard to give a rule-of-thumb where SWT would outperform Swing, or vice versa. In some environments (e.g., Windows), SWT is a winner. In others (Linux, VMware hosting Windows), Swing and its redraw optimization outperform SWT significantly. Differences in performance are significant: factors of 2 and more are common, in either direction..
  14. ↑ 14.0 14.1 "Creating Your Own Widgets using SWT". eclipse.org. 2007-03-22. Retrieved 2008-12-13. Subclassing may cause bad system-level bugs, and runs the risk of leaking resources(...)Subclassing Canvas or Composite is the best way to ensure that your widget works on all SWT platforms(...)When subclassing anything other than Composite or Canvas you must override the method protected void checkSubclass() to do nothing
  15. ↑ The Java developers guide to Eclipse, 2nd ed., p359
  16. ↑ "SwingWT — The Swing/AWT API over SWT library". Swingwt.sourceforge.net. Retrieved 2009-10-16.
  17. ↑ "The SWTSwing project". Swtswing.sourceforge.net. Retrieved 2009-10-16.
  18. ↑ "DWT — Port of SWT and friends to the D programming language". Dsource.org. Retrieved 2009-10-16.
  19. ↑ "Eclipse Forms". Eclipse.org. 2005-01-16. Retrieved 2009-10-16.

References

External links