Re: bringing an old javafx RCP project into the modern era

Hi, the problem with including JavaFX in a NetBeans RCP app is deployment, because you need different versions of the extension for different operating systems. All of the having the same class names, so you can't simply package all of them. I'm also in the process of figuring out how to do it best

Re: bringing an old javafx RCP project into the modern era

Following the directions at openjfx.io/openjfx-docs worked, make the sdk a library. BUT, they did miss something. Make sure to turn off Properties>Build>Compiling>CompileOnSave -ernie On 1/28/2020 8:16 PM, Ernie Rael wrote: Another look at openjfx.io/openjfx-docs and I see a NB example down

Re: bringing an old javafx RCP project into the modern era

Another look at openjfx.io/openjfx-docs and I see a NB example downloading the sdk and adding it as a library. Then adding the library to a pojo project (it's using jdk-13). So given that I downloaded the javafx plugin, I can't see how to add a dependency. Oh. Are those modules for running jfx

bringing an old javafx RCP project into the modern era

I have an old javafx project, NetBeans-8.0 RCP based. I abandoned it when it became obvious that Oracle was reducing support for javafx. I'm considering another look at javafx. I saw the latest release of javafx, 13.0.2, in the plugin manager, I loaded it and lots of stuff got turned on, see b