Announcing EA builds of standalone JavaFX SDK

[Ty Young]

This works just as well as a build of OpenJDK 11 with JavaFX prebuilt 
for me in Netbeans 9 Beta. The project tested on was a personal modular 
JavaFX application using OpenJDK 10 in Arch Linux.


That said however, there seems to be a bug in the latest release of 
OpenJFX that is reproducible on my end in both this(standalone library 
release) as well my OpenJDK 11 OpenJFX build with TableView's 
setMouseTransparent method no longer working. Using Oracle JDK 10 works 
as expected. Is this a known issue with the latest release?

Re: [11] RFR JDK-8202199 : Provide public, unsupported API for FX Swing interop

[Kevin Rushforth]

The module definition for jdk.unsupported.desktop and the changes to 
java.desktop look fine.


In reviewing the jdk.swing.interop API, I have the following suggestions 
/ observations:


1. DispatcherWrapper, DragSourceContextWrapper, 
DropTargetContextWrapper, and LightweightContentWrapper can all be 
abstract, along with most of the methods (rather than having an empty 
body return value that is never used).


2. The addNotify method in LightweightFrameWrapper is unused. Should be 
used somewhere? If not, then it can be removed.


The implementation of the new wrapper classes looks OK to me with one 
observation that might or might not matter:


3. The behavior of getDefaultScaleX/Y (which is now in 
SwingInteropUtils) has changed in the case where the Graphics is not an 
instance of SunGraphics2D. The former behavior was to leave the instance 
variables X and Y unchanged. The new behavior will set them back to 1.0. 
Maybe this can't happen in practice, but it is something to consider.


-- Kevin


On 5/8/2018 3:31 AM, Alan Bateman wrote:

On 08/05/2018 06:51, Prasanta Sadhukhan wrote:

Modified webrev to rename to InteropProviderImpl

http://cr.openjdk.java.net/~psadhukhan/fxswing.10/

This looks okay to me.

-Alan

Re: Paint Phase Debugging / Performance

[Nir Lisker]

Hi Matthew,

This is a typical pulse, which indeed cases the effect of low FPS, and
that's what I'm trying to solve.

* Cache hints are ignored for 3D (but I tried anyway).
* -Dprism.showdirty and printrendergraph also don't work for 3D scenes
(though I can get an approximation with a 2D scene).
* There are no effects.

I'm working with Mission Control already, most of the instances in the GC
class histogram are related to animation
classes: InterpolationInterval$TangentDoubleInterpolationInterval
and NumberTangentInterpolator.

Looks like all all the discussed difficulties with diagnostics are enhanced
when it comes to 3D. Will have to dig deep on this one.

Thanks,
Nir

On Mon, May 7, 2018 at 9:07 PM, Matthew Elliot <
matthew.james.ell...@gmail.com> wrote:

