I am sorry, I replied before reading the complete version of your post.
>It does, kind of...
I do realize android doesn't use the standard libraries or JVM but from what I gather, its essentially the same thing when it comes to writing code that doesn't involve the native android API so by learning Java I am learning a huge part of android development. I am also aware of javafxports but I would imagine that its capabilities are very limited since you cant create a native UI. It might be good for a game or something similar that doesn't need native controls.
>The JavaFX client documentation is (IMO) high quality and up-to-date.
Maybe I worded that the wrong way. I meant 3rd party resources, tutorials on the web, on youtube. Activity! All I see is some demos that feel like its just some people fooling around with a new toy. I want to see communities, detailed tutorials, recent uploads, custom controls, CSS stylesheets, apps (commercial and free). Something!
>There are discussions like this that I could link to. But personally, I don't find such discussions particularly useful.
Maybe they aren't, but its the only thing I ve got. I dont have any close friends that are software developers (only some who work on specialized computational applications) so my only sense of whats going on here can be gathered by googling all day and reading books. At some point, it doesn't cut it anymore.
>I don't advise that method of deployment...
You see, the reason why I thought that was because the book I am reading (Liang intro comprehensive 10E) presented JavaFX as a means of producing RIA when in fact it seems to be a simple replacement of Swing, just more modern (and I do agree it does feel really modern).
>Depends on the deployment model...
>I disagree, many people develop for Android and iOS.
What I meant was, since theres standard toolkits and API's for android and iOS why would you make a JFX app for those environments in the first place? You cant make a proper (read: native) UI in JFX for android and you can do that with the native API's plus everything else you can do with JFX. Whats the point of writing a JFX app for android unless you could make one single app that ran on both the desktop and mobile and could magically scale to fit the screen size. Thats why I am asking for windows 10. My idea is that since phones will be running full windows, in theory you could make one app that could run on the desktop and the phone/tablet. But still it would have to be aware of the form factor and the usage context (eg, when undocking the surface it goes into tablet mode. The app might need to know that somehow). Now if that works somehow thats great. You have a great platform and a great tool to work with. If not, JFX doesn't provide you with anything you don't already have on the mobile (even less in fact)
>The native platform.....
Again, maybe I should have been more verbose. What I mean by native is using the standard API's for the platform. Native controls, native GUI. Native in this context refers to the standard for developing for a platform. In windows C# VB (and metro apps with HTML intefaces) are native. On android you have the android API, in iOS you have COCOA touch or whatever its called. If you want to make "native" looking metro apps in JFX for instance what can you do? You can get stylesheets that mimic the look, but its not the same. How do you implement the new metro open file window? Thats a ton of work that probably won't pay out. The bottom line is java isn't the standard anywhere. Far from it.
>Oracle no longer support SceneBuilder binary releases.Binary releases are provided by the third party Gluon. Gluon have provided new releases of SceneBuilder within the last year.
I realize that and just yesterday I downloaded the new 64 bit binaries (which don't work on intellij idea for some reason) but the version number is still the same. Is SceneBuilder under active development?
> Lookups are based upon a CSS selector...
I think there's a misunderstanding here. The lookup works just fine. Its when the nodes are referenced through the @FXML declaration that I get the exception.
>I don't think decadence is the word you are looking for here.
Well maybe decadence is too strong a word but it captures the essence of what I am sensing. As Bear Bibeault put it in this thread
"For all I have been able to gather, JavaFX is generally considered DOA. I don't think it's going to have any effect on the mobile space at all. (Or any space at all, for that matter.) "
Thanks alot for your detailed answer. When I read the incomplete version I found to very crass to be honest