Skip to main content

Blog Archive for opinali during June 2009

Property binding is a great feature of JavaFX Script, but it's not without its issues, limitations or risks as you can see in recent posts. But even if perfect, no programming language feature exempts the programmer from learning how to use it optimally. There is an important rule that you must follow for binding. Check this code (simplified, from the JavaFX Balls benchmark): <p>public...
Fabrizio says: "You'd have problems in forcing it to a broader scope than the one it has been designed for." (i.e., GUIs) This may be true, but only because JavaFX Script is still a bit recent in both design and implementation. A few important features are still missing, some only not included due to time/resource constraints because the team's priority is the features to make JavaFX a...
Check first part here. By just adding -server, I got the following results (standard runs, without removing the toolbar or any other tricks): 16 Balls @ 980fps (1% CPU): 1.47X faster than HotSpot Client; 128 Balls @ 460fps (14% CPU): 1.39X faster; Adaptive mode / 285 Balls @ 200fps (20% CPU): 1.28X more load; Adaptive mode / 610 Balls @ 60fps (24% CPU) : 1.08X more load; HotSpot Server is not...
Migration JavaFX 1.2 is not a fully backwards compatible release. There are language and API changes, and the compiled code is not binary compatible even for sources that still compiles without changes in the new version. Check Stephen Chin's migration guide. This continues the trend of 1.1; it seems Sun is not yet caring too hard about backwards compatibility. "Legacy" JavaFX 1.0 and 1...