Note that this method is not supported for Opera Unite applications.

Calling this function will open a file chooser dialog showing only directories. When the user selects one, the directory is mounted and the given callback is called with a File object representing the directory. If the user cancels the dialog, or if mounting fails, the callback is called with a null argument.

Mount points are by default destroyed whenever the application is closed. If you give the persistent argument as true, the mount point will be remounted the next time the application is started.

The defaultlocation argument is used to specify the initial directory of the dialog.

This function will only be called as a result of direct user interaction, such as a click event or similar. If called from a timeout or a programatically dispatched event, it will be ignored by the runtime.

Mount points are mounted as read-write, so you should take care to protect your data by limiting user's access to it.

Note that this method is not supported for Opera Unite applications.

Calling this function will open a file chooser dialog. When the user selects a file, the file is mounted and the given callback is called with a corresponding File object. If the user cancels the dialog, or if mounting fails, the callback is called with a null argument.

Mount points are by default destroyed whenever the application is closed. If you give the persistent argument as true, the mount point will be remounted the next time the application is started.

The appearance of the dialog can be manipulated with the various arguments to the method. The defaultlocation argument is used to specify the initial directory of the dialog. The multiple argument is used to control whether or not the user can select multiple files. The filter can be given an array of file types such as 'txt', which limits the types of the files the user can select.

If the method is called with multiple set to true, a virtual directory will be created and mounted with the given name, containing the selected files. The callback will be called with the File representing the virtual directory. It is not possible to add further files to this mount point, although you can delete files already in it.

This function will only be called as a result of direct user interaction, such as a click event or similar. If called from a timeout or a programatically dispatched event, it will be ignored by the runtime.

Mount points are mounted as read-write, so you should take care to protect your data by limiting user's access to it.

Note that this method is not supported for Opera Unite applications.

Currently, the selected File is just returned, but not mounted. Consequently, using persistent has no meaning.

Calling this function will open a file chooser dialog whose start location is the location of the given mount point. In this dialog the user may create a new file. A File object is cteated and mounted and the given callback is called with the object. If the user cancels the dialog, or if mounting fails, the callback is called with a null argument.

If the file already exists, a File representing it us sent in the callback. If it doesn't exist, a File object is returned with the exists property set to false. It will be physically created only after it is opened.

Mount points are by default destroyed whenever the application is closed. If you give the persistent argument as true, the mount point will be remounted the next time the application is started.

This function will only be called as a result of direct user interaction, such as a click event or similar. If called from a timeout or a programatically dispatched event, it will be ignored by the runtime.

Mount points are mounted as read-write, so you should take care to protect your data by limiting user's access to it.

Applications that use the File I/O API have access to three special directories:

application

The application directory contains the actual files and directories of the current application accessing the API. For widgets, for example, the config.xml and index.html and other files of the widget are found here. This directory is mounted as readonly.

storage

The storage directory is for storing temporary files and configuration files specific to the application, for example uploaded files. This directory and its contents are persisted until the application is uninstalled.

shared

The shared directory is for sharing data from the regular file system. The directory is typically selected by the user when installing the application.

These directories of the application are not mounted by default. You need to call this method to mount and use them. Once mounted, they are available through the mountPoints property like other mount points. Files and directories under them can be accessed by resolving and using the mountpoint URL protocol as for normal files.

The application directory is always mounted as readonly.

If you do not supply the name argument, the location argument is used as the name of the mount point. They are then available as the mount points storage, application and shared, with paths /storage, /application and /shared respectively.

Note that the shared is mounted as read-write unless the underlying file system defines it to be read-only. You should take care to protect your data by limiting access and checking for exploitable code.