Add more flexible and evolved save/load system

[kaosat-dev]

Save to & load from:

• browser
• local file system
• gist

[kaosat-dev]

For now, there will only be:

• browser (localstorage)
• dropbox

Gist (actually, github) and local file system support for storage will be added in future versions IF the issues associated with both of them can be solved in a nice and cross browser fashion

• Github API suffers from problematic oauth when In pure client mode
• the various html5 filesystem apis are not quite stable enough yet (except in Google Chrome)

[jwygralak67]

Aren't the mechanics of downloading a file, to save it, and PUTing a file to load it reasonably generic?

Perhaps not, since you're dealing with a client-side memory resident object rather than a server side file.

[kaosat-dev]

Jim, unfortunately that is not the case : as you say it yourself: for now this is all purely client side, so it is somewhat limiting what I can / cannot do. The various authentication systems in different cloud based storage systems also don't always help.

I will very likely have a small optional back end (python or nodejs) that people can install (hint, on their Raspberry Pi for example :) to serve files more easily.

[daprice]

What about using the remoteStorage protocol from http://remotestorage.io? It allows saving to any server that supports it (ideally one's own personal server) from client side.

[kaosat-dev]

Hello Daprice ! Sorry for the late reply. Remotestorage actually seems really nice ! I have looked at the docs and the various examples they provide , and it seems promising! I'll experiment with their js bindings in a bit to see if there are any obvious shortcomings. Do you use it personally?

[zignig]

Going to be looking into couchdb

[kaosat-dev]

Zignig : great ! Please le me know if you need clarification on anything in the "stores" system : it is in a bad need of cleanup and refactoring so anything I can do to make things simpler just let me know.

[korpx]

+1 for local file system