JavaFX Watch....on TV

Continuing in yesterday's vein, there's as much to say about JavaFX.

No doubt you saw the first real step towards JavaFX in your living room, with the announcement from Amino Communications to put JavaFX TV in its range of futuristic egg-shaped TV set-top boxes.

There's also been much talk of the new features in JavaFX 1.2, with a typically thoughtful and useful look at the new layout containers from Swing veteran Amy Fowler (and another tutorial here), and a neat feed reader from Jim Weaver here, and a nice blog on the RSS reader capabilities in JavaFX now here.

Since the UK's Guardian newspaper opened up all its news content to developers, there's a new JavaFX tag cloud navigator, accompanied by an interesting writeup of the creator's experiences with JavaFX and comparisons with Flash.

The JavaFX team pushed out a minor 1.2.1 update of the SDK and runtime, containing a number of bug fixes, new samples and performance improvements. Performance continues to be a strong driver for the next release, as you can see from Really Hip Smart Dude Richard Bair's 100,000 node blog.

I did read the blog post (on about the guy's feeling after the Applet in javaFx. Nice post and nice application.
Here are a few extracts from his post ... and my own feeling about those issues.

\*\* 001 : java web development is still to painfull \*\*
[So Flash is deeply embedded into design houses, which have come to rely on some very mature tools in which programming is secondary]
---> Oh yea : a nice tool totaly integrated. For example why is it for example so horrible to write the Applet version of a java-or-javaFx application. In my opinion, the debugging of a JNLP is too difficult. I loose weeks and weeks each time. (see here ). In a way the ANT+JNLP+debuging-and-gessing-process is really a big part of programming an applet. Howcome is that ? Isn't it a 'sabotage' of the java-web-platform-hopes ? Just do at least one thing : JNLP console messages should be much clearer.

\*\* 002 : java-javaFx-applet web usability was-is made by a paranoic who doesn't like standard users \*\*
....[Designers demand a first rate user experience, or else their work won’t sell itself. That means Flash execution doesn’t suffer the popup bombardment of JavaFX.
---> I am just still a bit sick to force the user to "validate" the "yes the applet on" is not a bad thing. "Yea ...I click ok "!.
Why can't we just have a line in JNLP file that just say "Forget-about-java-security-messages-and-let's-be-friend-with-the-applet-users".
If you still think after all these years that those security messages are a good thing than .... well ...say you leave all the nice popular web-application-embeded-in-web-page to Adobe-Flash.
Have you ever think that such a frightning pop up messages will simply scare perhaps 60% of the users who after that gets frighted a virus or worms will eat his machine. Yes man : Flash, html, (perhaps javaFx) is a targeted to non techi guys.
If you want to seduce him, let's imagine it's better not to scare him. Makes sence ?

\*\* 003 : Mac-Apple is going very fine. Bad news : many visual developers are Apple maniacs. sorry \*\*\*
[And it means Flash runs just as well on a Mac as on a PC]
when I present an applet (I use java3D and Swing) to my potantial clients 1 of 2 has a Mac. I am really ambarased. Please Adobe Flash runs on Mac. My dream would be that an Applet would have the same 'chance'. If you could do that I would be more than pleased.

\*\* 003 : Preloaders an urgent simplification is quite urgently welcomed \*\*\*
[And it means component support in JavaFX is lacking where in Flash it’s commonplace. One example of this is the lack of a JavaFX preloader: with Flash it’s standard to have a progress bar as the application loads; with JavaFX the standard preloader is an animated image that continues to animate even if there’s a background error, and I can’t find any code which shows a progress bar. ]
This one is also a big issue. It is not that I dislike the new turning wheel with java logo inside. No, but my users do not care at all. And you know what : It is not my users who decide to choose Flash or javaFx/java stategy. It is me. And I really would like preloaders.
Let's dream a bit : Imagine a line in the JNLP that would say :
<loader: yes> <where:>
Sun internet site (or another url) would have a list of loaders available (class files ? javaFx files ? )
Simple. convenient. No ?
It would be great for us.

\*\* 004 : build to java API to acess javaFx programs \*\*\*
[...JavaFX classes and methods can’t be accessed from Java without a lot of jumping through hoops (you have to create an interface in Java, implement it in JavaFX, and then you can reference that interface in your Java code].
This is really something I hate. javaFx is losing something here. Why not make a java API called javaFxEasyCalling that dramaticaly ease the pain when calling a javaFx programs ?
for example, I would love (and so many Swing developers also I suppose) to integrate just small javaFx buttons, animations inside my existing java swing programs. Today it is almost impossible to do that...
The good thing is that with such an API, java Swing developers could learn javaFx step by step with their day-to-day java-swing job. If that is not a good marketing news ;)? The bad thing is that someone at sun has to build this java API. Yes I know : it is easy to tell people to do things, when execution is so difficult ;)

Anyway, thanks for planetarium site. It makes us developers believe there is a hope for us java-javaFx nerds in the web industry.
But afterall I am positive : We see today Microsoft Bing is finally catching up after google search successfully.
My profound hope is that java-javaFx could do the same.
"Hey man : Just kill those Adobe Flash guys ! "

Posted by Thierry on September 16, 2009 at 06:44 AM PDT #

very very useful machine..that is technology year...

Posted by acne treatment on September 21, 2009 at 12:03 PM PDT #

@Thierry: that's JavaFX, not javaFx...
And although I agree with a number of points, I disagree with your "Forget-about-java-security-messages-and-let's-be-friend-with-the-applet-users". Security messages might be annoying, but are friendly to applet users: allowing to do dangerous things is not what I call "being friendly to users"...
I am uneasy with Flash, allowing to use clipboard data without warning, and to send that data to some foreign Web site without my knowledge... And Java applets can be even more powerful, they can be granted full access to user's hard disk... So, no, thanks.

But now, the security mechanism can be better, offering less ugly dialogs, being triggered only when doing a possibly harmful action (eg. letting play without warning, popping up only if the applet needs to save score on a different Web site), etc.

Posted by Philippe Lhoste on September 24, 2009 at 06:45 PM PDT #

Post a Comment:
Comments are closed for this entry.

A blog all about Java in all its flavors on all client platforms from smartcards to desktops and everything inbetween.


« December 2016