First major release

Eclipse meets JavaFX: What’s new in e(fx)clipse 1.0?

Coman Hamilton
1.2

Eclipse’s IDE tooling and runtime platform for JavaFX is bring out its first major release

Once upon a time, there was an IDE called Eclipse that
had absolutely no support for JavaFX. Developers often resorted to
using Eclipse’s rival NetBeans for JavaFX applications. And then
along a man called Tom Schindl from the Eclipse development team,
who developed a magical tool called e(fx)clipse. And Eclipse and JavaFX
lived happily ever after.

Having debuted with its 0.0.1 release in 2011,
e(fx)clipse has made its way (through numerous bug fixes and
enhancements) to its first major release (1.0), scheduled for
August 15.

JavaFX UIs in Eclipse

The tooling and runtime platform is designed for
developers that want to use Eclipse to create JavaFX UIs and
modular JavaFX applications with a modern architecture like OSGi or
Dependency Injection.

Project leader Tom Schindl previously told
JAXenter
that e(fx)clipse’s main goal is to “provide tooling to
author JavaFX 2.0 applications using the Eclipse IDE.” In other
words, the e(fx)clipse toolkit means that any developer that wants
to develop applications with Eclipse as their primary IDE no longer
needs to switch to rivals like NetBeans for tooling support.

Alongside integration of the SceneBuilder, the latest
version will also be JavaFX 8 ready, meaning that Java developers
can also make use of lambdas.

Project leader Tom Schindl presented a few new
functions on his
blog
, including the new new helper which generates
get*/Set*/*Property methods for JavaFX. There’s also going to be a
new wizard to help developers create getters and setters.

You can find the latest e(fx)clipse addons and bundles over here.

Author
Coman Hamilton
Before becoming Editor of JAXenter.com (S&S Media Group), Coman completed an M.A. in Cultural Studies and wrote for numerous websites and magazines, as well as several ad agencies. // Want to submit a story? Get me at coman[AT]jaxenter.com or linkedin.com/in/comanhamilton
Comments
comments powered by Disqus