Chrome Web Store

Well as most of you may have heard Google announced the Chrome Web Store at Google I/O.

From the demonstration at the event it seems that its a Web Store done right (unlike the Java Store).

There was an impressive showcase of 3d games powered by Unity3d (the standard web plugin).

I have confirmed with the devs that Java Applets will be supported (as well as any other plugins that runs in the browser, flash, native client, silverlight, etc). Its essentially just a way in which a desktop icon is added to your computer and when clicked will open the browser.

I reckon java applets (using LWJGL or JOGL) could work really well here, if you use a proper certificate users should only get one security dialog which is shown the first time applet is run (which isn’t bad for a one time install).

If the store does well this could be a pretty cool way to monetise java games/apps (would also make sense for Android games/apps as they can share code bases).

Also it looks likely the Web Store will be the main way to install apps on the upcoming ChromeOS (which does run java applets, but atm is unclear if java will be installed by default).

more info and video here

The java games on the PC do have a better future! But for any product, marketing is everything…

What about Java Web Start?

Yeah, what about it? I fail to see the relevance.

I think he means games running in webstart in chrome web store. I don’t see why it would be an issue.

As said by kapta, Chrome Web Store is merely a collection of URLs, so it shouldn’t be a problem. That said, given how horrible Web Start is, nobody should use it.

Its unlikely that java web start is supported, its not real web content and doesn’t run in the browser. JWS is just a text file(xml) that is downloaded and run by an external application.

If you must have something like JWS then its better to go for GetDown, its superior to JWS and just works.

You can use javascript to redirect to the JNLP file, so surely it will work. But again, nobody should do that.

not sure Chrome supports launching or associating jnlp files, it just treat them as downloadable text files.

besides with java’s plagued image, the last thing end users need to see is a java logo or dialog before your app starts :slight_smile:

Chrome Web Store works in every HTML5 enabled browser :slight_smile:

ah, nice :slight_smile:

but yeh jws is a technology best avoided in this use case.

Aw come on, JWS is not that bad.
To be honest I’ve generally had more luck with .jnlp than with applets, especially when it comes to games using OpenGL.

JWS is reliable on a ‘just a hobby’ level. Nothing you’d use for anything commercially.

The caching is bugged, the HTTP connections are flaky at best, and the “it worked the second time”-bug is still around. Not to mention the flooding of the “Add/remove programs” under Windows, the deadlocks while loading the security dialog since 6u19 and blocking-modal-popunder-dialogs when asking for a desktop-shortcut while you’re in FSEM. No doubt I missed a few hundred other issues. Anyway, let’s not derail this thread (too much) and hope the Chrome Web Store will be a stable/reliable deployment method.

I agree with erikd. I am having more luck with Java Web Start than Java Applets. Caching issues with Applets are worse than what I experienced using JWS.

Caching issues can be workarounded by adding (partial) MD5 hash to the filename of each .jar, worked very well for me :slight_smile:

stuff like LWJGL’s Appletloader and GetDown manage their own downloading and caching thus do not suffer from the issue.

Yes, LWJGL Applets work very well. User experience and caching are very good, though it happened that I had to delete the Java pluging cache to resolve weird class loading bug(s) but I think it doesn’t happen anymore with the latest version of LWJGL applet.

Ok JWS is not perfect, but at least it doesn’t depend on some flaky browser plugin, nor can it crash or freeze the browser, nor do you have to work around grey boxes until everything is loaded.
I’d even go as far as to say I’d rather depend on JWS than on applets, even commercially. Better to be able to say “Well, try again, it usually works the second time” (although it’s been years since the last time I saw that myself) than to have to say “Sorry my game destroyed your hard work when it crashed your browser”. In my experience JWS is far more reliable than applets.

applets use to be truly horrid and JWS was a far superior choice. However I ask that you give them another chance and re-evaluate them.

The changes and fixes that have gone into applets (plus browsers) especially since the Java 1.6.0_10+ release are significant and address almost all the issues you have outlined above.

There is tons of room for improvement but as it stands now applets IMO have advanced to a level where they are now a better and more reliable deployment method then JWS (generally speaking).

This chrome web store has caught me; I’m now regularly checking the chromium blog: http://blog.chromium.org/