Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serialize and cache state #147

Open
alukach opened this issue Jun 15, 2015 · 0 comments
Open

Serialize and cache state #147

alukach opened this issue Jun 15, 2015 · 0 comments

Comments

@alukach
Copy link
Member

alukach commented Jun 15, 2015

It would be great if DropChop cached its state to the browser to be loaded between usages. This would minimize the pain of accidental reloads and allow users to return to their work if they need to close the app during usage.

To cache state, we will first need to be able to serialize DropChop's state (layers loaded, operations ran). This would be extremely useful if/when we move towards making DropChop states shareable (as outlined in #130, where we would just write the state to a gist or other third-party storage). This may be easier following the completion of #140.

An example of caching state to browser can be seen when using geojson.io, as it prompts a user to "recover your map from the last time you edited?" when you use the app for the not-first time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant