Java desktop links of the week, October 21

A relatively quiet week this week – it seems people are recovering after JavaOne, or getting prepared for all the Java-related conferences that seem to kick off this time of the year in Europe! 🙂 In any case, enjoy the links from the past week and I’ll catch you again next week with more 🙂

JavaFX

  • The big news this week is that the OpenJFX project announced it is now fully open source (barring source code that cannot be open sourced as it is not owned by Oracle). This announcement came due to the release of the media source code.
  • With the recent release of ControlsFX 8.0.2, I interviewed Eugene Ryzhikov to introduce one of the main guys behind the project and to see where he sees the project going in future releases.
  • Stephen Chin has announced that he will be interviewing James Gosling again on Wednesday, October 23rd at 8AM Hawaii Time, which is apparently 11AM PST. As Stephen notes, “during this broadcast we will show some of the footage of his aquatic robots, talk through the technologies he is hacking on daily, and do Q&A with folks on the live chat. “
  • Pedro Duque Vieira has revisited and improved his Metro styling for JavaFX. It’s great to see people working on ‘native’ styles for JavaFX. We now have both a Metro and an Aqua style for JavaFX.
  • Geertjan Wielenga has posted about CaseLnk Case Management System, which is built using JavaFX and the NetBeans Platform.
  • Andy Till has published code for his floaty-field JavaFX component. You can see an animation at the previous link to better understand what this is all about.
  • The IDR Solutions blog has two posts this week. Firstly, George Perry posts about his three big takeaways from rewriting some of their Swing code in JavaFX. Secondly, Kieran France has posted about his experiments with JavaFX and Java 8, particularly around printing in JavaFX 8.0.

2 thoughts on “Java desktop links of the week, October 21”

  1. I would really appreciate if the term ‘native’ wouldn’t be used in this context – it’s very misleading. More accurate would be ’emulates the system UI’ or ’emulates the native OS skin’. In my understanding ‘native’ means that the current skin of the OS is used and any change on the OS skin leads to related skin changes in the user application.

    1. This was why I put native in inverted commas – I agree with your statement. It’s an English subtlety I guess, but native and ‘native’ can mean two very different things 🙂

Leave a Reply