makes Java even more fun

Project maintained by CodeFX-org Hosted on GitHub Pages — Theme by mattgraham


LibFX has no strict goal for a feature set. It collects functionality I created for my use in other projects but are abstract enough to be generally helpful. Many will revolve around JavaFX (hence the name).

This somewhat vague sentiment does not translate to quality! The code is clean, which especially includes thorough testing. It is also extensively documented and contains many examples. Bugs will be addressed quickly and feature requests as well as forks and pull requests are welcome.


These features are present in the latest release:





The best documentation are the tests. But understandably nobody wants to dig into them just to understand what the classes do so there are also examples and extensive Javadoc. The best way to get to know a feature is to check out the corresponding article in the wiki. It will include a high level explanation as well as links to demos and the best entry point into the documentation. The Javadoc of the current version is published here.

If anything is missing or an explanation proves to be unhelpful, contact me (see below).


License details can be found in the LICENSE file in the project's root folder. The information provided there is binding but the gist is: LibFX is licensed under the GPL but if that does not suit your licensing model, other arrangements are possible (contact me; see below).


Releases are published on GitHub. The release notes also contain a link to the artifact in Maven Central and its coordinates.

The current version is 0.3.0:




    compile 'org.codefx.libfx:LibFX:0.3.0'


Some information about how this library is developed:


The best starting point to everything regarding LibFX is

The library has its home on GitHub where the following features are especially noteworthy:

I have a blog at where I might occasionally blog about LibFX. Those posts are filed under their own tag.

I use Eclipse and my project settings (like compiler warnings, formatter and save actions) can be found in the repository folder .settings. I know this is a little unusual but it makes it easier for contributors to cope with my obsession for warning free and consistently formatted code.


Nicolai Parlog