Now that the first public Developer Preview of SceneBuilder 2.0 is close to be made available it's time to update NetBeans so that it can interoperate with it.
The overall idea is to keep NB's code able to starts SB 1.0 and 1.1 and add new case for SB 2 so that by order or priority NB will try to locate SB 2 then 1.1 then 1.0.
Default installation dir of SB 2 is:
- on a Windows 32-bit system
C:\Program Files\Oracle\JavaFX Scene Builder 2.0
- on a Windows 64-bit system
C:\Program Files (x86)\Oracle\JavaFX Scene Builder 2.0
- on a MacOS system
/Applications/JavaFX Scene Builder 2.0
- on a Linux system
The executable launcher has the same name where 1.1 is replaced by 2.0 (but on Mac NB calls script scenebuilder-launcher.sh, no change here).
For what is about the content of the SB 2 product note that there's a few changes.
On all platforms SB 2 is now made of 2 jar files SceneBuilderApp.jar and SceneBuilderKit.jar.
The overall layout remains identical from SB 1.1 to SB 2.
However on MacOS the file scenebuilder.properties isn't handled the same way.
In SB 1.1 it is duplicated, you have it in:
In SB 2 the first location disappears, remains only Contents/Resources/Java/scenebuilder.properties.
You'll notice the move of scenebuilder.policy but I don't think this file is involved in interop.
Let me know if I forgot something you guys need.
before Christmas I made a change (as a bug fix) that should add the support for version 2.0. Also the auto detection mechanism should work as described (trying 2.0 first).
Can you please give it a try? Please report back here if something doesn't work in Dev build of NetBeans.
Thanks and All the best in the year 2014!
It looks great on both Windows 7 and 8.1. I started using it on 16-Dec, flipping back and forth between Scene Builder versions. Verified fixed in Bug 238520 and today using:
Product Version: NetBeans IDE Dev (Build 201401020002)
Java: 1.8.0-ea; Java HotSpot(TM) Client VM 25.0-b63
Runtime: Java(TM) SE Runtime Environment 1.8.0-ea-b121
System: Windows 7 version 6.1 running on x86; Cp1252; en_US (nb)
System: Windows 8 version 6.2 running on x86; Cp1252; en_US (nb)
I'll ask Banu to check it on Mac, and Amr on Ubuntu just to be sure all bases are covered on this important one. Added to cc: list, and I'll gen up a test case for it.
Please make sure it integrates well with Maven projects:
Currently, SceneBuilder 2.0 standalone is pretty unusable as soon as you have some third-party controls in the FXML.
And there are also issues if you have images in a different directory than the Java source files etc.
Now that Oracle no longer provides binary builds of SceneBuilder, NetBeans should integrate it directly into the IDE (or at least bundle a recent binary build of it).
I think so too. You have a very nive tool with mantisse for Swing right inside the IDE and the same should be done with the JavaFX Scene builder. Sure you can have the standalone too for eclipse and intelliJ but to bring the best together, you should integrate it right into netbeans. I don't want to use and install another design tool. For me the swing gui designer is good and if I want to use JavaFX, it should be integrated too to use it in netbeans.