Open bollwyvl opened 6 years ago
What about dexie js as a wrapper around IndexedDB. Creating a contents manager that uses the inbrowser web interface?
yeah, custom contents manager/fs is the right approach. pretty easy to drop in an IDrive implementation, though the ui might be a bit unexpected.
a long-term goal is something that (also) works with IPFS and dat, but indexedb, serviceworker, localstorage is probably a fine initial approach.
either way, getting the kernels access to this stuff is also important, but just being able to get a changed notebook in and out is the biggest value in the near term.
On Sun, Oct 7, 2018 at 10:29 PM Simon Biggs notifications@github.com wrote:
What about dexie js as a wrapper around IndexedDB. Creating a contents manager that uses the inbrowser web interface?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/deathbeds/jyve/issues/37#issuecomment-427708584, or mute the thread https://github.com/notifications/unsubscribe-auth/AACxRPA3uvwliP5ZLxOTn5szPwZ1f83Wks5uiriIgaJpZM4XMKqK .
If Dexiejs was used as an IDrive implementation then the following tool might be used to sync to a server if desired while still keeping a principle of supporting the static use case as front and centre.
Drag-to-upload (or the upload button) and download should work.
This probably means actually solving the contents problem.