FontAwesome TTF is distributed with ControlsFX JAR, JavaDoc says it is not
See original GitHub issueThe JavaDoc of org.controlsfx.glyphfont.FontAwesome says:
Note that at present the FontAwesome font is not distributed with ControlsFX, and is, by default, instead loaded from a CDN at runtime.
But now the “fontawesome-webfont.ttf” IS distributed in the ControlsFX JAR: here.
JavaDoc should be revised.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (2 by maintainers)
Top Results From Across the Web
FontAwesome (ControlsFX Project 8.0.2) - javadoc.io
Note that at present the FontAwesome font is not distributed with ControlsFX, and is instead loaded from Bootstrap CDN at runtime. To use...
Read more >org.controlsfx.glyphfont.FontAwesome java code examples
Note that at present the FontAwesome font is not distributed with ControlsFX, and is, by default, instead loaded from a CDN at runtime....
Read more >Unanswered 'controlsfx' Questions - Stack Overflow
I am using this code to create a glyph from the most recent fontawesome that is not available on controlsfx: InputStream resourceAsStream =...
Read more >org.controlsfx.glyphfont.FontAwesome Maven / Gradle / Ivy
Note that at present the FontAwesome font is not distributed * with ControlsFX, and is instead loaded from Bootstrap CDN at runtime. *...
Read more >Compare Packages Between Distributions - DistroWatch.com
This can let us know which distribution is more up to date, ... In this way we can not only compare two competing...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Supporting JDK8 and JDK11+ is not a trivial task as there are binary breakages since JavaFX 9 (CSS api has been moved from private to public for example). Also all artifacts provide a
module-info.java
file that can only be compiled with JDK9+.Plugins like moditect could help in generating the module descriptors even of JDK8 is used. Ideally we could build MRJARs but Gradle’s support for it is dismal at best. Now that I think of it MRJARs would not work as the
ikonli-javafx
artifact must have explicit dependencies on the JavaFX APIs, which are distributed differently since JDK11 thus 2 distinct artifacts must be published.Let me think about this as it’s mostly a build problem.
No, it works for 8 and 11.
Alexander Krimm notifications@github.com schrieb am Do. 31. Okt. 2019 um 22:10:
– Dirk Lemmermann
Software & Consulting Zurich, Switzerland +41-(0)79-800-23-20 http://www.dlsc.com mailto:dlemmermann@gmail.com