This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
It is better to have one nbm file that contains the SDK based on openjfx-compiler libraries for all platforms. In this case there will be only one nbm file org-netbeans-modules-javafx-sdk.nbm instead of 4 (org-netbeans-modules-javafx-sdk-mac.nbm, org-netbeans-modules-javafx-sdk-win.nbm, ...) so the final 2008-06-25_02-32-47.zip file will have smaller size.
I would agree but the SDK contains native libraries that are platform specific. At the moment, only windows version contains the libraries but it will change.
This is a good idea to have another module providing open version of JavaFX SDK for all platforms. Setting it as an enhacement.
>I would agree but the SDK contains native libraries that are platform specific. At the moment, only windows version >contains the libraries but it will change. you could deploy the system dependant natives on first module load or on demand. We use this technique to deploy JOGL+GlueGen in the NetBeans OpenGL Pack we even have to distinguish between CPU architectures. IMO it is always better to provide platform independent modules. Imagine you want to load netbeans from a USB stick or move your user folder to a different OS (I do this regularly between ubuntu and xp). native lib support module (GPL v2 + CP ex) https://netbeans-opengl-pack.dev.java.net/source/browse/netbeans-opengl-pack/trunk/native-lib-support/ the configuration for platform agnostic deployment is stored in simple xml files.
JavaFX SDK is more and more platform-dependent. We have no chance to change it.
verified
Cleaning bugzilla categories ....