storage

[tantaman]

For presentations storage, use:

1. FileSystemAPI when available
2. IndexedDB otherwise
3. WebSQL if neither of the two are available
4. finally use LocalStorage if all the above fail.

This will allow us to save images locally instead of uploading them to imgur. The ServiceRegistry can be used to dynamically provide the available storage backend as it used to do for the RemoteStorage and LocalStorage options.

Storage backends should be loaded based on feature detection and NOT browser detection. This will allow us to automatically take advantage of new APIs as they become available in the various browsers or gracefully fall back to other APIs if Chrome kills the FileSystemAPI, for example.

The above paragraph implies that the various storage backends will need to be scanned for existing presentations. Existing presentations will have to be copied out to the selected provider. E.g., if FileSystemAPI becomes available in FF then previous presentations must be copied out of IndexedDB.

[tantaman]

This is being implemented in Strut on: https://github.com/tantaman/Strut/tree/large-local-storage via: https://github.com/tantaman/LargeLocalStorage

[vadi2]

I would like to see the ability to link images to a URL to still be there. It is really helpful to be able to upload images to, for example, Dropbox and then be able to edit them without having to re-insert into the presentation like every other presentation app requries you to.

[tantaman]

Yeah, the ability to link images by URL will still be there.

[wizzor]

Hi, is there any update on this issue? It's the primary blocker from us starting to use Strut more widely.