Two bits of exciting news for IntelliJ IDEA’s users today. The first one is that the upcoming release of IntelliJ IDEA 12.1.2 is available for early preview. The new build brings many enhancements and bugfixes.
Good news for all who use Gradle in their projects. The newest update of IntelliJ IDEA brings new features and enhancements for the Gradle integration.
Now IntelliJ IDEA provides you additional configuration settings:
Use gradle wrapper — The IDE automatically detects if the linked gradle project is wrapper-aware and uses it for refreshing the project and running tasks;
Use auto-import — Every project structure change is automatically picked up by the IDE on Gradle project refresh (e.g. when a new library is added/removed at build.gradle, it’s added/removed at the IDE as well). Note, that user-defined project changes are not automatically overwritten. E.g. when a user manually adds a library dependency to a module it’s not automatically removed during the auto-import.
Service directory path — Allows to specify a location where Gradle stores downloaded library binaries. Useful for Windows’ users who may want to tune their anti-virus software.
Each year we celebrate Spring by rolling out a fresh update for the latest big release, with bugfixes and usability enhancements. This spring is no exception, so today we are excited to announce that IntelliJ IDEA 12.1 is finally out and available for download.
As you remember, IntelliJ IDEA 12 brought major improvements such as support for Java 8, Play 2, Android UI designer, a new compiler with double the performance, more database tools, and of course Darcula, the new dark look and feel. This update improves on most of these features and adds some new ones as well.
Support for JavaFX 2, Oracle’s new rich client platform for Java, now includes complete support for FXML markup, custom CSS, code completion, navigation and search, refactorings, packaging tools, and integration with SceneBuilder.
We are happy to announce that the first release candidate for IntelliJ IDEA 12.1 is out and available for download. The release candidate build as always comes with a new bunch of bugfixes and enhancements you have been waiting for.
Today we would like to answer the most frequent questions about file encodings in the IDE and show you a few tricks, which may help you to avoid potential pitfalls.
What is the problem with file encodings?
To be able to display the text correctly, IntelliJ IDEA needs to know which file encoding to use. Unfortunately, it is not always possible to tell the file encoding without additional information. Especially when single-byte encodings are used, there are multiple mappings possible.
This is the second part of the serie about Java FX 2 support in the upcoming IntelliJ IDEA 12.1. Today we would show some features dedicated to help you to skin your JavaFX application with CSS. We would use the same sample application we were using in the previous post.
As you know JavaFX allows to configure stylesheets for nodes in your .fxml. IntelliJ IDEA helps to complete existing .css files:
You may rename, move, etc your .css file, the reference would be updated accordingly. If you deside to add one more stylesheet and want to convert attribute value to subtag, the IDE would also help you here.
As you know, there’s only two weeks left before the long-awaited big update to IntelliJ IDEA 12.1. That’s why today we are announcing IntelliJ IDEA 12.1 EAP 129.17, one more public preview for the upcoming release, with more bugfixes and enhancements.
As usual, the full list of changes is available in Release Notes.
Thanks to everyone for sharing your feedback on the new features in our discussion forum and reporting bugs to the issue tracker. Your help and support is invaluable for us.