> Hey Nir,
>
> I’m not sure if I can offer much support as I haven’t been into the 3D
> world but just to clarify, is it one pulse after another with long wait,
> paint phases? From what I’ve seen personally if you have painting of 100+
> milliseconds on every pulse you will be in big trouble / laggy as.
>
> On a one-off pulse like building a scene the first time I would say it is
> fine but regular paints that are longer are going to cause issues from my
> experience.
>
> Did you try profiling with mission controller to look at what garbage is
> being created / what hot methods there? Maybe it points you in a better
> direction / at least rule out your own code.
>
> With animations I guess you set cache hints already?
>
> Make sure you don’t have any effects on the animation as well, a Gaussian
> blur blend/drop shadow on an animation killed it for me.
> You can also try -Dprism.disableEffects= true to rule it out.
> You can also enable the prism option to show what is being painted on each
> pulse as an overlay. -Dprism.showdirty and there is another I forget to
> show how many times it was painted. (Not that your whole scene is painted
> when you expect a small part of it)
>
> Or some trial and error with the prism flags here to try narrow it down -
> Just open PrismSettings.java in your IDE or web browser.
>
> Code explains them better than most posts I’ve seen.
>
> Good luck.
> Matt
>
> Sent from my phone.
>
> On 7/05/2018, at 2:36 PM, Nir Lisker  wrote:
>
> Hi,
>
> I'm having a performance issue myself. I'm using animations on 3D models
> (in a 3D subscene) and when there are "too many" models the QuantumRenderer
> thread is running 100% of the time and utilizing 20-25% of the CPU, though
> the OS reports that overall all cores are at ~40%. The application is using
> the d3d pipeline.
>
> A typical pulse is
>
> PULSE: 4078 [112ms:225ms]
> T15 (11 +0ms): CSS Pass
> T15 (11 +0ms): Layout Pass
> T15 (12 +0ms): Update bounds
> T15 (12 +95ms): Waiting for previous rendering
> T15 (108 +0ms): Copy state to render graph
> T12 (109 +115ms): Painting
> T12 (224 +0ms): Presenting
> Counters:
> Nodes rendered: 651
> Nodes visited during render: 651
>
> Thread dumps show that QuantumRenderer is busy with tasks inside
>
> at com.sun.prism.impl.BaseMesh.buildPTGeometry(javafx.
> graphics@10-internal/BaseMesh.java:584)
> at com.sun.prism.impl.BaseMesh.buildGeometry(javafx.graphics@
> 10-internal/BaseMesh.java:516)
> at com.sun.javafx.sg.prism.NGTriangleMesh.validate(
> javafx.graphics@10-internal/NGTriangleMesh.java:75)
> at com.sun.javafx.sg.prism.NGShape3D.renderMeshView(
> javafx.graphics@10-internal/NGShape3D.java:84)
> at com.sun.javafx.sg.prism.NGShape3D.renderContent(
> javafx.graphics@10-internal/NGShape3D.java:201)
> at com.sun.javafx.sg.prism.NGNode.doRender(javafx.
> graphics@10-internal/NGNode.java:2072)
> at com.sun.javafx.sg.prism.NGNode.render(javafx.graphics@
> 10-internal/NGNode.java:1964)
> at com.sun.javafx.sg.prism.NGGroup.renderContent(javafx.
> graphics@10-internal/NGGroup.java:270)
> at com.sun.javafx.sg.prism.NGNode.doRender(javafx.
> graphics@10-internal/NGNode.java:2072)
> at com.sun.javafx.sg.prism.NGNode.render(javafx.graphics@
> 10-internal/NGNode.java:1964)
> at com.sun.javafx.sg.prism.NGGroup.renderContent(javafx.
> graphics@10-internal/NGGroup.java:270)
> at com.sun.javafx.sg.prism.NGNode.doRender(javafx.
> graphics@10-internal/NGNode.java:2072)
> at com.sun.javafx.sg.prism.NGNode.render(javafx.graphics@
> 10-internal/NGNode.java:1964)
> at com.sun.javafx.sg.prism.NGGroup.renderContent(javafx.
> graphics@10-internal/NGGroup.java:270)
> at com.sun.javafx.sg.prism.NGNode.renderCached(javafx.
> graphics@10-internal/NGNode.java:2379)
> at com.sun.javafx.sg.prism.NGNode.doRender(javafx.
> graphics@10-internal/NGNode.java:2063)
> at com.sun.javafx.sg.prism.NGNode.render(javafx.graphics@
> 10-internal/NGNode.java:1964)
> at com.sun.javafx.sg.prism.NGGroup.renderContent(javafx.
> graphics@10-internal/NGGroup.java:270)
> at 

Re: Announcing EA builds of standalone JavaFX SDK

[Michael Paus]

Am 08.05.18 um 23:55 schrieb Nir Lisker:

Thanks Kevin, that's good to hear.

Michael, adding the external jars as single entries is the simplest 
and most granular way, but you can also define a library from those 
jars and then add that single library to any project:


1. Add Library...
2. User Library
3. User Libraries...
4. New... (give it a name)
5. Add External JARs... (add all the jars)
6. OK/Apply everything.

