...
You can then leave the command line (hopefully forever!) and do all the rest of your work from within your IDE. No, really!
The "Gradle Support" module for NetBeans 7.3 was previously installed in my NetBeans instance. After running 'gradle netBeans', I then opened the javafx project with NetBeans and all of JavaFX is available for me and ready to go, even including native code. Its all there.
In order to perform a build from NetBeans, you simply have to hit the build button. To run a specific file (such as a sample), find the sample in the source tree (NOTE: Samples not setup yet as of 3/23/2013), right click and choose "run".
The experience in IDEA is similar. After running 'gradle idea', you open the "javafx" project. We will have already generated the project, workspace, and module settings for you. Many settings will have already been configured to be shared across all developers working on the project, such as the number of spaces per indent and the use of spaces instead of tabs.
IDEA and Eclipse differ from NetBeans in that they maintain their own compiled classes and maintain their own build. That is, while you can (and need to at times) run the Gradle build script in order to build, for example an SDK or the JavaDoc for the entire project or run all of the tests in the right way, most of the time you will end up just working in IDEA like you would for any other project. There are caveats though (such as making sure the JDK you have configured for the project does not have jfxrt.jar on its classpath!). This will all be documented separately.
You can setup a run configuration for any gradle tasks you want to. In this screenshot above, IDEA has been configured to execute the top-level clean run target. You can specify any environment variables or Gradle properties to feed to the build. This can be very convenient when you have different configurations you want to build for (for example, you might have a configuration for building normally and another for building iOS or ARM).
Most of the time you will be able to just work from within your IDE, doing building and testing. Even when you need to execute actually tasks in the OpenJFX Gradle build script, you can do it easily from within the IDE. However, for the sake of understanding the nuts and bolts (and to avoid having to take screenshots from all three IDEs for the rest of this document), I will switch to executing all commands from the command line. In fact, one of the advantages to Gradle over Ant is the fantastic command line interface it provides.
Unique Challenges of Working on the JDK
...
Overview
Content Tools
ThemeBuilder