Swing look-and-feel library
Java HTML Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.settings Move project files Oct 18, 2016
drop Latest prebuilts Jan 31, 2017
lib Another round Dec 22, 2016
src Latest prebuilts Jan 31, 2017
www Updating docs Feb 8, 2017
.classpath Move project files Oct 18, 2016
.gitignore First pass for supporting high-resolution screens Oct 22, 2016
.project
README.md
build.properties
build.xml Latest prebuilts Jan 31, 2017
doc-robot-schemes.sh Another round Dec 22, 2016
doc-robot-skins.sh Another round Dec 22, 2016
doc-robot-watermarks.sh Historical snapshot Dec 21, 2010
versions.txt Latest cleanup pass Jan 14, 2017

README.md

Substance look and feel

Getting started

If you are new to Swing, start with the general Swing tutorial. If you are new to look-and-feels, read the getting started first.

To use Substance in your applications, choose one of the following options:

  • Use one of the skin-based look-and-feel classes (light or dark).
  • Extend the SubstanceLookAndFeel class and pass a SubstanceSkin instance to the super constructor.
  • Use the static setSkin(SubstanceSkin) or setSkin(String) APIs to set the specific skin.

In any case, add the latest substance.jar to your classpath.

If you wish to build Substance from the sources, you will need to also get laf-plugin and laf-widget (binaries or sources). The best way is to sync to the latest and use the build.xml script. The main test application uses the FormLayout and components from SwingLabs.

Have a question? See the FAQ and the list of known issues, and if you don't see an answer there, file a bug or get in touch.

Configure and customize

You can use Substance-specific settings and APIs to add custom functionality to your components. See detailed examples of using API calls, client properties and VM flags for more information. To control the animations, consult the animation overview.

Substance can be customized to fit your visual needs. The overall visuals are controlled by skins, with each skin defined by color scheme bundles and painters. The skinning primer has a few tips on how to use the different Substance painters in applications that wish to paint custom components in a way that is consistent with other Substance visuals. The Substance samples project provides a detailed walktrough that analyzes a complex UI mockup and uses different Substance APIs to implement it.

Plugins

While the core Swing components cover the basic UI functionality found in most applications, modern UIs need modern UI components. To address this need, Substance comes with a built-in support to allow defining and seamlessly loading plugins that provide consistent appearance and interaction for third-party components.

During the initialization, Substance looks in the classpath for the META-INF/substance-plugin.xml descriptor files. The <component-plugin-class> element should contain the fully qualified name of a class that implements the LafComponentPlugin interface. This interface defines the lifecycle of a Substance plugin, with the main extension point that allows setting custom entries in the UIManager tables.

Substance plugin for Flamingo components is the only actively developed and fully supported plugin.

Substance plugin for SwingX components has been aligned with the latest Substance sources. However, since the core SwingX project is effectively dead (last official 1.6.4 release is from July 2013), there is no more active development in that plugin.

Substance Extras pack provides additional watermarks, color schemes and skins and is another example of a Substance plugin.