Re: Matrox Graphics Cards Problems

2018-05-18 Thread Kevin Rushforth
On 5/18/2018 10:45 AM, Matthew Elliot wrote: Hey Anirvan, Thanks for the info - guess it’s not such a promising route either then. As these Jira for Matrox cards in JavaFX were from 2013 is it possible that later Matrox cards / drivers would now work if this global disablement was not

Re: OpenJFX status update

2018-05-18 Thread Kevin Rushforth
I was somewhat imprecise. That should have read: We still expect to do a release of JavaFX 11 around the same time as JDK 11, but using a different **JBS release version** will help track the actual content of JavaFX 11 separately from JDK 11. The JavaFX version is still 11 as reported by

Re: OpenJFX status update

2018-05-18 Thread Kevin Rushforth
Sure. No problem. -- Kevin On 5/18/2018 1:22 PM, Nir Lisker wrote: I see, sorry about the false flag. On Fri, May 18, 2018 at 11:13 PM, Kevin Rushforth > wrote: I was somewhat imprecise. That should have read: We

Re: OpenJFX status update

2018-05-18 Thread Nir Lisker
I see, sorry about the false flag. On Fri, May 18, 2018 at 11:13 PM, Kevin Rushforth < kevin.rushfo...@oracle.com> wrote: > I was somewhat imprecise. That should have read: > > We still expect to do a release of JavaFX 11 around the same time as JDK > 11, but using a different **JBS release

Re: OpenJFX status update

2018-05-18 Thread Nir Lisker
> > We still expect to do a release of JavaFX 11 around the same time as JDK > 11, but using a different release number will help track the actual content > of JavaFX 11 separately from JDK 11. Iv'e just realized that not releasing JavaFX with version number 11 will cause confusion with all the

jfx-dev issues in JBS should now use "openjfx11" as release version

2018-05-18 Thread Kevin Rushforth
Starting now, the JBS release version for the "jfx-dev" repo is "openjfx11". All JBS issues for bugs that affect jfx-dev (e.g., are found in a local build or in an openjfx-11-ea release) should use "openjfx11" as the "affected version". Likewise, all bugs that are fixed in jfx-dev or targeted

Re: Matrox Graphics Cards Problems

2018-05-18 Thread Matthew Elliot
Hey Anirvan, Thanks for the info - guess it’s not such a promising route either then. As these Jira for Matrox cards in JavaFX were from 2013 is it possible that later Matrox cards / drivers would now work if this global disablement was not present. I.e is forceGpu enough to test such

Re: Matrox Graphics Cards Problems

2018-05-18 Thread Anirvan Sarkar
Hi Matthew, OpenGL pipeline on Windows is not a supported configuration and so it is not present in JavaFX for Windows[1][2]. You would have to build JavaFX yourself to include this pipeline and "use it at your own risk". It may or may not work. Also it looks like the card should support OpenGL

[11] RFR : JDK-8203365: [TESTBUG] Mark MeshManagerCacheLeakTest as unstable until test is fixed

2018-05-18 Thread Ambarish Rapte
Hi Kevin & Ajit, Please review this small fix: Webrev: http://cr.openjdk.java.net/~arapte/fx/8203365/webrev.00/ JBS: https://bugs.openjdk.java.net/browse/JDK-8203365 Regards, Ambarish

Re: OpenJFX status update

2018-05-18 Thread Kevin Rushforth
Hi Johan, On 5/18/2018 4:51 AM, Johan Vos wrote: Hi Kevin, Related to point 3: what exactly do you mean with "Java FX has been removed from JDK 11"? It isn't part of the OpenJDK 11-ea13 either so I don't see the difference? It was removed from the Oracle JDK 11 (it never was part of OpenJDK

Re: OpenJFX status update

2018-05-18 Thread Johan Vos
Hi Kevin, Related to point 3: what exactly do you mean with "Java FX has been removed from JDK 11"? It isn't part of the OpenJDK 11-ea13 either so I don't see the difference? I thought references to JavaFX would be removed from sun.launcher.LauncherHelper, but they are still there. Do you know

Re: bundling native libs in jars or modules

2018-05-18 Thread Johan Vos
I fully agree it should somehow somewhere sometime be standardized. But it is extremely unlikely it will be standardized before the Java 11 release, and we need a solution by the time Java 11 is released (and preferably sooner, as in "tomorrow") hence we need to have this or a similar workaround