Lemmermann
Cc: OpenJFX
Assunto: Re: JavaFX-Bugs on GraalVM 19.3 (Java 11)
As I said a number of times, this is ground-breaking new area, and still
work in progress. There is a reason we start with "Hello, FX" and not with
"Launch Apollo 11".
If you expect a 100,000 lines of code
ev em nome de Johan
> Vos
> Enviado: quinta-feira, 21 de novembro de 2019 15:44
> Para: Dirk Lemmermann
> Cc: OpenJFX
> Assunto: Re: JavaFX-Bugs on GraalVM 19.3 (Java 11)
>
> As I said a number of times, this is ground-breaking new area, and still
> work in progress. Th
does not happen with standard jre.
Seems like a very hard to find bug.
Cheers.
De: openjfx-dev em nome de Johan Vos
Enviado: quinta-feira, 21 de novembro de 2019 15:44
Para: Dirk Lemmermann
Cc: OpenJFX
Assunto: Re: JavaFX-Bugs on GraalVM 19.3 (Java 11)
As I sa
As I said a number of times, this is ground-breaking new area, and still
work in progress. There is a reason we start with "Hello, FX" and not with
"Launch Apollo 11".
If you expect a 100,000 lines of code application to run without any issue
from day 1 on a new platform, yes, you might be disappoi
OK, I understand. But a real world application that already consists of say
10 lines of code with tons of dependencies would require an enormous amount
of work before the list of classes that need to be added to the reflections
list is complete. This would be a trial and error approach. Laun
Please file issues if you run into them:
* JavaFX related: http://bugs.openjdk.java.net/
* GraalVM related: https://github.com/oracle/graal/issues/
* Substrate related: https://github.com/gluonhq/substrate/issues
Keep in mind that with these new approaches come new docs, so make sure to
read them.
After experimenting a lot today with the Gluon client plugin I must assume that
currently not all of Java is supported via the substrate / GraalVM duo.
For example I was unable to use the java.util.Preferences API. I also got an
error that said Integer.parseInt() does not exist.
Is that correct?
We have samples showing how to build and run JavaFX applications using
GraalVM. See our blog post [1] with samples [2].
Keep in mind that JavaFX has some characteristics that make it non-trivial
to apply native-image out of the box (reflection/jni configuration,
platform-specific static libraries,
In thinking about it further, since these are likely Graal bugs, it
seems better to file them with the Graal team.
-- Kevin
On 11/21/2019 5:45 AM, Kevin Rushforth wrote:
My guess is that these are GraalVM bugs rather than JavaFX bugs, but
without debugging them it's hard to know for sure.
J
My guess is that these are GraalVM bugs rather than JavaFX bugs, but
without debugging them it's hard to know for sure.
Johan has spent a fair bit of time looking into running JavaFX on
GraalVM, so might have some additional insights.
As for bug tracking, I don't have a problem with using the
I am also observing issues related to text color. All of my labels show up in
blue instead of the color defined globally in my css file.
> On 20 Nov 2019, at 22:20, Michael Paus wrote:
>
> Hi,
>
> I would just like to know where JavaFX problems or bugs should be reported
> which are strictly
Hi,
I would just like to know where JavaFX problems or bugs should be reported
which are strictly related to running on the just released GraalVM 19.3 with
Java 11 support. Should they go into the regular JBS or should they be
reported
elsewhere?
For example: I have observed that a large JavaF
12 matches
Mail list logo