This creates a single entry in the .classpath:

    path="org.eclipse.jdt.USER_LIBRARY/library_name">


This should be the parallel to specifying a single folder from the 
command line.

I'll give that a try in the morning.


As for the runtime issue, is it finding the other modules?
No, if I do not specify javafx.fxml it complains about the next one. I 
also tried moving all jars to the classpath instead of the module path. 
Again this resolves the compile time dependencies but results in an 
error at runtime. Since Java 9 Eclipse has really become a mess.


- Nir

On Tue, May 8, 2018 at 3:39 PM, Michael Paus > wrote:


Am 08.05.18 um 14:27 schrieb Tom Schindl:

[...]

3. How do you properly configure an Eclipse (the latest
4.7.3a) project
to use this module path. Adding the OpenJDK was no problem
but how do
you add the module path for JavaFX? I failed on that.

You just open the Java Build Path-Properties-Page on the
project and add
the external jars, not?

Tom


That's one of the ways I tried it but ...

1. is that the intended way of doing it? On the command line you
just specify a single folder.

2. I did this and it resolved all dependencies at compile time but
I got an exception at runtime

Error occurred during initialization of boot layer
java.lang.module.FindException: Module javafx.fxml not found

although I also added

--add-modules=javafx.fxml,javafx.controls,javafx.web,javafx.media

as VM arguments.

Re: Announcing EA builds of standalone JavaFX SDK

[Nir Lisker]

Thanks Kevin, that's good to hear.

Michael, adding the external jars as single entries is the simplest and
most granular way, but you can also define a library from those jars and
then add that single library to any project:

1. Add Library...
2. User Library
3. User Libraries...
4. New... (give it a name)
5. Add External JARs... (add all the jars)
6. OK/Apply everything.

This creates a single entry in the .classpath:



This should be the parallel to specifying a single folder from the command
line.

As for the runtime issue, is it finding the other modules?

- Nir

On Tue, May 8, 2018 at 3:39 PM, Michael Paus  wrote:

> Am 08.05.18 um 14:27 schrieb Tom Schindl:
>
> [...]
>>
>> 3. How do you properly configure an Eclipse (the latest 4.7.3a) project
>>> to use this module path. Adding the OpenJDK was no problem but how do
>>> you add the module path for JavaFX? I failed on that.
>>>
>>> You just open the Java Build Path-Properties-Page on the project and add
>> the external jars, not?
>>
>> Tom
>>
>
> That's one of the ways I tried it but ...
>
> 1. is that the intended way of doing it? On the command line you just
> specify a single folder.
>
> 2. I did this and it resolved all dependencies at compile time but I got
> an exception at runtime
>
> Error occurred during initialization of boot layer
> java.lang.module.FindException: Module javafx.fxml not found
>
> although I also added
>
> --add-modules=javafx.fxml,javafx.controls,javafx.web,javafx.media
>
> as VM arguments.
>
>

Re: Announcing EA builds of standalone JavaFX SDK

[Jonathan Giles]

Congrats to Kevin and team on this milestone!

-- Jonathan
(Tapped on a touch device)

On Mon, 7 May 2018, 4:01 PM Kevin Rushforth, 
wrote:

> I am pleased to announce the first Early Access build of a standalone
> JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an
> OpenJDK 11 EA build.
>
> If your application is in an unnamed module (i.e., your app is on the
> classpath), you can run your application as follows, after unzipping the
> SDK bundle for your platform.
>
> $ java --module-path $PATH_TO_FX/javafx-sdk-11
> --add-modules=javafx.controls,javafx.fxml MyApp
>
> This assumes you don't need media or web. If you do, then add those
> modules, too. Note that since javafx.web "requires transitive
> javafx.controls", you can omit javafx.controls if you add javafx.web.
>
> If you are running a modular application, then you don't need the
> "--add-modules" option.
>
> Note that this is a stepping stone to javafx modules in a repository
> like Maven.
>
> Please test your applications with the SDK and give us feedback.
>
> Thanks.
>
> -- Kevin
>
> [1] http://jdk.java.net/openjfx/
>
>

