FX Experience Has Gone Read-Only

I've been maintaining FX Experience for a really long time now, and I love hearing from people who enjoy my weekly links roundup. One thing I've noticed recently is that maintaining two sites (FX Experience and JonathanGiles.net) takes more time than ideal, and splits the audience up. Therefore, FX Experience will become read-only for new blog posts, but weekly posts will continue to be published on JonathanGiles.net. If you follow @FXExperience on Twitter, I suggest you also follow @JonathanGiles. This is not the end - just a consolidation of my online presence to make my life a little easier!

tl;dr: Follow me on Twitter and check for the latest news on JonathanGiles.net.

JavaFX links of the week, June 27

Here we go again, with this weeks batch of links. Thanks to the people contacting me with links and praise – it’s all much appreciated 🙂 Anyway, let’s get into things…

That’s all for this weeks folks. Keep up the blogging and exploring of the Java desktop APIs. Catch you in a weeks time! 🙂

JavaFX 2.0 beta build 32 available now

Time to hit the Oracle download servers for a brand new build of the JavaFX 2.0 beta. This build brings with it 2 weeks of bug fixes, optimisations and features. If you’re on an older release (b28 or b30), it’s time to get downloading! 🙂

Also, thanks to everyone filing bugs and feature requests into our Jira issue tracker. It’s your feedback that we’re using to polish the beta releases. I hope that you’ll keep providing your useful feedback throughout the beta release train.

JavaFX links of the week, June 20

Another week of JavaFX links – hopefully you all find something of interest. Also, thanks to everyone emailing me links!

That’s all I have for you this week. I’ll see you in a weeks time 🙂

JavaFX Code Names

I was just going through the bug database and realized that, to my knowledge, we’ve never actually told people what the code names are for our releases, and that that is pretty useful to know when filing bugs. Ever since JavaFX 1.0 we’ve used street or area names from San Francisco as our code names. Honestly I can’t remember the 1.0 code name anymore. 1.2 was called “Marina”, 1.3 was “SoMa” (South of Market).

This release, 2.0, is called “Presidio”, and the next major release is called “Lombard”. So when you see that your issue is targeted at one of these, you know what we’re taking about! If it remains “untargeted”, then it has gone into the pool from which we draw features for future releases, but may not be targeted to a specific release until later in the planning cycle.

JavaFX links of the week, June 13

Another week, another batch of links. Let’s just get right into it!

  • GroovyFX was announced this week by Jim Clarke, which is a library that makes building JavaFX 2.0 user interfaces easier (when written in Groovy, obviously). The features include a SceneGraphBuilder, TimelineBuilder, bind syntax and a GroovyDSL to support colors, durations, timelines, enumerations, etc. I’m very excited to see alternate JVM languages starting to adopt JavaFX 2.0 now that it is all Java-based.
  • Speaking of alternate JVM languages, here are two blog posts by Emil Kruczek about using JavaFX 2.0 in Clojure.
  • Tom Schindl has taken JavaFX 2.0 for a spin, and thinks that JavaFX 2.0 is looking pretty good, which is kind considering he is an SWT fan. Despite this, he says that “[t]his makes me a bit sorry about SWT because compared to what JavaFX provides to me SWT is light years behind.”
  • In a separate post, Tom blogs about using Xtext to create a JavaFX-CSS editor, which, he theorises, could quite nicely become part of an Eclipse JavaFX 2.0 plugin (along with other Eclipse-based techonologies).
  • Rafał Rusin has blogged about visualising GIS data in JavaFX 2.0 beta using GeoTools.
  • I put up a link to my in-progress JavaFX Control Cell Factories project. Currently you can just check out the (clearly beta quality) screenshots and see what the API looks like (hint: fully static API with a lot of Callbacks – I can’t wait for closures to clean this up!).

That’s all for another week. I hope you all found something useful in the links above. Catch you again in a weeks time, and keep up all the hard work folks!