Releases: Col-E/Recaf-Launcher
0.8.8 - More JFX bruh moments
This locks the upper bound of JavaFX at version 24, since in 26 (and backported to 25) they introduce new methods which break API compatibility with RichTextFX: FXMisc/RichTextFX#1282
0.8.7
0.8.6
0.8.5 - Trolled by JFX snapshot
Now we sanity check if a JFX version has artifacts for the current target platform before picking it as a candidate to update to.
0.8.4
0.8.3 - JavaFX version constraints
The launcher will now warn you if the version of JavaFX used is too new for the Java version you have selected to run Recaf with.
Pressing the update button will download the latest compatible version of JavaFX.
This is necessary as JavaFX will be taking a N-2 approach for version compatibility.
0.8.2 - Faster launching
The launcher will stick around longer while Recaf initializes in the background. If Recaf fails to launch the launcher will also stick around rather than immediately terminating.
Also, I removed the dirs.dev dependency since people complained it was slow due to its use of powershell and such. I personally haven't seen such issues, but multiple users have reported that this drops launch times from anywhere between 5-10 seconds down to 0.5 seconds.
0.8.1 - Fix script classpathing
The FX isolation from the prior release broke scripting support. This release addresses that bug.
0.8.0 - FX version handling improvements
This release changes how the launcher creates the Recaf child process, and allows us to force usage of our cached JavaFX artifacts over anything included in a JDK with bundled JavaFX classes.
Changes per #33
0.7.0 - Proper download progress display
Preview of the new feedback system:
java_ZoLnvWybia.mp4
Other changes:
- Launching Recaf now has additional sanity checks which should now alert you of configuration problems earlier on.
- All downloads are written to
.tmpfiles first, before being moved to their intended destinations.- Now you can close the launcher while updating Recaf and it will no longer break the previous version you had installed.
- JavaFX will show as being
Not installedwhen any of the 4 required artifacts are not found in the cache.- Previously, any single one existing by themselves would indicate a full install to the launcher, which was incorrect.
- JavaFX will show old versions (less than 21) as being
Outdated.- This wont prevent you from launching, but should indicate that an update is necessary.
- Removed unused blank space at the bottom of the launcher window.