Re: Announcing EA builds of standalone JavaFX SDK

[Kevin Rushforth]

On 5/8/2018 5:01 AM, Michael Paus wrote:

Hi Kevin,
that's a great achievement. I have a few questions/remarks though:

1. On the announcement page I assume the license agreement should not 
read
"These binaries are provided under the GNU General Public License 
."

but instead should read
"These early-access, open-source builds are provided under the GNU 
General Public License, version 2, with the Classpath Exception 
."
With or without classpath exception makes a big difference. (The 
actual link is already the same anyway.)


I will get this fixed to match the JDK 11 EA text.


2. I can confirm that a simple program from the command line works 
nicely on my MacBook Pro Retina but I had to add "/lib" to the module 
path to get it working.


Yes, adding the javafx-sdk-11/lib to the module-path is a required step.

Thanks.

-- Kevin




3. How do you properly configure an Eclipse (the latest 4.7.3a) 
project to use this module path. Adding the OpenJDK was no problem but 
how do you add the module path for JavaFX? I failed on that.


Michael

Am 08.05.18 um 01:00 schrieb Kevin Rushforth:
I am pleased to announce the first Early Access build of a standalone 
JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an 
OpenJDK 11 EA build.


If your application is in an unnamed module (i.e., your app is on the 
classpath), you can run your application as follows, after unzipping 
the SDK bundle for your platform.


$ java --module-path $PATH_TO_FX/javafx-sdk-11 
--add-modules=javafx.controls,javafx.fxml MyApp


This assumes you don't need media or web. If you do, then add those 
modules, too. Note that since javafx.web "requires transitive 
javafx.controls", you can omit javafx.controls if you add javafx.web.


If you are running a modular application, then you don't need the 
"--add-modules" option.


Note that this is a stepping stone to javafx modules in a repository 
like Maven.


Please test your applications with the SDK and give us feedback.

Thanks.

-- Kevin

[1] http://jdk.java.net/openjfx/

Re: [11] RFR JDK-8202199 : Provide public, unsupported API for FX Swing interop

[Kevin Rushforth]

Exactly. The current naming was recommended by the jigsaw team, and I 
fully agree.


-- Kevin

On 5/8/2018 12:53 AM, Prasanta Sadhukhan wrote:
We have discussed this internally and we believe that 
"unsupportedness" is the critical property here so it justifies 
grouping them in the same "unsupported" namespace rather than desktop 
namespace.


Regards
Prasanta
On 5/8/2018 12:56 PM, Ali Ebrahimi wrote:

Hi,
What about " jdk.desktop.unsupported" for new module name?

On Tue, May 8, 2018 at 10:21 AM, Prasanta Sadhukhan 
> wrote:


    Modified webrev to rename to InteropProviderImpl

    http://cr.openjdk.java.net/~psadhukhan/fxswing.10/
    

    Regards
    Prasanta

    On 5/7/2018 8:35 PM, Kevin Rushforth wrote:

    That name seems good to me.

    -- Kevin


    On 5/7/2018 8:01 AM, Prasanta Sadhukhan wrote:

    Would InteropProviderImpl sound good?

    Regards
    Prasanta
    On 5/7/2018 8:27 PM, Alan Bateman wrote:



    On 07/05/2018 10:26, Prasanta Sadhukhan wrote:

    :

    Modified webrev to use InteropProvider
http://cr.openjdk.java.net/~psadhukhan/fxswing.9/


    This looks okay although for consistent then
    InteropImpl could be renamed too.

    -Alan







--

Best Regards,
Ali Ebrahimi

Fwd: [11] RFR: 8202553: Update FXLauncherTest as part of removing JavaFX from JDK

[Kevin Rushforth]

FYI...

-- Kevin



 Forwarded Message 
Subject: 	[11] RFR: 8202553: Update FXLauncherTest as part of removing 
JavaFX from JDK

