JavaFX Script

[Mohammed Yousuff]

Can you please explain what this book focus on... Do we want to be a expert in JS to read this Book ??

[Bear Bibeault]

It'd probably be a better idea to wait until the book promotion is announced before posting questions. In fact, I do not believe that question posted before the announcement are eligible for the drawing.

[Mohammed Yousuff]

welcome James L. Weaver to Javaranch, can you explain me the objectives of this book.

[Ben Souther]

"Mohammed Yousuff M N",
Please check your private messages regarding an important administrative matter.
-Ben

[James Weaver]

The main objective of the book is to teach JavaFX Script. It exists to help build Rich Internet Applications (RIA). I had high hopes in 1995 that the JVM would become ubiquitous. Then the browser wars happened, so the dream of an RIA world degraded into building applications using technologies and protocols (the Web, HTTP, HTML, etc.) that were designed to share scientific information. We then stretched these technologies to be able to accommodate applications, and the result in many cases are applications that are hard to write and maintain. I see JavaFX Script as a way to achieve RIA that fully leverages the power of Java on the client.

[Mohammed Yousuff]

James Weaver Thanks a lot for your detail explanations

[Rahesh Kumar]

Originally posted by James Weaver:
I see JavaFX Script as a way to achieve RIA that fully leverages the power of Java on the client.

Jim,

I am not trying to debate, but just want to get it clarified! Is it not an overhead to push code to client and then execute, rather than a client-server model? I thought that was one of the drawbacks fo the Applet technology!

Kindly clarify! --- many a thanks in advance
[ April 02, 2008: Message edited by: Rahesh Kumar ]

[Ulf Dittmer]

One of the aims of JavaFX (and of the "Consumer JRE") is to address some of the drawbacks of applets. It still makes sense to offload processing to the client; keeping a farm of servers that run web applications is expensive. So it depends on your perspective whether it's a good thing or a bad thing to run code on the client. What's not in doubt is that Java (applets or JavaFX) can provide a richer client environment than HTML/CSS/DOM/JavaScript.

[Rahesh Kumar]

Originally posted by Ulf Dittmer:
One of the aims of JavaFX (and of the "Consumer JRE") is to address some of the drawbacks of applets. It still makes sense to offload processing to the client; keeping a farm of servers that run web applications is expensive. So it depends on your perspective whether it's a good thing or a bad thing to run code on the client. What's not in doubt is that Java (applets or JavaFX) can provide a richer client environment than HTML/CSS/DOM/JavaScript.

@Ulf,

Thanks for replying! Though servers may prove costly to host the web application, offloading can be malicious and vulnerable too, IMHO.
Yeah!! When we see some sample implementation, JavaFX/Applets give some life to the web apps, which the rest of the technologies don't!

For the benefit of others
=========================

Ulf has thrown light on "Consumer JRE"! This is an update to the Java SE 6.
Refer this article for more information!!

[Ulf Dittmer]

offloading can be malicious and vulnerable

I don't really see how. The Java client sandbox is rather more secure than executing JavaScript in a browser.

[Rahesh Kumar]

Originally posted by Ulf Dittmer:

I don't really see how. The Java client sandbox is rather more secure than executing JavaScript in a browser.

Well. At the time of execution, Applets can gain control to the client system's resources, which is little unsafe. In a broswer based application, once scripts and other necessary things are offloaded to the client environment, not the entire functional code.

I had this thoughtfrom some source. What would be the advantage in the security aspect, if it is a sandbox, rather than a browser?

[Pradeep bhatt]

Does the client need to install JDK ? Or it gets downloaded ? How is multiple version of jdk etc handled.

[Pradeep bhatt]

Originally posted by Rahesh Kumar:


Well. At the time of execution, Applets can gain control to the client system's resources, which is little unsafe. In a broswer based application, once scripts and other necessary things are offloaded to the client environment, not the entire functional code.

I had this thoughtfrom some source. What would be the advantage in the security aspect, if it is a sandbox, rather than a browser?

Can you tell us the resosurces over which applets gain control over ? thanks

[Rahesh Kumar]

Originally posted by Prad Dip:


Can you tell us the resosurces over which applets gain control over ? thanks

@Prad,

I am stating what I know of!

There are two models in which applets can be loaded.

1. Loaded from the network.
2. Loaded from the local file system.

"Files" could be one good example of the resource, over which the Applet can take control of. I do accept that fact that Applets cannot ordinarily take control over, or change the file system. They need to be loaded with certain policies. They are called "Signed applets".

[Pradeep bhatt]

Only signed applets can access the files. I dont see any problem here.