José Pereda

@mipastgt good to know that works! As for the System Menu, that is a different issue. As you mentioned, using native-image, `getSystemMenu().isSupported()` returns false, because there is a [check](https://github.com/openjdk/jfx/blob/master/modules/javafx.graphics/src/main/native-glass/mac/GlassApplication.m#L1088) done...

JBS issue: https://bugs.openjdk.java.net/browse/JDK-8279463

The link for the JavaFX 11 docs is: https://openjfx.io/javadoc/11/ A link to the each of the JavaFX modules javadoc jars can be found in Maven central, like: https://repo1.maven.org/maven2/org/openjfx/javafx-graphics/11.0.1/javafx-graphics-11.0.1-javadoc.jar or you...

Playing with the workaround, it works fine, with the following consideration: NetBeans only adds javadoc/source jars for a jar with the exact same name and `-javadoc`/`-source` suffix. This means that...

For reference: Maven workaround: https://stackoverflow.com/questions/54278159/javafx-11-in-netbeans-10-with-maven-has-no-sources-javadocs NetBeans related issue: https://issues.apache.org/jira/browse/NETBEANS-1396

As this is constantly evolving I'm not updating this repo everyday... but you can use the latest snapshot of Charm-Down (0.0.4-SNAPSHOT) or the release version (0.0.3). Also you can use...

There is no support yet for AWT on Android, so any library that makes use of it should be excluded, if possible.

I don't see any relation between possible use of AWT with https://github.com/gluonhq/substrate/issues/840 I can't reproduce the issue deploying HelloGluon to Android with plugin 1.0.3 and Gluon's GraalVM, even if I...

There is a tentative workaround to avoid AWT references on Android, providing AWT is not used explicitly by the project. To test it use: gluonfx-maven-plugin version: 1.0.4-SNAPSHOT plugin repository: ```...

Submitted PR to fix this issue in OpenJFX: https://github.com/openjdk/jfx/pull/55 In the meantime setting a font should solve it.