Date:   Tue, 8 May 2018 08:15:48 -0700
From:   Kevin Rushforth 
To: 	core-libs-...@openjdk.java.net , 
Kumar Srinivasan 




Please review the following test fix:

https://bugs.openjdk.java.net/browse/JDK-8202553
http://cr.openjdk.java.net/~kcr/8202553/webrev.00/

This modifies the existing FXLauncherTest as follows:

1. Reverse the check for the presence of the
javafx.application.Application class and fail the test if present

2. Create a "mock" javafx.graphics module with a mocked up version of
the few classes needed to validate the FX launcher functionality

3. Remove the "intermittent" and "headful" keywords, since neither apply
any more

4. Remove the test from the problem list

Thanks.

-- Kevin

Re: Announcing EA builds of standalone JavaFX SDK

[Michael Paus]

Am 08.05.18 um 14:37 schrieb Paul Ray Russell:

V. pleased to say it's working for me. It builds using our current Maven
build ( which is targeted in Maven at JDK 9)

  
 org.apache.maven.plugins
 maven-compiler-plugin
 3.6.2
 
 1.9
 1.9
 
 -Xlint:unchecked
 
 
 

Trying to set a 1.11 release will give the Maven error:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile
(default-compile) on project KattRunOnTheTide: Fatal error compiling:
error: invalid target release: 1.11 -> [Help 1]

Have you tried using the latest Maven compiler plugin 3.7.0 ?

TextArea doesn't scroll to bottom when texts becomes long and vertical scrollbar appears JDK-8189732

[Alex Sviridov]

More then half a year ago I opened an issue  
https://bugs.openjdk.java.net/browse/JDK-8189732  
that TextArea doesn't scroll to bottom when texts becomes long and vertical 
scrollbar appears.

The issue is still not resolved and even fix version is not defined. Could 
anyone say the reason
of this? It is very strange as such issues must be resolved very quickly. 


-- 
Alex Sviridov

Re: Announcing EA builds of standalone JavaFX SDK

[Michael Paus]

Am 08.05.18 um 14:27 schrieb Tom Schindl:

[...]


3. How do you properly configure an Eclipse (the latest 4.7.3a) project
to use this module path. Adding the OpenJDK was no problem but how do
you add the module path for JavaFX? I failed on that.


You just open the Java Build Path-Properties-Page on the project and add
the external jars, not?

Tom


That's one of the ways I tried it but ...

1. is that the intended way of doing it? On the command line you just 
specify a single folder.


2. I did this and it resolved all dependencies at compile time but I got 
an exception at runtime


Error occurred during initialization of boot layer
java.lang.module.FindException: Module javafx.fxml not found

although I also added

--add-modules=javafx.fxml,javafx.controls,javafx.web,javafx.media

as VM arguments.

Re: Announcing EA builds of standalone JavaFX SDK

[Paul Ray Russell]

V. pleased to say it's working for me. It builds using our current Maven
build ( which is targeted in Maven at JDK 9)

 
org.apache.maven.plugins
maven-compiler-plugin
3.6.2

1.9
1.9

-Xlint:unchecked




Trying to set a 1.11 release will give the Maven error:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile
(default-compile) on project KattRunOnTheTide: Fatal error compiling:
error: invalid target release: 1.11 -> [Help 1]

-

Running under Win10 via a BAT file: I've made sure OpenJDK is the only JDK
on the system path. I built using Maven then Shade into a single Jar. For
the purposes of this test, I've made an explicit call to the VM from a
batch file on Win 10 64 bit.

"C:\Program Files\Java\jdk-11\bin\java" -Xms2500m -Xmx4500m -jar
-Djavafx.animation.fullspeed=true runTime.jar
pause

(Normally I wrap this into an .EXE. using Launch4J after going through
Proguard.)


I cannot build the project under Intellij: I get a Jetbrains error:

