Under all the same conditions, JavaFX-API may be more consistent across components. However, this depends more on how the code is written than the library used to write the code.
It depends greatly on what you are building. Swing has more components (third party and embedded type), not all components are in the new JavaFX platform, so if you need something you need some reinvent of the wheel It may become. On the other hand, if you want to run conversion / animation / video content, FX is easier.
Another thing to keep in mind is (probably) a look and feel. If you need to have a default system look and feel, JavaFX (now) does not provide this functionality. I do not need it (I prefer the default FX look), but I know that depending on the policy you need to restrict system style.
Personally, I think that JavaFX is a UI library that will be released soon. It does not exist completely yet (although it is not only usable). Swing is a full-fledged UI library currently fully functional and supported. It will be very large in the coming years (so foreign exchange may exceed that at some point.)
JavaFX can be a GUI toolkit for Java (GUI is a brief introduction of the graphical user interface). With JavaFX you can easily write desktop applications and games in Java. Thanks to the proposed Java GUI toolkit, JavaFX replaced Swing. More importantly, JavaFX is more consistent in style than Swing and there are other choices. There are also other ways of setting up a layout file (XML) that is the victim of the GUI and evaluating them using CSS just as familiar in web applications. JavaFX integrates the second 3D graphics, graphics, audio, video, and embedded web applications into a consistent GUI toolkit. It is lightweight and hardware acceleration has been enhanced. We support a wide range of operating systems as well as Windows, UNIX system, Mac OS.
Returning to JavaFX 1.3, you can embed Swing in JavaFX, but not vice versa. At least it can not be officially done. I implemented a Swing component that embeds JavaFX content (called JXScene) in Swing and makes it available for publication in the jfxtras project. This is the only way to embed JavaFX scenes in Swing applications. Oracle with JavaFX 2.X incorporates the official method of JavaFX into Swing, but unfortunately we can not embed Swing in JavaFX. In most cases this is enough. However, in future JavaFX 8, you can also use the Swing node to embed swing components in JavaFX applications.
I think JavaFX will be the way to develop desktop applications, but I am surprised if you see many web applications as your first project. Once Java 7 and JavaFX are released, people will see more FX, people will strip out their Windows XP machine. At the same time, I regard JavaFX as a desktop framework for developing desktop applications. The downside of Swing is that it seems like there is no plan to add new features. Another disadvantage is that JavaFX is a fantastic new toolkit. Easily do everything, but Swing can only do a lot of work. As JavaFX grows, I think that more and more people will be installing user interfaces using Swing UI using JavaFX components.