[ v1.3.5 | v1.3.4 | v1.3.3 | v1.3.2 | v1.3.1 | v1.3.0 | v1.1.10 | v1.0.11 | v1.4.x | Git | Subversion ]
Developing new FLTK applications? Use 1.3.5, the first entry in the table below. The top entry will always be the latest stable release.
Only old software should use 1.1.10, and only very old software uses 1.0.11. These older releases are end of life, and may not even compile on new platforms. Try to use 1.3; many older apps can use it with little or no change.
For more about FLTK releases and development, see this article on FLTK releases and the FLTK roadmap.
The FLTK software is available to the public via Git.
The current active development branch is FLTK 1.4, and the latest stable version is FLTK 1.3.
These can be checked out of Git using the following command:
git clone https://github.com/fltk/fltk.git
..or browsed with this URL:
For more information on using Git see the
Git Quick-Start Guide page.
Developers with write access should consult GitHub docs on how to setup
their access and/or read article #1591:
Git for FLTK Developers
for more information.
For further explanation about the different versions of FLTK
see article #825: What are the Versions of FLTK?.
NOTE: Dev snapshots of 2.x and 3.x have been disabled; use Git to access them.
The FLTK developers voted to disable snapshots of 2.x and 3.x because
app developers were still using them for production software, despite
warnings, which is bad. Only the active release stream (1.4.x) has
development snapshots now, to avoid confusion.
The previous experimental and now inactive branch is FLTK 2.0.
If you really need access, you can check this out using:
git clone https://github.com/fltk/fltk-legacy.git
..or browse with this URL:
Another previous experimental and now inactive development
branch is FLTK 3.0. It is in pre-alpha stage, but is currently dormant
and should not be used. If you really need access, you can check this
out using the above ("-legacy") command and URL and switch to branch
git checkout branch-3.0
The FLTK software is no longer available via Subversion.
Please use Git instead (see above).