Error:Internal error: (java.net.MalformedURLException) unknown protocol: jrt
java.net.MalformedURLException: unknown protocol: jrt
at java.net.URL.(URL.java:421)
at java.net.URL.(URL.java:310)
at java.net.URL.(URL.java:333)
at
com.intellij.compiler.instrumentation.InstrumentationClassFinder.createJDKPlatformUrl(InstrumentationClassFinder.java:61)
at
org.jetbrains.jps.incremental.instrumentation.ClassProcessingBuilder.createInstrumentationClassFinder(ClassProcessingBuilder.java:125)
at
org.jetbrains.jps.incremental.instrumentation.ClassProcessingBuilder.build(ClassProcessingBuilder.java:93)
at
org.jetbrains.jps.incremental.IncProjectBuilder.runModuleLevelBuilders(IncProjectBuilder.java:1246)
at
org.jetbrains.jps.incremental.IncProjectBuilder.runBuildersForChunk(IncProjectBuilder.java:923)
at
org.jetbrains.jps.incremental.IncProjectBuilder.buildTargetsChunk(IncProjectBuilder.java:995)
at
org.jetbrains.jps.incremental.IncProjectBuilder.buildChunkIfAffected(IncProjectBuilder.java:886)
at
org.jetbrains.jps.incremental.IncProjectBuilder.buildChunks(IncProjectBuilder.java:719)
at
org.jetbrains.jps.incremental.IncProjectBuilder.runBuild(IncProjectBuilder.java:371)
at
org.jetbrains.jps.incremental.IncProjectBuilder.build(IncProjectBuilder.java:178)
at org.jetbrains.jps.cmdline.BuildRunner.runBuild(BuildRunner.java:138)
at org.jetbrains.jps.cmdline.BuildSession.runBuild(BuildSession.java:308)
at org.jetbrains.jps.cmdline.BuildSession.run(BuildSession.java:138)
at
org.jetbrains.jps.cmdline.BuildMain$MyMessageHandler.lambda$channelRead0$0(BuildMain.java:235)
at
org.jetbrains.jps.service.impl.SharedThreadPoolImpl.lambda$executeOnPooledThread$0(SharedThreadPoolImpl.java:42)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Please perform full project rebuild (Build | Rebuild Project)

==
I added a check in the code directly: the result in the log file:

2018-05-08 :13:16:28 : INFO : techtalix.app.StartGame start : JAVA VERSION
11-ea

But running from the BAT file directly after building with Maven- I only
had one error during game play: I don't get this error normally. In my
code, I've just checking some game tiles, and in this case one is clearly
null.

Exception in thread "JavaFX Application Thread"
java.lang.NullPointerException
at
com.techtalix.player.PlayerController.lambda$new$0(PlayerController.java:114)
at
javafx.base/com.sun.javafx.event.CompositeEventHandler$NormalEventHandlerRecord.handleBubblingEvent(CompositeEventHandler.java:218)
at
javafx.base/com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(CompositeEventHandler.java:80)
at
javafx.base/com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:238)
at
javafx.base/com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:191)
at
javafx.base/com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(CompositeEventDispatcher.java:59)
at
javafx.base/com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:58)
at
javafx.base/com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114)
at
javafx.base/com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56)
at

Re: Announcing EA builds of standalone JavaFX SDK

[Tom Schindl]

[...]

> 3. How do you properly configure an Eclipse (the latest 4.7.3a) project
> to use this module path. Adding the OpenJDK was no problem but how do
> you add the module path for JavaFX? I failed on that.
> 

You just open the Java Build Path-Properties-Page on the project and add
the external jars, not?

Tom

Re: Announcing EA builds of standalone JavaFX SDK

[Michael Paus]

Hi Kevin,
that's a great achievement. I have a few questions/remarks though:

1. On the announcement page I assume the license agreement should not read
"These binaries are provided under the GNU General Public License 
."

but instead should read
"These early-access, open-source builds are provided under the GNU 
General Public License, version 2, with the Classpath Exception 
."
With or without classpath exception makes a big difference. (The actual 
link is already the same anyway.)


2. I can confirm that a simple program from the command line works 
nicely on my MacBook Pro Retina but I had to add "/lib" to the module 
path to get it working.


