Welcome to another weeks worth of links. I should note that I’m back in New Zealand after a week in the US, and I was a little distracted last week, so some links may have slipped through the cracks. Sorry if I miss anybodies hard work! 🙂
- Probably the biggest news of the past week was that Niklas Therning has managed to get JavaFX running on iOS devices by combining OpenJFX with Apache Harmony and RoboVM.
- Tom Schindl has made available builds of Eclipse that work with Java 8, which is really useful for anyone developing JavaFX now that it has switched to depending on some Java 8 features and API. I intend to switch back to Eclipse ASAP.
- Gerrit Grunwald has once again updated his validation UI feedback API, improving it to not draw validation feedback for invisible fields.
- Speaking of Gerrit, he has also posted a new (JavaFX 2.x) toggle button control.
- Danno Ferrin has released version 0.3.0 of the JavaFX Gradle Plugin. As he says in the post, “new in this release is the ability to specify a particular JVM to package with your native bundles and the ability to customize platform-specific build options. Some configuration options and conventions also moved around to support these two features, most notably the plugin no longer automatically self-signs the code.”
- Hendrik Ebbers has posted part two of his series on ‘designing JavaFX business applications‘. This post discusses the limitations of FXML, and makes a proposal on how to improve this.
- Sean Phillips has been working on a ‘JavaFX Accordion slide-out menu for the NetBeans Platform‘.
- The Canoo blog has a post on AfterburnerDolphin, which is (rather obviously) a combination of the AfterBurner.fx project by Adam Bien and the OpenDolphin project by Canoo.
- Granite Data Services 3.0.0.M2 is out and available for download here, and you can read the announcement on their website.
- Robert Ladstätter has posted on 2D Image Filters with OpenCV and JavaFX.
- Asko K has put up a small code snippet to test out JavaFX 3D features (in his case specifically on Mac OS X).
That’s all this week. Catch you again next week!
Just to make it crystal clear. Only people who want to work on the JavaFX8 codebase have to use the beta builds I make available.
Developers who only want to code against JavaFX8 can still use the default EclipseSDK+ e(fx)clipse tooling!
Wow, great news about JavaFX on iOS. I didn’t realize it could happen so soon.
This will be a great help for my project.