{"id":280,"date":"2012-09-27T22:53:22","date_gmt":"2012-09-27T20:53:22","guid":{"rendered":"https:\/\/mihosoft.eu\/?p=280"},"modified":"2013-02-07T22:57:02","modified_gmt":"2013-02-07T21:57:02","slug":"javafx-2-2-performance","status":"publish","type":"post","link":"https:\/\/mihosoft.eu\/?p=280","title":{"rendered":"JavaFX 2.2 Performance"},"content":{"rendered":"

JavaFX is a really powerful UI platform. I noticed a lot of momentum in Java as client technology. As JavaFX is now clearly the successor of Swing I will give it a try.<\/p>\n\n

I have created the Visual Programming Environment VRL-Studio<\/a> with Swing. I added a lot of features to the rendering\/animation\/effects pipeline. But for the next version I think of switching to JavaFX. But before I start with the real implementation I want to be sure that the performance is ok. Unfortunately, JavaFX still has some critical issues that are hopefully resolved in the near future.<\/p>\n\n

Issues<\/h2>\n\n

Performance seems to heavily depend on the graphics card\/driver\/OS. Even more important, the framerate of a JavaFX application drops as the size of the application stage increases. This does not only happen if nodes are drawn on the whole application window but also if only a part of the window shows content. If your application runs on a large screen, e.g., a 27″ iMac (2880×2560), this does really matter.<\/p>\n\n

Questions<\/h2>\n\n