Java runtime

Feb 17, 2013 at 5:03 PM
Why does it require the java runtime?
Feb 18, 2013 at 3:22 AM
I have added few FAQs around this. Explaining below as well.

In case of 'portable app', all application files are stored on local file system of computer or on a USB. To maintain state of the application across browser refresh and to store data locally - without getting tied to the browser implementation (e.g., WebStorage, WebSQL, etc. stores data within browser reach only, cannot have it on USB or elsewhere) - fluid needs to access local file system where the application is running. For this, it is programmed to use variety of drivers such as FileSystemObject (FSO) on Internet Explorer, XPConnect API on FireFox and bundled Java applet (fsa.jar) on Google Chrome.

For various reasons, at the moment Java applet is set as primary driver and therefore JRE is required.

In case you want framework to access local file system (and eventually to get rid of JRE), you can use a different deployment mode (other than 'portableApp') and set 'isEnableLocalFileSystemAccess' option to false. This will exclude JRE dependency altogether.

As of current build (v0.1.500) though, only 'portableApp' mode is stable and therefore you need JRE for the time being. Soon, when all deployment modes are available, this dependency would go off.
Mar 4, 2013 at 5:27 PM
Update: In version 0.1.842 another IO driver is added which works with Internet Explorer's FileSystemObject ActiveX control. For cases where only IE is used as browser of choice, by changing a security setting in local zone, this driver takes over file system access tasks and dependency on JRE goes away as far as IE is concerned.

Try given example and see how it works. More details are on example page.