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

Save state #36

Open
Bilge opened this issue Sep 19, 2019 · 3 comments
Open

Save state #36

Bilge opened this issue Sep 19, 2019 · 3 comments

Comments

@Bilge
Copy link

Bilge commented Sep 19, 2019

If there isn't going to be an import option any time soon, at the very least it would be useful to have client-side saving using localStorage or something. Resetting to default on every page load isn't very user-friendly.

@ciembor
Copy link
Owner

ciembor commented Oct 22, 2019

Hey, I was thinking about rewriting the whole thing to some more modern technology with design patterns I learned since I wrote this. But every time I want to do this I don't have enough time. It would be nice to rewrite the whole thing. I was also thinking about creating backend and storing all generated by users schemes, so people could name them and share. But this would require hosting, so much more problems than just a github page.

@Bilge
Copy link
Author

Bilge commented Oct 22, 2019 via email

@riedel
Copy link

riedel commented Jun 11, 2023

Was stumbling over the same problem. However, please don't add complexity via a backend. IMHO the much easier quickwin would be just encoding the state in the URL. This way people can share any color-schemes easily via a link.

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

3 participants