3. How do you properly configure an Eclipse (the latest 4.7.3a) project 
to use this module path. Adding the OpenJDK was no problem but how do 
you add the module path for JavaFX? I failed on that.


Michael

Am 08.05.18 um 01:00 schrieb Kevin Rushforth:
I am pleased to announce the first Early Access build of a standalone 
JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an 
OpenJDK 11 EA build.


If your application is in an unnamed module (i.e., your app is on the 
classpath), you can run your application as follows, after unzipping 
the SDK bundle for your platform.


$ java --module-path $PATH_TO_FX/javafx-sdk-11 
--add-modules=javafx.controls,javafx.fxml MyApp


This assumes you don't need media or web. If you do, then add those 
modules, too. Note that since javafx.web "requires transitive 
javafx.controls", you can omit javafx.controls if you add javafx.web.


If you are running a modular application, then you don't need the 
"--add-modules" option.


Note that this is a stepping stone to javafx modules in a repository 
like Maven.


Please test your applications with the SDK and give us feedback.

Thanks.

-- Kevin

[1] http://jdk.java.net/openjfx/

Re: Announcing EA builds of standalone JavaFX SDK

[John-Val Rose]

Thanks very much Kevin.

This is a great step forward and will make all of our lives easier.

Graciously,

John-Val Rose

> On 8 May 2018, at 17:43, Johan Vos  wrote:
> 
> Hi Kevin,
> 
> Excellent work.
> I confirm this is working for me.
> 
> Java: openjdk 11-ea+12 for Linux
> App from
> https://github.com/gluonhq/projavafx9/tree/master/chapter1/HelloEarthRise/src/main/java/projavafx/helloearthrise/ui
> (on
> classpath)
> 
> - Johan
> 
> On Tue, May 8, 2018 at 1:11 AM Kevin Rushforth 
> wrote:
> 
>> I am pleased to announce the first Early Access build of a standalone
>> JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an
>> OpenJDK 11 EA build.
>> 
>> If your application is in an unnamed module (i.e., your app is on the
>> classpath), you can run your application as follows, after unzipping the
>> SDK bundle for your platform.
>> 
>> $ java --module-path $PATH_TO_FX/javafx-sdk-11
>> --add-modules=javafx.controls,javafx.fxml MyApp
>> 
>> This assumes you don't need media or web. If you do, then add those
>> modules, too. Note that since javafx.web "requires transitive
>> javafx.controls", you can omit javafx.controls if you add javafx.web.
>> 
>> If you are running a modular application, then you don't need the
>> "--add-modules" option.
>> 
>> Note that this is a stepping stone to javafx modules in a repository
>> like Maven.
>> 
>> Please test your applications with the SDK and give us feedback.
>> 
>> Thanks.
>> 
>> -- Kevin
>> 
>> [1] http://jdk.java.net/openjfx/
>> 
>> 

Announcing EA builds of standalone JavaFX SDK

[Paul Ray Russell]

Excellent! I'll try to get this working for our game later in the week.

Best,
Paul

[11] RFR JDK-8198602 : [TestBug] test.javafx.css.StylesheetTest logs IllegalArgumentException

[Ambarish Rapte]

Hi Kevin & Ajit,

 

Please review this small fix,
Bug: https://bugs.openjdk.java.net/browse/JDK-8198602
Webrev: http://cr.openjdk.java.net/~arapte/fx/8198602/webrev.00/

 

 

Regards,

Ambarish

Re: [11] RFR JDK-8202199 : Provide public, unsupported API for FX Swing interop

[Alan Bateman]

On 08/05/2018 06:51, Prasanta Sadhukhan wrote:

Modified webrev to rename to InteropProviderImpl

http://cr.openjdk.java.net/~psadhukhan/fxswing.10/

This looks okay to me.

-Alan

Re: [11] RFR JDK-8202199 : Provide public, unsupported API for FX Swing interop

[Prasanta Sadhukhan]

