Base class of all button-like widgets, such as push buttons, check boxes, and radio buttons.

An abstract action to be performed in reaction to user input. Not every action component will honor every property of its action. An action itself can generally be configured so that certain properties should be ignored and instead taken from the component directly. In the end, it is up to a component which property it uses in which way.

Clients should implement the ui field. See the SimpleApplet demo for an example. Note: Applet extends javax.swing.JApplet to satisfy Java's applet loading mechanism. The usual component wrapping scheme doesn't work here.

A container that arranges its children around a central component that takes most of the space. The other children are placed on one of four borders: north, east, south, west.

A panel that lays out its contents one after the other, either horizontally or vertically.

Default partial implementation for buffer adapters.

A button that can be clicked, usually to perform some action.

A button mutex. At most one of its associated buttons is selected at a time.

Two state button that can either be checked or unchecked.

A menu item with a check box.

Let's the user make a selection from a list of predefined items. Visually, this is implemented as a button-like component with a pull-down menu.

Base class for all UI elements that can be displayed in a window.

A UI element that can contain Components, such as windows, panels, and menus.

Used to open file dialogs.

A panel that arranges its contents horizontally, one after the other. If they don't fit, this panel will try to insert line breaks.

A text field with formatted input.

A window with decoration such as a title, border, and action buttons.

A panel that arranges its children in a grid. Layout details can be given for each cell of the grid.

A panel that lays out its contents in a uniform grid.

A label component that display either a text, an icon, or both.

A container that associates layout constraints with its children. See GridBagPanel for an example.

A component that displays a number of elements in a list. A list view does not support inline editing of items. If you need it, use a table view instead. Named ListView to avoid a clash with the frequently used scala.List

A frame that can be used for main application windows. Shuts down the framework and quits the application when closed.

A menu. Contains menu items. Being a menu item itself, menus can be nested.

A menu bar. Each window can contain at most one. Contains a number of menus.

A menu item that can be used in a menu.

An Oriented whose orientation can be changed.

Something that can have an orientation.

A component that can contain other components, such as layout panels.

A password field, that displays a replacement character for each character in the password.

A bar indicating progress of some action. Can be in indeterminate mode, in which it indicates that the action is in progress (usually by some animation) but does not indicate the amount of work done or to be done.

Notifies registered reactions when an event is published. Publishers are also reactors and listen to themselves per default as a convenience. In order to reduce memory leaks, reactions are weakly referenced by default, unless they implement Reactions.StronglyReferenced. That way, the lifetime of reactions are more easily bound to the registering object, which are reactors in common client code and hold strong references to their reactions. As a result, reactors can be garbage collected even though they still have reactions registered at some publisher, but not vice versa since reactors (strongly) reference publishers they are interested in.

A two state button that is usually used in a ButtonGroup together with other RadioButtons, in order to indicate that at most one of them can be selected.

A menu item with a radio button.

Used by reactors to let clients register custom event reactions.

The counterpart to publishers. Listens to events from registered publishers.

The root of a component hierarchy. Contains at most one component.

Can have at most a single child component, which will be put inside a canvas (the viewport) that can be scrolled.

A component that is specially suitable for being placed inside a ScrollPane.

A bar that can be used a separator, most commonly in menus.

A container that contains children in a specific sequential order.

Extend this class for most simple UI applications. Clients need to implement the top method. Framework intialization is done by this class.

Lets users select a value from a given range. Visually, this is represented as a draggable knob on a horizontal or vertical bar. Fires a ValueChanged event whenever the slider's value changes and when the knob is released.

A container with exactly two children. Arranges them side by side, either horizontally or vertically. Displays a draggable divider component between them that lets the user adjust the size ratio of the children.

Displays the contents of one of several pages at a time. For each page a tab is visible at all times. The user can click on one of these tabs to move the corresponding page to the front.

Displays a matrix of items.

A text component that allows multiline text input and display.

A component that allows some kind of text input and display.

A text component that allows single line text input and display.

A two state button with a push button like user interface. Usually used in tool bars.

The base trait of all user interface elements. Subclasses belong to one of two groups: top-level elements such as windows and dialogs, or Components.

Horizontal and vertical alignments. We sacrifice a bit of type-safety for simplicity here.

Simple predefined dialogs.

Helpers for this package.