Re: [9] review request: 8131888: Deliver javafx.swt as a modular jar in JDK 9

[Mandy Chung]

> On May 27, 2016, at 1:30 AM, Tom Schindl  wrote:
> 
> Do you have an example how to construct such a Layer?


// path is the path to javafx-swt.jar
ModuleFinder finder = ModuleFinder.of(path);
Configuration cf = Layer.boot()
.configuration()
.resolveRequires(finder, ModuleFinder.of(), Set.of("javafx.swt"));

// “parent” is the class loader to which SWT types are visible
Layer layer = Layer.boot().defineModulesWithOneLoader(cf, parent);

// the class loader defining javafx.swt module
ClassLoader loader = layer.findLoader("javafx.swt”);

[1] will show more examples of Layer.
Mandy
[1] 
http://hg.openjdk.java.net/jdk9/dev/jdk/file/df35a805b405/test/java/lang/reflect/Layer/LayerAndLoadersTest.java

Re: HEADS-UP: plan to integrate a newer WebKit into 9-dev next week.

[Kevin Rushforth]

We're too focused on JDK 9 to think about JDK 10 yet. After we stabilize 
JDK 9 we'll start planning. At that time we will solicit feedback from 
the openjfx-dev community to help prioritize.


-- Kevin


Konstantin Pasko wrote:

Hi Kevin,

sorry for the offtopic, but as you just mentioned JDK 10, could you 
please tell us what is planned for that release? 
Something from the high level? New/missing features, controls, huge 
bugfixes?
Googling "javafx road map" or "javafx jdk10" gives no results and 
looking 
through https://bugs.openjdk.java.net/projects/JDK/versions/16302 is 
quite time-consuming.



With best regards,
Konstantin

2016-05-27 14:51 GMT+02:00 Kevin Rushforth >:


No, I don't have anything further to add about WebGL, if that's
what you are asking.

As for moving to Blink, that would be a very large effort. We do
not currently plan to do this for JDK 10, but could reevaluate it
in the future if something changes.


-- Kevin


Felix Bembrick wrote:

Any comments on this? Isn't it time to move to Blink?

 


On 13 May 2016, at 04:32, Felix Bembrick
> wrote:

Thanks Kevin.

I was more curious as to why WebGL support hasn't been
there since day 1, given that WebKit itself supports it.

Felix

   


On 13 May 2016, at 01:52, Kevin Rushforth
> wrote:

It was an issue of resources versus priority and
scope. JDK 9 is focused on Jigsaw modularity and a few
other minor features. It is more of a "smoothing out"
release than a big feature release (except for
Jigsaw). We expect JDK 10 to be a somewhat more
feature-oriented release.

-- Kevin


Felix Bembrick wrote:
 


Do you mind if I ask what the rationale behind
such a decision is?

From an admittedly perhaps totally ignorant
outside observer, it would seem to me that any
cost/benefit analysis would basically put this
feature in the "no brainer" category and should
have been implemented at the very least since JFX 8.


   


On 12 May 2016, at 01:11, Kevin Rushforth
> wrote:

No. WebGL support is not planned for JDK 9. We
will look at this for JDK 10.

-- Kevin


Felix Bembrick wrote:

 


Will this new WebKit finally support WebGL?

Just by supporting WebGL in the JavaFX
WebView will instantly enable an entire
new set of 3D features and access to a
plethora of JavaScript 3D libraries for
"free".

And, Google Maps will finally work too.


   


On 11 May 2016, at 08:20, Kevin
Rushforth >
wrote:

All,

As a heads-up, we plan to push an
updated WebKit to FX 9-dev early next
week [1]. If there are no build
problems, they will be integrated to 9
master the following week for
jdk-9+119. We then plan to backport
the newer WebKit (to keep them in
sync) to 8u-dev a couple weeks later.

The only new tool needed to build this
is CMake [2] version 3.4 or later (we
will use 3.4.1 to build).

Let me know if you have any questions.

-- Kevin

[1]
https://bugs.openjdk.java.net/browse/JDK-8156698

[2] http://cmake.org/


 

Open test development: JDK-8139764

[Andrey Rusakov]

Please look at my new test for regression JDK-8139764 


http://cr.openjdk.java.net/~arusakov/8139764/webrev.00/

Re: JavaFX with Eclipse and JDK9

[Kevin Rushforth]

Where did you download it from? What build is it (i.e., what is the 
output of "java -version")? Can you run "java -listmods" and see whether 
the javafx.* modules are there?


-- Kevin


Dr. Michael Paus wrote:
I recently tried to get a JavaFX application running with the latest 
EA build of JDK9 from
within Eclipse but I failed. Can anybody on this list tell me what I 
have to do to get that
working? I have the latest milestone release of Eclipse Neon installed 
together with the
latest JDK9 and I have also installed the Java 9 Support (BETA) for 
Neon. I also installed
e(fx)clipse if that should matter. The problem is that I cannot access 
any of the JavaFX
packages. I even added a module-info.java file to the project which 
explicitly requires the
JavaFX modules but nothing helped so far. The JRE System Library only 
contains the modules
which are in the java.* namespace but none of the other modules 
especially the javafx.*
modules and I don't find any option to add these. Did anybody ever try 
this and succeeded?


Thanks, Michael

Re: HEADS-UP: plan to integrate a newer WebKit into 9-dev next week.

[Kevin Rushforth]

As I mentioned before, it is a non-trivial amount of work to integrate 
it into FX. We don't use the WebKit native renderer, rather the WebKit 
renderer is implemented by calling into Prism. Further, we use DirectX 
on Windows, which adds an additional complication (yes I know that WebGL 
has a solution for that, but integrating it will require a fair bit of 
work). Having said that, WebGL support in JavaFX is a likely JDK 10 feature.


-- Kevin


Felix Bembrick wrote:

 Can you at least let me know why the JavaFX usage of WebKit does *not* support 
WebGL when native WebKit itself always has?

Is there some technical or architectural barrier?

  

On 27 May 2016, at 22:51, Kevin Rushforth  wrote:

No, I don't have anything further to add about WebGL, if that's what you are 
asking.

As for moving to Blink, that would be a very large effort. We do not currently 
plan to do this for JDK 10, but could reevaluate it in the future if something 
changes.

-- Kevin


Felix Bembrick wrote:


Any comments on this? Isn't it time to move to Blink?

 
  

On 13 May 2016, at 04:32, Felix Bembrick  wrote:

Thanks Kevin.

I was more curious as to why WebGL support hasn't been there since day 1, given 
that WebKit itself supports it.

Felix

   


On 13 May 2016, at 01:52, Kevin Rushforth  wrote:

It was an issue of resources versus priority and scope. JDK 9 is focused on Jigsaw 
modularity and a few other minor features. It is more of a "smoothing out" 
release than a big feature release (except for Jigsaw). We expect JDK 10 to be a somewhat 
more feature-oriented release.

-- Kevin


Felix Bembrick wrote:
 
  

Do you mind if I ask what the rationale behind such a decision is?

From an admittedly perhaps totally ignorant outside observer, it would seem to me that 
any cost/benefit analysis would basically put this feature in the "no brainer" 
category and should have been implemented at the very least since JFX 8.


   


On 12 May 2016, at 01:11, Kevin Rushforth  wrote:

No. WebGL support is not planned for JDK 9. We will look at this for JDK 10.

-- Kevin


Felix Bembrick wrote:

 
  

Will this new WebKit finally support WebGL?

Just by supporting WebGL in the JavaFX WebView will instantly enable an entire new set of 
3D features and access to a plethora of JavaScript 3D libraries for "free".

And, Google Maps will finally work too.


   


On 11 May 2016, at 08:20, Kevin Rushforth  wrote:

All,

As a heads-up, we plan to push an updated WebKit to FX 9-dev early next week 
[1]. If there are no build problems, they will be integrated to 9 master the 
following week for jdk-9+119. We then plan to backport the newer WebKit (to 
keep them in sync) to 8u-dev a couple weeks later.

The only new tool needed to build this is CMake [2] version 3.4 or later (we 
will use 3.4.1 to build).

Let me know if you have any questions.

-- Kevin

[1] https://bugs.openjdk.java.net/browse/JDK-8156698

[2] http://cmake.org/


 
  

JavaFX with Eclipse and JDK9

[Dr. Michael Paus]

I recently tried to get a JavaFX application running with the latest EA 
build of JDK9 from
within Eclipse but I failed. Can anybody on this list tell me what I 
have to do to get that
working? I have the latest milestone release of Eclipse Neon installed 
together with the
latest JDK9 and I have also installed the Java 9 Support (BETA) for 
Neon. I also installed
e(fx)clipse if that should matter. The problem is that I cannot access 
any of the JavaFX
packages. I even added a module-info.java file to the project which 
explicitly requires the
JavaFX modules but nothing helped so far. The JRE System Library only 
contains the modules
which are in the java.* namespace but none of the other modules 
especially the javafx.*
modules and I don't find any option to add these. Did anybody ever try 
this and succeeded?


Thanks, Michael

Re: HEADS-UP: plan to integrate a newer WebKit into 9-dev next week.

[Felix Bembrick]

 Can you at least let me know why the JavaFX usage of WebKit does *not* support 
WebGL when native WebKit itself always has?

Is there some technical or architectural barrier?

> On 27 May 2016, at 22:51, Kevin Rushforth  wrote:
> 
> No, I don't have anything further to add about WebGL, if that's what you are 
> asking.
> 
> As for moving to Blink, that would be a very large effort. We do not 
> currently plan to do this for JDK 10, but could reevaluate it in the future 
> if something changes.
> 
> -- Kevin
> 
> 
> Felix Bembrick wrote:
>> Any comments on this? Isn't it time to move to Blink?
>> 
>>  
>>> On 13 May 2016, at 04:32, Felix Bembrick  wrote:
>>> 
>>> Thanks Kevin.
>>> 
>>> I was more curious as to why WebGL support hasn't been there since day 1, 
>>> given that WebKit itself supports it.
>>> 
>>> Felix
>>> 
>>>
 On 13 May 2016, at 01:52, Kevin Rushforth  
 wrote:
 
 It was an issue of resources versus priority and scope. JDK 9 is focused 
 on Jigsaw modularity and a few other minor features. It is more of a 
 "smoothing out" release than a big feature release (except for Jigsaw). We 
 expect JDK 10 to be a somewhat more feature-oriented release.
 
 -- Kevin
 
 
 Felix Bembrick wrote:
  
> Do you mind if I ask what the rationale behind such a decision is?
> 
> From an admittedly perhaps totally ignorant outside observer, it would 
> seem to me that any cost/benefit analysis would basically put this 
> feature in the "no brainer" category and should have been implemented at 
> the very least since JFX 8.
> 
> 
>
>> On 12 May 2016, at 01:11, Kevin Rushforth  
>> wrote:
>> 
>> No. WebGL support is not planned for JDK 9. We will look at this for JDK 
>> 10.
>> 
>> -- Kevin
>> 
>> 
>> Felix Bembrick wrote:
>> 
>>  
>>> Will this new WebKit finally support WebGL?
>>> 
>>> Just by supporting WebGL in the JavaFX WebView will instantly enable an 
>>> entire new set of 3D features and access to a plethora of JavaScript 3D 
>>> libraries for "free".
>>> 
>>> And, Google Maps will finally work too.
>>> 
>>> 
>>>
 On 11 May 2016, at 08:20, Kevin Rushforth  
 wrote:
 
 All,
 
 As a heads-up, we plan to push an updated WebKit to FX 9-dev early 
 next week [1]. If there are no build problems, they will be integrated 
 to 9 master the following week for jdk-9+119. We then plan to backport 
 the newer WebKit (to keep them in sync) to 8u-dev a couple weeks later.
 
 The only new tool needed to build this is CMake [2] version 3.4 or 
 later (we will use 3.4.1 to build).
 
 Let me know if you have any questions.
 
 -- Kevin
 
 [1] https://bugs.openjdk.java.net/browse/JDK-8156698
 
 [2] http://cmake.org/
 
 
  

Re: [9] review request: 8131888: Deliver javafx.swt as a modular jar in JDK 9

[Kevin Rushforth]

Thanks for confirming. So it sounds like we have a workable plan.

-- Kevin


Alan Bateman wrote:



On 27/05/2016 13:47, Kevin Rushforth wrote:


The qualified exports are done using reflection to the calling module 
that contains the javafx.embed.swt.FXCanvas class, irrespective of 
the name of the module (so it works even when the javafx.embed.swt 
package is in the unnamed module). I plan to file a follow-on bug to 
tighten the integrity checks, which may or may not include requiring 
it to be in a module named "javafx.swt", depending on whether all of 
the use cases can be done with javafx-swt.jar being loaded in a named 
module (e.g., Mandy's recommendation of using the Layer API).
Okay and using addExports is really the only way this will work when 
javafx.swt is a child layer.


As regards the mixing of code in named modules and unnamed modules 
then it should work fine. javafx.swt will read all modules in the boot 
layer. Code this module will also link to SWT types and for that to 
work then they must be visible by means of its class loader. The 
simplest is to just specify that loader as the parent class loader 
when creating the child layer.


-Alan

Re: [9] review request: 8131888: Deliver javafx.swt as a modular jar in JDK 9

[Alan Bateman]

On 27/05/2016 13:47, Kevin Rushforth wrote:


The qualified exports are done using reflection to the calling module 
that contains the javafx.embed.swt.FXCanvas class, irrespective of the 
name of the module (so it works even when the javafx.embed.swt package 
is in the unnamed module). I plan to file a follow-on bug to tighten 
the integrity checks, which may or may not include requiring it to be 
in a module named "javafx.swt", depending on whether all of the use 
cases can be done with javafx-swt.jar being loaded in a named module 
(e.g., Mandy's recommendation of using the Layer API).
Okay and using addExports is really the only way this will work when 
javafx.swt is a child layer.


As regards the mixing of code in named modules and unnamed modules then 
it should work fine. javafx.swt will read all modules in the boot layer. 
Code this module will also link to SWT types and for that to work then 
they must be visible by means of its class loader. The simplest is to 
just specify that loader as the parent class loader when creating the 
child layer.


-Alan

Re: HEADS-UP: plan to integrate a newer WebKit into 9-dev next week.

[Kevin Rushforth]

No, I don't have anything further to add about WebGL, if that's what you 
are asking.


As for moving to Blink, that would be a very large effort. We do not 
currently plan to do this for JDK 10, but could reevaluate it in the 
future if something changes.


-- Kevin


Felix Bembrick wrote:

Any comments on this? Isn't it time to move to Blink?

  

On 13 May 2016, at 04:32, Felix Bembrick  wrote:

Thanks Kevin.

I was more curious as to why WebGL support hasn't been there since day 1, given 
that WebKit itself supports it.

Felix



On 13 May 2016, at 01:52, Kevin Rushforth  wrote:

It was an issue of resources versus priority and scope. JDK 9 is focused on Jigsaw 
modularity and a few other minor features. It is more of a "smoothing out" 
release than a big feature release (except for Jigsaw). We expect JDK 10 to be a somewhat 
more feature-oriented release.

-- Kevin


Felix Bembrick wrote:
  

Do you mind if I ask what the rationale behind such a decision is?

From an admittedly perhaps totally ignorant outside observer, it would seem to me that 
any cost/benefit analysis would basically put this feature in the "no brainer" 
category and should have been implemented at the very least since JFX 8.




On 12 May 2016, at 01:11, Kevin Rushforth  wrote:

No. WebGL support is not planned for JDK 9. We will look at this for JDK 10.

-- Kevin


Felix Bembrick wrote:

  

Will this new WebKit finally support WebGL?

Just by supporting WebGL in the JavaFX WebView will instantly enable an entire new set of 
3D features and access to a plethora of JavaScript 3D libraries for "free".

And, Google Maps will finally work too.




On 11 May 2016, at 08:20, Kevin Rushforth  wrote:

All,

As a heads-up, we plan to push an updated WebKit to FX 9-dev early next week 
[1]. If there are no build problems, they will be integrated to 9 master the 
following week for jdk-9+119. We then plan to backport the newer WebKit (to 
keep them in sync) to 8u-dev a couple weeks later.

The only new tool needed to build this is CMake [2] version 3.4 or later (we 
will use 3.4.1 to build).

Let me know if you have any questions.

-- Kevin

[1] https://bugs.openjdk.java.net/browse/JDK-8156698

[2] http://cmake.org/


  

Re: [9] review request: 8131888: Deliver javafx.swt as a modular jar in JDK 9

[Kevin Rushforth]

Alan Bateman wrote:


On 26/05/2016 16:38, Kevin Rushforth wrote:
Yes, I've tested it in both modes (with a simple HelloFXCanvas 
program) -- as an automatic jar file and as just an ordinary jar on 
the classpath.
Just curious, if there are qualified exports to javafx.swt then how it 
does when on the class path?


The qualified exports are done using reflection to the calling module 
that contains the javafx.embed.swt.FXCanvas class, irrespective of the 
name of the module (so it works even when the javafx.embed.swt package 
is in the unnamed module). I plan to file a follow-on bug to tighten the 
integrity checks, which may or may not include requiring it to be in a 
module named "javafx.swt", depending on whether all of the use cases can 
be done with javafx-swt.jar being loaded in a named module (e.g., 
Mandy's recommendation of using the Layer API).


-- Kevin

Re: [9] review request: 8131888: Deliver javafx.swt as a modular jar in JDK 9

[Alan Bateman]

On 26/05/2016 16:38, Kevin Rushforth wrote:
Yes, I've tested it in both modes (with a simple HelloFXCanvas 
program) -- as an automatic jar file and as just an ordinary jar on 
the classpath.
Just curious, if there are qualified exports to javafx.swt then how it 
does when on the class path?


-Alan

Re: HEADS-UP: plan to integrate a newer WebKit into 9-dev next week.

[Felix Bembrick]

Any comments on this? Isn't it time to move to Blink?

> On 13 May 2016, at 04:32, Felix Bembrick  wrote:
> 
> Thanks Kevin.
> 
> I was more curious as to why WebGL support hasn't been there since day 1, 
> given that WebKit itself supports it.
> 
> Felix
> 
>> On 13 May 2016, at 01:52, Kevin Rushforth  wrote:
>> 
>> It was an issue of resources versus priority and scope. JDK 9 is focused on 
>> Jigsaw modularity and a few other minor features. It is more of a "smoothing 
>> out" release than a big feature release (except for Jigsaw). We expect JDK 
>> 10 to be a somewhat more feature-oriented release.
>> 
>> -- Kevin
>> 
>> 
>> Felix Bembrick wrote:
>>> Do you mind if I ask what the rationale behind such a decision is?
>>> 
>>> From an admittedly perhaps totally ignorant outside observer, it would seem 
>>> to me that any cost/benefit analysis would basically put this feature in 
>>> the "no brainer" category and should have been implemented at the very 
>>> least since JFX 8.
>>> 
>>> 
 On 12 May 2016, at 01:11, Kevin Rushforth  
 wrote:
 
 No. WebGL support is not planned for JDK 9. We will look at this for JDK 
 10.
 
 -- Kevin
 
 
 Felix Bembrick wrote:
 
> Will this new WebKit finally support WebGL?
> 
> Just by supporting WebGL in the JavaFX WebView will instantly enable an 
> entire new set of 3D features and access to a plethora of JavaScript 3D 
> libraries for "free".
> 
> And, Google Maps will finally work too.
> 
> 
>> On 11 May 2016, at 08:20, Kevin Rushforth  
>> wrote:
>> 
>> All,
>> 
>> As a heads-up, we plan to push an updated WebKit to FX 9-dev early next 
>> week [1]. If there are no build problems, they will be integrated to 9 
>> master the following week for jdk-9+119. We then plan to backport the 
>> newer WebKit (to keep them in sync) to 8u-dev a couple weeks later.
>> 
>> The only new tool needed to build this is CMake [2] version 3.4 or later 
>> (we will use 3.4.1 to build).
>> 
>> Let me know if you have any questions.
>> 
>> -- Kevin
>> 
>> [1] https://bugs.openjdk.java.net/browse/JDK-8156698
>> 
>> [2] http://cmake.org/
>> 
>> 

[webkit] [9] Review request for 8157509: UserDataDirectoryTest fails on Windows platforms with updated WebKit

[Arunprasad Rajkumar]

Hello Kevin, Guru, Murali,

Please review the fix for UserDataDirectoryTest failure.

JIRA: https://bugs.openjdk.java.net/browse/JDK-8157509

Webrev: http://cr.openjdk.java.net/~arajkumar/8157509/webrev.00

Issue: New WebKit takes around 5 mins to close the sqlite-db file 
associated with localStorage. Problem is evident in Windows because of 
the file system behavior.


Solution: Try File.delete(..), if it fails defer the deletion task to VM 
shutdown using File.deleteOnExit(..).


Regards,
Arun

Re: [9] review request: 8131888: Deliver javafx.swt as a modular jar in JDK 9

[Tom Schindl]

Do you have an example how to construct such a Layer?

Tom

Von meinem iPhone gesendet

> Am 26.05.2016 um 17:47 schrieb Mandy Chung :
> 
> 
>> On May 26, 2016, at 8:38 AM, Kevin Rushforth  
>> wrote:
>> 
>> Yes, I've tested it in both modes (with a simple HelloFXCanvas program) -- 
>> as an automatic jar file and as just an ordinary jar on the classpath.
> 
> an automatic module needs to be on modulepath.
> 
> For container-like environment, it can create a Layer to load javafx.swt with 
> a parent class loader that loads SWT classes - would that be feasible?
> 
> Mandy
> 
>> 
>> -- Kevin
>> 
>> 
>> Tom Schindl wrote:
>>> Rereading the jira it take that back if javafx.swt can still be loaded as a 
>>> simple jar things will work
>>> 
>>> Tom
>>> 
>>> Von meinem iPhone gesendet
>>> 
>>> 
>>> 
 Am 26.05.2016 um 16:51 schrieb Tom Schindl 
 :
 
 Hi,
 
 I highly doubt this will work in an OSGi-Env like Eclipse (which the 99%) 
 use case for SWT useage.
 
 The SWT jar is not on the application classpath so how should a module 
 (named or unnamed) find the SWT classes?
 
 Tom
 
 Von meinem iPhone gesendet
 
 
 
> Am 26.05.2016 um 02:43 schrieb Mandy Chung 
> :
> 
> 
> 
> 
> 
>> On May 25, 2016, at 3:38 PM, Kevin Rushforth 
>> wrote:
>> 
>> Please review the following:
>> 
>> 
>> https://bugs.openjdk.java.net/browse/JDK-8131888
>> http://cr.openjdk.java.net/~kcr/8131888/webrev.00/
>> 
>> 
>> This adds support for the javafx.embed.swt package back into the JDK, 
>> which will be delivered as an automatic module in 
>> $JAVA_HOME/lib/javafx-swt.jar (final location is TBD).
> The approach to have javafx.swt be an automatic module that can access 
> org.eclipse.swt.* (that may be from an unnamed module) sounds reasonable. 
>  I wonder what the JAR file should be named -  javafx.swt.jar or 
> javafx-swt.jar?  They both have the same module name “javafx.swt”.
> 
> I skimmed through the change.  There are several System.err.println calls 
> that I assume are debugging code to be removed. e.g.
> 
> FXCanvas.java
> 247 System.err.println("FXCanvas class successfully initialized”);
> 294 System.err.println("FXCanvas: FX platform is 
> initlialized”);
> 
> PlatformImpl.java
> 308 System.err.println("FXCanvas: no permission to access 
> JavaFX internals");
> 309 ex.printStackTrace();
> 
> I reviewed mainly addExportsToFXCanvas and addExportsToFXCanvas methods.  
> Happy to see StackWalker be useful in this case.  The check to compare 
> the class name with “javafx.embed.swt.FXCanvas” to derermine whether 
> qualified exports should be added.  You can consider checking the 
> caller's module name as a starter.  I know you are planning to look into 
> the integrity check as a follows up.
> 
> ModuleHelper.java
> 57 // ignore
> 
> This deserves to be an InternalError.  This is temporary until FX is 
> transitioned to be built with JDK 9.
> 
> Otherwise, look fine to me.
> Mandy
> 

RE: Mouse events blocked during DnD inside JFXPanel - bug or limitation?

[Fisher, Robert]

Sorry I forgot to add - I'm using 1.8.0_66 on Windows 7.

Cheers,
Rob

-Original Message-
From: openjfx-dev [mailto:openjfx-dev-boun...@openjdk.java.net] On Behalf Of 
Fisher, Robert
Sent: Freitag, 27. Mai 2016 10:07
To: openjfx-dev@openjdk.java.net
Subject: Mouse events blocked during DnD inside JFXPanel - bug or limitation?

Hi all,

When inside a JFXPanel, after DnD has been started on a node and content put 
the dragboard, mouse-exited events for the node do not fire until the drag 
gesture is over.

Is this a known bug, new bug, or a limitation of using Swing + FX together?

Check out the test program below. Any input would be appreciated.

Cheers,
Rob

public class Main extends Application {

// Set to true to test behaviour when embedded inside a JFXPanel.
private static final boolean EMBED_IN_SWING = true;

public static void main(String[] args) {
if (EMBED_IN_SWING) {
SwingUtilities.invokeLater(() -> {
JFXPanel jfxPanel = new JFXPanel();
JFrame frame = new JFrame();
frame.add(jfxPanel);
frame.setDefaultCloseOperation(WindowConstants.EXIT_ON_CLOSE);
frame.setSize(800, 600);
frame.setVisible(true);
Platform.runLater(() -> {
Scene scene = createScene();
jfxPanel.setScene(scene);
});
});
} else {
launch(args);
}
}

@Override
public void start(Stage primaryStage) {
Scene scene = createScene();
primaryStage.setScene(scene);
primaryStage.show();
}

private static Scene createScene() {
Rectangle rectangle = new Rectangle(50, 50);

rectangle.hoverProperty().addListener((v, o, n) -> 
System.out.println("Hover property: " + n));
rectangle.addEventFilter(MouseEvent.MOUSE_ENTERED, event -> 
System.out.println("Mouse entered"));
rectangle.addEventFilter(MouseEvent.MOUSE_EXITED, event -> 
System.out.println("Mouse exited"));

rectangle.setOnDragDetected(event -> {
Dragboard db = rectangle.startDragAndDrop(TransferMode.COPY);
ClipboardContent content = new ClipboardContent();
content.putString("Hello World");
db.setContent(content);
event.consume();
});

StackPane stackPane = new StackPane(rectangle);
return new Scene(stackPane, 800, 600);
}
}