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
> 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 delive
Mandy,
Thanks for your feedback. Comments inline.
Mandy Chung wrote:
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
If you add javafx-swt.jar to the custom classpath created by the OSGI
container it should work in the same way it does today when you add
jfxswt.jar.
Can you suggest an easy way that I can test this?
-- Kevin
Tom Schindl wrote:
Hi,
I highly doubt this will work in an OSGi-Env like Eclipse
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.
-- 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 mein
> 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 ca
I'll prepare a simple osgi swt test app
Tom
Von meinem iPhone gesendet
> Am 26.05.2016 um 17:38 schrieb Kevin Rushforth :
>
> 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.
>
> -- Kevin
>
>
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 :
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 useag
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 automa
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 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 o
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 t
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
> 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(), Se
15 matches
Mail list logo