Hey Tom,
thanks for you answer. while the OSX font stuff is there and Orcale's goal is to use the native font renderer on each platform. I am sure there must be some kind of an Android font renderer in the code. I couldn't find one until now. Another question: Since I ported you latest jfx78 to Java6 it's now jfx678 ;) What would be the best way to contribute the port? Do you think it's good to contribute it to jfx78 or to have a separate jfx68 branch? regards Matthias Am 11.10.2013 um 18:22 schrieb Tom Schindl <tom.schi...@bestsolution.at>: > On 11.10.13 18:10, Matthias Hänel wrote: >> Hi Tomas, >> >> >> today, I took the time to investigate a little more time on this. >> >> 1. I build an entirely new openjfx78 build for android >> 2. starting this gave me several errors that lead me to the >> conclusion that I need a java6 openjfx >> 3. based on openjfx78 I ported it back to java6 (adapted gradled scripts, >> and tons of java source code) >> 4. Now it's almost running on an 18th android. All libraries are firing up >> until the CssStyleHelper >> is called with a static call to createStyleHelper. >> >> That looks like the font stuff is not in jfx78. That's why "new Font" >> returns with null and therefore > > On OS-X font stuff is definately there in jfx78, but the low-level font > stuff is loaded using reflection (at least this was the cause on robovm)! > > Tom
