Saving Opera Unite service data using File I/O

In this article Keith Johnson takes the blog service example from our original Opera Unite developer's primer, and shows how to modify it so that your blog entries are persisted inside files. This is all done using the magic of the File I/O API.

( Read the article )

If you go through the API Documentation, you may notice some functions named browseFor*. These functions do not work with Unite; you will not be able to use them. The reason for this is that those functions can only be called as the result of a user's action, and with Opera Unite the user is unable to perform any actions directly.

I wish these functions worked in plain widgets, not Unite apps. However they don't work there either. Well, at least they weren't working when Unite was released, and changelogs didn't mention fixing that.