NetBeans, the free open source IDE for Java and PHP, has reached version 7.1 and, with support for JavaFX 2.0, it's a more important upgrade than suggested by a decimal point increment.
NetBeans, the free open source IDE for Java and PHP, has reached version 7.1. In many ways this is more than a decimal point upgrade to NetBeans. The key fact is that this is the first IDE to support JavaFX 2.0 and IDE support is important if this new UI technology is going to get much general acceptance.
It supports JavaFX 2.0 in all three deployment models: Desktop, Applet and JNLP. It also features preloaders to improve the application loading experience and customised UI controls using CSS3. As a consequence CSS3 support has been generally improved with with code completion, syntax coloring and documentation for new CSS3 elements, and new browser specific properties settings.
Other general improvements include:
Java: Bulk refactoring tools enable project wide corrections and updates to code.
A new visual debugger helps control execution flow in terms of level structures in the UI.
Gap support in the GridBagLayout customizer visually maintains gaps in columns and rows.
Improved Javadoc highlighting and formatting and "inspect and refactor" allows project wide application on selected projects.
NeBeans 7.1 also supports JDK7, but this is only to be expected as is support for Oracle's WebLogic Server 12c and better GlassFish support.
As well as Java improvements, PHP use has also been improved: better PHP debugging; PHPUnit test groups capabilities; support for Smarty templates; and faster uploads with keep-alive for (S)FTP clients.
The IDE also has inVersion Control and Bug Tracking: Out-of-the-box, integrated Git support; new history tab on file editor window shows change history; locking/unlocking files in Subversion working directory; and support for mercurial branches and tags.
The conclusion has to be that, if you want to work with JavaFX, then you need to switch to NetBeans.
A recent security flaw in iOS is down to an error involving a spurious goto statement - but when you look a little more closely there is a bigger lesson to learn from the incident - and not just "goto [ ... ]