diff --git a/java/libraries/javafx/build.xml b/java/libraries/javafx/build.xml
index 3161d5238..6c23dea3a 100644
--- a/java/libraries/javafx/build.xml
+++ b/java/libraries/javafx/build.xml
@@ -85,20 +85,25 @@
          dest="${gluon.base}.zip"
          usetimestamp="true" />
 
-    <available file="${library.path}/javafx.base.jar"
+<!--     <available file="${library.path}/javafx.base.jar"
                property="javafx.jars.exist" />
-
+ -->
     <antcall target="unzip-gluon-jars" />
     <antcall target="unzip-gluon-natives" />
   </target>
 
   <!-- extract the .jar files from the first javafx we run across -->
-  <target name="unzip-gluon-jars" unless="${javafx.jars.exist}">
+  <!-- <target name="unzip-gluon-jars" unless="${javafx.jars.exist}"> -->
+  <target name="unzip-gluon-jars">
     <echo message="Extracting jars from ${gluon.base}.zip" />
     <!-- should javafx.properties be copyed? is it used for anything? [fry 210620] -->
 
     <!-- https://ant.apache.org/manual/Tasks/unzip.html -->
-    <unzip dest="${library.path}" src="${gluon.base}.zip" overwrite="true">
+    <!-- <unzip dest="${library.path}" src="${gluon.base}.zip" overwrite="true"> -->
+    <!-- !#($*#! the builds have *slightly* different classes in each release
+         (WinPlatformFactory not in macOS .jar... FFS it 1100 bytes of glue code)
+         So the .jar files go into the native subdirectories as well. -->
+    <unzip dest="${natives.path}" src="${gluon.base}.zip" overwrite="true">
       <patternset>
         <include name="**/*.jar" />
         <!-- These two aren't supported/used -->
diff --git a/todo.txt b/todo.txt
index 9c14389c4..478360f8b 100755
--- a/todo.txt
+++ b/todo.txt
@@ -39,18 +39,29 @@ X   https://github.com/processing/processing4/issues/210
 X move JavaFX to its own library, too many weird quirks that it includes
 o   build bits should be in core/build.xml or javafx/build.xml
 X   by moving it out, all the strangeness of download and import is outside core
+X add JavaFX library to IntelliJ
+X #@$*$& the JavaFX jars are ever-so-slightly different between platforms
 
-_ "WARNING: Unsupported JavaFX configuration" when running Tools that use JavaFX
-_   we were probably spared the warnings because the older JARs were hanging around
 
-_ add JavaFX library to IntelliJ
+for next release
+_ debug JavaFX and Export to Application on Windows
+_   this was working on Saturday, now broken after the move to a separate library
+_ debug JavaFX and Export to Application on Linux
+_ Code completion not working
+_   https://github.com/processing/processing4/issues/177
+_   confirmed not working from Sam's repo either
+
+
+_ lots more cleanup to do in javafx/build.xml
 
 _ macosx vs macosx64 in JavaFX
 _   the latter is making the export fail because it won't embed a Java VM
 _   may be because it's exporting twice and overwriting? or 64 takes precedence?
 
 _ fix modules path warning for Tools in the PDE
-_ update for new modules path when running from the PDE
+_   "WARNING: Unsupported JavaFX configuration" when running Tools that use JavaFX
+_   we were probably spared the warnings because the older JARs were hanging around
+
 _ update modules path when exporting application
 
 _ automatically import JavaFX if FX2D is in sketch? or tell user?
@@ -61,13 +72,6 @@ _ Only specify --modules-path when running JavaFX apps
 _   https://github.com/processing/processing4/issues/209
 
 
-for next release
-_ debug JavaFX and Export to Application on Linux
-_ Code completion not working
-_   https://github.com/processing/processing4/issues/177
-_   confirmed not working from Sam's repo either
-
-
 may be fixed
 _ Undo feature may have undesired results (4.0a4)
 _   https://github.com/processing/processing/issues/4775