my dog learned polymorphism*
The moose likes JavaFX and the fly likes [javafx]  confused on javafx status Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Java » JavaFX
Bookmark "[javafx]  confused on javafx status" Watch "[javafx]  confused on javafx status" New topic
Author

[javafx] confused on javafx status

Jesus Angeles
Ranch Hand

Joined: Feb 26, 2005
Posts: 2057
Currently, I am studying javafx.

The sample codes in an older javafx book compiles and runs on the latest javafxpad. The codes include 'removed' javafx items like 'attribute'.

The same code doesnt compile in netbeans 6.7.1 (the latest), and on Eclipse Galileo using plugin.

I am so confused what is going on.

Outside of javafxpad, I cant seem to use Frame, etc., which works well on javafxpad.

I am hoping for any comments; before I lose all my hair on this.
Rob Spoor
Sheriff

Joined: Oct 27, 2005
Posts: 19697
    
  20

We're using the Swing / AWT forum for JavaFX, so moving there.


SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6
How To Ask Questions How To Answer Questions
Gregg Bolinger
GenRocket Founder
Ranch Hand

Joined: Jul 11, 2001
Posts: 15299
    
    6

When you say it doesn't compile, what do you mean exactly? The compile errors may actually tell you what is going on, to some extent. JavaFX changed quite a bit since its first release, including syntax. JavaFX started out as a pure interpreted language and now it is also a compiled language. Unfortunately, some of the syntax is different for each and that is probably what you are running into.

GenRocket - Experts at Building Test Data
Jesus Angeles
Ranch Hand

Joined: Feb 26, 2005
Posts: 2057
An example is the Frame. It used to be like in a package javafx.ui.*. It doesnt exist anymore.

In the Weaver book, it seems that the codes are for older versions. This is although the book was published not that long ago.

I am therefore shifting to a newer book by javafx pioneers - Clarke, Bruno, etc.

Even if the above is the latest, it still warns that the javafx specs may change anytime.

It does however look like I love the way it was before, where the Frame was the at the highest level and the code seems very declarative and xml-like.

We have no choice but to do it the Stage way now.

Happy Javafx-ing!
 
GeeCON Prague 2014
 
subject: [javafx] confused on javafx status