Johan Vos

The reason is that the Java 11 runtime will check if the main class extends javafx.application.Application, and if that is the case, it strongly requires the javafx platform to be...

If there are enough people who would use this, I'm ok as well.

@andres can you target this PR to develop branch (instead of master)? That way, appveyor might pass. Also, can you comment on the suggestions from @svenreimers

Looking at PR#117 there was one file in the native webkit implementation that is changed: FontJava.cpp We don't use that on Android, but all the others are used. I think...

The difference is this: The "Single View Project" uses the "old" approach: JavaFX on top of Android/Dalvik, and using RoboVM which uses more or less the Harmonic classes (Java 6++)...

The basis for this is having Java on Android devices (as opposed to using the Android API's that somehow look like but definitely are not Java), and that takes time,...

The problem is in ` - (BOOL)performKeyEquivalent:(NSEvent *)theEvent` in `native-glass/mac/GlassView3D.m` That method always return `NO`, allowing the regular key processing to do its work. In case the action is processed...

You're right. The build rules for the default platforms has been converted from Qmake to Cmake, but the ARM build logic is not yet converted.

This is very likely related to JDK-8218424 indeed.

Relates to #826 (which can probably be closed in favor of this?)