Re: Testing your JavaFX applications on JDK 9

Sorry, I believe I'm running a 64-bit JRE in both cases. I will verify when I’m back in the office tomorrow. Scott > On Jan 26, 2017, at 9:56 PM, Philip Race wrote: > > I was asking about the VM not the O/S. > > 32 bit or 64 bit in this case. > > Notably the 32 bit

Re: Testing your JavaFX applications on JDK 9

I was asking about the VM not the O/S. 32 bit or 64 bit in this case. Notably the 32 bit client VM is gone so you get the 32 bit server VM. That could make a difference, although in theory the server VM performs better - so long as it does not run out of memory. -phil. On 1/26/17, 6:44 PM,

Re: Testing your JavaFX applications on JDK 9

I’ve only tested with Java 9 on Windows 10 64-bit so far. I have not yet done any profiling to try to isolate where the difference might be. The application generates data in native code, wrapped in a native ByteBuffer and passes an object around holding the buffer and map of properties to go

Re: Testing your JavaFX applications on JDK 9

Scott, What VM/bitness/platforms show this ? All or just a specific one ? -phil. On 1/26/17, 6:08 PM, Kevin Rushforth wrote: Hi Scott, Thanks for the report. The only JDK 9 specific performance problems I have seen is with startup, which would be a good thing to discuss on jigsaw-dev. If

Re: Testing your JavaFX applications on JDK 9

Hi Scott, Thanks for the report. The only JDK 9 specific performance problems I have seen is with startup, which would be a good thing to discuss on jigsaw-dev. If you are seeing actual application slowdown, that might be something else, depending on where the problem is. Have you profiled

Re: Testing your JavaFX applications on JDK 9

Exactly. I would add that any tests that need Robot or PerformanceTracker will need to use "--add-exports" to add the necessary qualified exports on the command line as there is no public API for those. -- Kevin Jonathan Giles wrote: Platform.firePulse() never existed, you're probably

Re: Testing your JavaFX applications on JDK 9

Platform.firePulse() never existed, you're probably thinking of Toolkit.firePulse() (which is not public API)? A close replacement is Platform.requestNextPulse(). -- Jonathan On 17/01/17 10:00 AM, Tom Eugelink wrote: One of the methods I use a lot in Tests, to make sure something has

Re: Testing your JavaFX applications on JDK 9

One of the methods I use a lot in Tests, to make sure something has happened, is: runAndWait( () -> Platform.firePulse() ); firePulse no longer exists. Is there a replacement? The rest seems to compile ok. But I cannot run the tests ATM. On 11-1-2017 20:14, Kevin Rushforth wrote: As

Re: Testing your JavaFX applications on JDK 9

That indeed works, thanks Vadim. And of course my approach does not work because the gradle.properties are read after its JVM has already started. Onwards. Tom On 14-1-2017 21:37, Vadim Pakhnushev wrote: Tom, In JavaFX we use _JAVA_OPTIONS environment variable to workaround this:

Re: Testing your JavaFX applications on JDK 9

Tom, In JavaFX we use _JAVA_OPTIONS environment variable to workaround this: http://mail.openjdk.java.net/pipermail/openjfx-dev/2016-December/020077.html Note that if you are building on Windows without Cygwin, you need to remove quotes. Vadim On 14.01.2017 23:26, Tom Eugelink wrote: On

Re: Testing your JavaFX applications on JDK 9

On 11-1-2017 20:14, Kevin Rushforth wrote: As you may know JDK 9 has hit the feature extension complete milestone [1]. We still have a small number of weeks to fix P1-P3 bugs, but we need to know about them in order to fix them. Our focus will be on bugs that are new in JDK 9 (regressions).

Re: Testing your JavaFX applications on JDK 9

Thank you Kevin, after looking inside I see it. Right now, I will do a pull request for it. -- Rahman 2017-01-14 19:33 GMT+03:00 Kevin Rushforth : > The deprecated builders were removed from 9 early in the JDK 9 development > cycle [1][2]. > > -- Kevin > > [1]

Re: Testing your JavaFX applications on JDK 9

The deprecated builders were removed from 9 early in the JDK 9 development cycle [1][2]. -- Kevin [1] https://bugs.openjdk.java.net/browse/JDK-8092861 [2] http://mail.openjdk.java.net/pipermail/openjfx-dev/2015-January/016496.html Rahman USTA wrote: Hello Kevin, I try to run AsciidocFX

Re: Testing your JavaFX applications on JDK 9

Hello Kevin, I try to run AsciidocFX with latest JDK 9 EA. AsciidocFX uses FXForm2 project and while building I get the following error. Exception in thread "JavaFX Application Thread" java.lang.NoClassDefFoundError: javafx/scene/layout/GridPaneBuilder at

Testing your JavaFX applications on JDK 9

As you may know JDK 9 has hit the feature extension complete milestone [1]. We still have a small number of weeks to fix P1-P3 bugs, but we need to know about them in order to fix them. Our focus will be on bugs that are new in JDK 9 (regressions). I ask all JavaFX developers to please