Top Qs
Timeline
Chat
Perspective

List of widget toolkits

From Wikipedia, the free encyclopedia

Remove ads

This article provides a list of widget toolkits (also known as GUI frameworks), used to construct the graphical user interface (GUI) of programs, organized by their relationships with various operating systems.

Low-level widget toolkits

Integrated in the operating system

  • Mac OS X uses Cocoa. Mac OS 9 and Mac OS X used to use Carbon for 32-bit applications.
  • The Windows API used in Microsoft Windows. Microsoft had the graphics functions integrated in the kernel until 2006[1]
  • The Haiku operating system uses an extended and modernised version of the Be API that was used by its predecessor BeOS. Haiku is expected to drop binary and source compatibility with BeOS at some future time, which will result in a Haiku API.

As a separate layer on top of the operating system

  • The X Window System contains primitive building blocks, called Xt or "Intrinsics", but they are mostly only used by older toolkits such as: OLIT, Motif and Xaw. Most contemporary toolkits, such as GTK or Qt, bypass them and use Xlib or XCB directly.
  • The Amiga OS Intuition was formerly present in the Amiga Kickstart ROM and integrated itself with a medium-high level widget library which invoked the Workbench Amiga native GUI. Since Amiga OS 2.0, Intuition.library became disk based and object oriented. Also Workbench.library and Icon.library became disk based, and could be replaced with similar third-party solutions.
  • Since 2005, Microsoft has taken the graphics system out of Windows' kernel.[2]
Remove ads

High-level widget toolkits

Summarize
Perspective
More information Toolkit name, Windows ...

OS dependent

On Amiga

  • BOOPSI (Basic Object Oriented Programming System for Intuition) was introduced with OS 2.0 and enhanced Intuition with a system of classes in which every class represents a single widget or describes an interface event. This led to an evolution in which third-party developers each realised their own personal systems of classes.
  • MUI: object-oriented GUI toolkit and the official toolkit for MorphOS.
  • ReAction: object-oriented GUI toolkit and the official toolkit for AmigaOS.
  • Zune (GUI toolkit) is an open source clone of MUI and the official toolkit for AROS.

On macOS

On Microsoft Windows

On Unix, under the X Window System

Note that the X Window System was originally primarily for Unix-like operating systems, but it now runs on Microsoft Windows as well using, for example, Cygwin, so some or all of these toolkits can also be used under Windows.

Cross-platform

Based on C (including bindings to other languages)

Based on C++ (including bindings to other languages)

Based on Python

Based on Flash

  • Adobe Flash allows creating widgets running in most web browsers and in several mobile phones.
  • Adobe Flex provides high-level widgets for building web user interfaces. Flash widgets can be used in Flex.
  • Flash and Flex widgets will run without a web browser in the Adobe AIR runtime environment.

Based on Go

  • Fyne, open source (BSD) is inspired by the principles of Material Design to create applications that look and behave consistently across Windows, macOS, Linux, BSD, Android and iOS.

Based on XML

Based on JavaScript

General

RIAs

Full-stack framework

Resource-based

No longer developed

  • YUI (Yahoo! User Interface Library)

Based on SVG

  • Raphaël is a JavaScript toolkit for SVG interfaces and animations

Based on C#

  • Gtk#, C# wrappers around the underlying GTK and GNOME libraries, written in C and available on Linux, MacOS and Windows.
  • QtSharp, C# wrappers around the Qt widget toolkit, which is itself based-on the C++ language.
  • Windows Forms. There is an original Microsoft's implementation that is a wrapper around the Windows API and runs on windows, and Mono's alternative implementation that is cross platform.

Based on Java

  • The Abstract Window Toolkit (AWT) is Sun Microsystems' original widget toolkit for Java applications. It typically uses another toolkit on each platform on which it runs.
  • Swing is a richer widget toolkit supported since J2SE 1.2 as a replacement for AWT widgets. Swing is a lightweight toolkit, meaning it does not rely on native widgets.
  • Apache Pivot is an open-source platform for building rich web applications in Java or any JVM-compatible language, and relies on the WTK widget toolkit.
  • JavaFX and FXML.
  • The Standard Widget Toolkit (SWT) is a native widget toolkit for Java that was developed as part of the Eclipse project. SWT uses a standard toolkit for the running platform (such as the Windows API, macOS Cocoa, or GTK) underneath.
  • Codename One originally designed as a cross platform mobile toolkit it later expanded to support desktop applications both through JavaSE and via a JavaScript pipeline through browsers
  • java-gnome provides bindings to the GTK toolkit and other libraries of the GNOME desktop environment
  • Qt Jambi, the official Java binding to Qt from Trolltech. The commercial support and development has stopped[5]

Based on Object Pascal

  • FireMonkey or FMX is a cross-platform widget and graphics library distributed with Delphi and C++Builder since version XE2 in 2011. It has bindings for C++ through C++Builder, and supports Windows, macOS, iOS, Android, and most recently Linux. FireMonkey supports platform-native widgets, such as a native edit control, and custom widgets that are styled to look native on a target operating system. Its graphics are GPU-accelerated and it supports styling, and mixing its own implementation controls with native system controls, which lets apps use native behaviour where it's important (for example, for IME text input.)
  • IP Pascal uses a graphics library built on top of standard language constructs. Also unusual for being a procedural toolkit that is cross-platform (no callbacks or other tricks), and is completely upward compatible with standard serial input and output paradigms. Completely standard programs with serial output can be run and extended with graphical constructs.
  • Lazarus LCL (for Pascal, Object Pascal and Delphi via Free Pascal compiler), a class library wrapping GTK+ 1.2–2.x, and the Windows API (Carbon, Windows CE and Qt4 support are all in development).
  • fpGUI is created with the Free Pascal compiler. It doesn't rely on any large 3rdParty libraries and currently runs on Linux, Windows, Windows CE, and Mac (via X11). A Carbon (macOS) port is underway.
  • CLX (Component Library for Cross-platform) was used with Borland's (now Embarcadero's) Delphi, C++ Builder, and Kylix, for producing cross-platform applications between Windows and Linux. It was based on Qt, wrapped in such a way that its programming interface was similar to that of the VCL toolkit. It is no longer maintained and distributed, and has been replaced with FireMonkey, a newer toolkit also supporting more platforms, since 2011.

Based on Objective-C

Based on Dart

Based on Swift

Based on Ruby

Remove ads

Not yet categorised

Comparison of widget toolkits

More information Toolkit, Initial release ...
Remove ads

See also

References

Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.

Remove ads