« Earthrise at Christmas 1968: An Apollo 8 Holiday Wish Echoed in JavaFX | Main | If a [JavaFX] Tweet Falls in the Forest, Does it Make a Sound? »

December 22, 2008

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00e54f133d698834010536926283970c

Listed below are links to weblogs that reference More Cowbell! An Imaginary Audio Control Example in JavaFX:

Comments

Jim Weaver

"I don't see anything about allowing Java classes to use compiled JavaFX classes just as easily as any other Java class, though, and this is -- as I mentioned -- when we would see a quantum leap in benefit for Java and JavaFX.

Do you know of any news on that front??"

Ari,

I don't know of any news on that front, but the way that I call JavaFX from Java code is by creating Java interfaces (method #1 in the following blog post).

http://blogs.sun.com/michaelheinrichs/entry/using_javafx_objects_in_java

Thanks,
Jim Weaver

Ari Goldstein

Thanks for responding so quickly!

I checked this out, and am glad to hear it -- I like some of the planned changes. I don't see anything about allowing Java classes to use compiled JavaFX classes just as easily as any other Java class, though, and this is -- as I mentioned -- when we would see a quantum leap in benefit for Java and JavaFX.

Do you know of any news on that front??

Thanks very much,

Ari

Jim Weaver

"I know -- but I may not need this enum in my Java code. I'd rather stay with the rapidity of the scripting language where possible, and save Java for the heavy lifting..."

Ari,

This was submitted as a desired feature by Martin Brehovsky (the JavaFX Production Suite guy), and comment on by Brian Goetz (JavaFX compiler team lead). See:

http://javafx-jira.kenai.com/browse/JFXC-1770

Thanks,
Jim Weaver

Ari Goldstein

I know -- but I may not need this enum in my Java code. I'd rather stay with the rapidity of the scripting language where possible, and save Java for the heavy lifting.

This is mainly because I feel that Java and JavaFX are not really playing together well enough yet to intermingle them freely. When I can easily call JavaFX classes from Java, gaining from their binding capabilities and easy declaration (or if you want to give me "bind" and "property" keywords in java), THEN the ease of development of JavaFX will make it into Java, and I will mix-and-match to my heart's content.

Best,

Ari

The comments to this entry are closed.