We have discussed this internally and we believe that "unsupportedness" 
is the critical property here so it justifies grouping them in the same 
"unsupported" namespace rather than desktop namespace.


Regards
Prasanta
On 5/8/2018 12:56 PM, Ali Ebrahimi wrote:

Hi,
What about " jdk.desktop.unsupported" for new module name?

On Tue, May 8, 2018 at 10:21 AM, Prasanta Sadhukhan 
> 
wrote:


Modified webrev to rename to InteropProviderImpl

http://cr.openjdk.java.net/~psadhukhan/fxswing.10/


Regards
Prasanta

On 5/7/2018 8:35 PM, Kevin Rushforth wrote:

That name seems good to me.

-- Kevin


On 5/7/2018 8:01 AM, Prasanta Sadhukhan wrote:

Would InteropProviderImpl sound good?

Regards
Prasanta
On 5/7/2018 8:27 PM, Alan Bateman wrote:



On 07/05/2018 10:26, Prasanta Sadhukhan wrote:

:

Modified webrev to use InteropProvider
http://cr.openjdk.java.net/~psadhukhan/fxswing.9/


This looks okay although for consistent then
InteropImpl could be renamed too.

-Alan







--

Best Regards,
Ali Ebrahimi

Re: Announcing EA builds of standalone JavaFX SDK

[Johan Vos]

Hi Kevin,

Excellent work.
I confirm this is working for me.

Java: openjdk 11-ea+12 for Linux
App from
https://github.com/gluonhq/projavafx9/tree/master/chapter1/HelloEarthRise/src/main/java/projavafx/helloearthrise/ui
(on
classpath)

- Johan

On Tue, May 8, 2018 at 1:11 AM Kevin Rushforth 
wrote:

> I am pleased to announce the first Early Access build of a standalone
> JavaFX SDK [1]. You can download it and run it using OpenJDK 10 or an
> OpenJDK 11 EA build.
>
> If your application is in an unnamed module (i.e., your app is on the
> classpath), you can run your application as follows, after unzipping the
> SDK bundle for your platform.
>
> $ java --module-path $PATH_TO_FX/javafx-sdk-11
> --add-modules=javafx.controls,javafx.fxml MyApp
>
> This assumes you don't need media or web. If you do, then add those
> modules, too. Note that since javafx.web "requires transitive
> javafx.controls", you can omit javafx.controls if you add javafx.web.
>
> If you are running a modular application, then you don't need the
> "--add-modules" option.
>
> Note that this is a stepping stone to javafx modules in a repository
> like Maven.
>
> Please test your applications with the SDK and give us feedback.
>
> Thanks.
>
> -- Kevin
>
> [1] http://jdk.java.net/openjfx/
>
>

Re: [11] RFR JDK-8202199 : Provide public, unsupported API for FX Swing interop

[Ali Ebrahimi]

Hi,
What about " jdk.desktop.unsupported" for new module name?

On Tue, May 8, 2018 at 10:21 AM, Prasanta Sadhukhan <
prasanta.sadhuk...@oracle.com> wrote:

> Modified webrev to rename to InteropProviderImpl
>
> http://cr.openjdk.java.net/~psadhukhan/fxswing.10/
>
> Regards
> Prasanta
>
> On 5/7/2018 8:35 PM, Kevin Rushforth wrote:
>
>> That name seems good to me.
>>
>> -- Kevin
>>
>>
>> On 5/7/2018 8:01 AM, Prasanta Sadhukhan wrote:
>>
>>> Would InteropProviderImpl sound good?
>>>
>>> Regards
>>> Prasanta
>>> On 5/7/2018 8:27 PM, Alan Bateman wrote:
>>>


 On 07/05/2018 10:26, Prasanta Sadhukhan wrote:

> :
>
> Modified webrev to use InteropProvider
> http://cr.openjdk.java.net/~psadhukhan/fxswing.9/
>
 This looks okay although for consistent then InteropImpl could be
 renamed too.

 -Alan

>>>
>>>
>>
>


-- 

Best Regards,
Ali Ebrahimi