I am very excited to announced that we have posted an early access release of the JavaFX Mobile runtime to enable people to begin developing and running JavaFX applications on real devices! The runtime package is designed for use with select Windows Mobile handsets and also includes the Sun Java Wireless Client, giving you everything you need to get started today. While we've tested (and will be supporting) this package on the HTC Diamond and the LG Incite, you may be able to run it on other Windows Mobile devices as well, although your mileage may vary.
If you purchased an JavaFX-enabled HTC Diamond at JavaOne, we recommend that you update your device to this release. Although not required, you may also want to uninstall your previous release before installing and then make sure you install to "internal storage." We still have more work to do and will be updating this stack again in the future, but go ahead and grab yourself a copy, have fun, and talk to us about it!
Well, It's good to see javafx on phone. But I and million others would like to see something on iPhone.
I know officially it could be a challenge, but look at that java on iPhone project(http://blog.taragana.com/index.php/archive/how-to-install-compile-run-java-on-iphone/), if they can do it, definitely javafx can also be ported. It's matter of porting a compiler and runtime.
Posted by taranfx on July 24, 2009 at 02:26 AM PDT #
Can't believe that you have only released a windows version and not a symbian cldc runtime beta that most of the world can try out.
Posted by buzz on July 24, 2009 at 02:47 AM PDT #
... meant cldc/msa
Posted by buzz on July 24, 2009 at 03:27 AM PDT #
@taranfx: We too would love to see JavaFX available to developers on the iPhone, but as you may appreciate, this is more of a business challenge than a technical one. Apple's Appstore policies prohibit distribution of applications that can run their own applications. Also, we cannot legally support the jailbreaking required to distribute this independently of the Appstore
Posted by Jacob Lehrbaum on July 24, 2009 at 04:19 AM PDT #
This is great, Jacob!(wrote you an email a couple of weeks ago about this)
I have bought an HTC Touch diamond three weeks ago only because I knew Sun would be posting the runtime!
The phone is ,euh, okay but a little bit slow...
Guido
Posted by Guido Amabili on July 24, 2009 at 05:49 AM PDT #
@taranfx: Ahead-of-time compilation solutions cannot support the Java/JavaFX model of application distribution, with apps being downloaded from the net. The best thing you could do (within Apple's license rules) is compiling each individual app into a self-contained native program, including all required runtime, and that would be big and cumbersome, not to mention no support for dynamic runtime features of Java (Apple won't let you have even a hybrid AOT+interpreter/JIT VM).
Posted by Osvaldo Pinali Doederlein on July 24, 2009 at 05:56 AM PDT #
Iphone version will just about never happen, Apple will never allow any other development tracks get apps on it.
A WinMo runtime is .. ok .. I guess. But I would be much more excited about a Symbian, Series60 or Android runtime.
Posted by Pehr on July 24, 2009 at 06:19 AM PDT #
I'd love to see at least an update from Sun on Android JavaFX progress. I certainly appreciate that this is a time-consuming process, but it's the silence that gets a little strange for those of us working on Android development! Just knowing that it's still in the works would be nice. I know it's a different situation in that Google isn't shipping a real Java platform, technically, or Java branding. But it's a heck of a lot better than the iPhone.
But yeah, I'd be really thrilled if some day we could build JavaFX apps that worked across Symbian, WiMo, and Android -- even without the iPhone, even with some additional glue to take advantage of specific APIs on those platforms, even just to port the UI. That'd be well worth e wait.
Posted by Peter Kirn on July 24, 2009 at 07:17 AM PDT #
Heck, than support it inofficially, and let us compile the stuff for Android (and iPhone jailbroken). Sun is great at innovation and stops at the middle of the way.
That's way it's hard to trust in Sun's commitment and I - and lot's of people I know - hesitate in adopting (investing!) in new efforts which are led by Sun.
All politics aside, Android is gaining momentum and and even if it's a realy pity that Sun don't get deserved licensing fees it's important to support it for JavaFX.
I am not sure if iPhone will be *that* important after JavaFX shipping and running on most devices. I guess not.
Posted by Thomas on July 24, 2009 at 11:35 AM PDT #
What's the min Windows mobile version you can use? I tried on 2003 but it wont even install.
Posted by Zammbi on July 25, 2009 at 08:23 AM PDT #
Oh found the info. It's only for Windows Mobile 6. Any chances of supporting lower versions?
Posted by Zammbi on July 25, 2009 at 08:26 AM PDT #
What about SonyEricsson?
I thought SonyEricsson plan to support JavaFX Mobile?
/ove
Posted by Ove Nordström on July 27, 2009 at 12:57 AM PDT #
@Ove
This stack is designed to help developers begin creating JavaFX applications even before some of these companies release their first devices. Now, we can't comment on their schedules, but for information about Sony Ericsson and JavaFX, you try reading this blog on the Sony Ericsson website:
http://blogs.sonyericsson.com/developerworld/tag/javafx/
Also, it seems some people have been able to run the JavaFX Mobile stack on an Xperia as well:
http://fav.or.it/post/1704096/javafx-for-windows-mobile-ea
Posted by Jacob Lehrbaum on July 27, 2009 at 05:07 AM PDT #
From the release notes:
This release implements a set of standard APIs defined through the Java Community Process:
Platform
• Mobile Information Device Profile (MIDP) 2.1 (JSR 118)
• Connected Limited Device Configuration (CLDC) 1.1a (JSR 139)
Optional Packages
• PDA Optional Packages for the J2ME Platform 1.0 (JSR 75)
• Location API for J2ME (JSR 179)
• Wireless Messaging API (WMA) 1.1 (JSR 120)
• SIP API for J2ME (JSR 180)
• Mobile Media API (MMAPI) 1.2 (JSR 135)
• Java Technology for the Wireless Industry 1.0c (JSR 185)
• J2ME Web Services Specification (JSR 172)
• Content Handler API 1.0 (JSR 211)
Interesting.
Posted by Tobias on July 27, 2009 at 11:52 PM PDT #
Interesting, but the font size is waaayy to small on modern WVGA devices like the Touch HD. Is there a way to adjust this?
Posted by VWong on August 02, 2009 at 05:47 AM PDT #
VWong:
is this happening in the AMS or in the Apps itself? The AMS should use the default font size on the device which should be appropriate for the screen resolution. The apps, on the other hand, may have been hard-coded for a smaller screen size.
If you would like to move this to the JavaFX forums, we should be able to get some people to work with you on this:
http://forums.sun.com/category.jspa?categoryID=132
Posted by Jacob Lehrbaum on August 04, 2009 at 04:54 AM PDT #
It is not working with window mobile standard 6.1. I tried on samsung i200.
Posted by Rajesh on August 08, 2009 at 09:15 PM PDT #
working on my moto Q8with wm 6standard
but still buggy i think
all connection ok but cant go full screen. and still have the gradient softkey with no text on it
and opera mini *# keys dont work. others is pretty normal. havent tried games yet.
please fix the opera mini and full screen bug???
also texts are in clear type now!!!!! wooohoooo... i hate using jbed cause of the non clear type font
Posted by john on August 16, 2009 at 02:54 AM PDT #
great posting: thanks for sharing that.
Posted by Mobile Phone on October 01, 2009 at 06:12 AM PDT #
Does this mean the end of lack of JME support on Windows Mobile phones? eek?
Does this mean a windows mobile phone will be equally capable like feature phones regarding JME? (eek again).
Does this mean Sun is taking care of JME on Windows Mobile phones?
Does this mean in a future we won't need bad VMs like JBed anymore?
Posted by mjordan on October 19, 2009 at 04:16 PM PDT #
A WinMo runtime is .. ok .. I guess
best regards.
http://www.mobile-phone.pk
Posted by Phone on October 28, 2009 at 12:24 AM PDT #
Not releasing JavaFX straight away for Symbian is a big mistake. It is really frustrating to get motivated for using JavaFX and then finding out it isn't available on Symbian.
Wouldn't it be possible to simply convert JavaFX to java or straight to class files on the client an then simply deploying that application as a regular MIDP application? At least then all MIDP devices could have used it from the start.
Posted by Erik on November 20, 2009 at 12:03 PM PST #
Javafx I hope to have ready-made tree, table components, there is the ability to flexibly the layout, so that the layout can be relatively free to develop a useful procedure.
I would like to put my jsf program into javafx procedures, so that can have a greater coverage, and better operating experience.
Unfortunately, javafx the loading speed is still too slow, then quick like, and load a simple scenario also appears slower.
If we can, like jsf + ajax, as the scene switches a little faster, it is really great, javafx development needs to be accelerated ah.
Posted by abercrobmie and fitch on November 27, 2009 at 11:55 PM PST #