search

patuwwy / ShaderToy-Chrome-Plugin

Web extension for shadertoy.com
https://github.com/patuwwy/ShaderToy-Chrome-Plugin
Other
240 stars 29 forks source link

suggestion: Shader snapshots (history) #25

Open patuwwy opened 7 years ago

patuwwy commented 7 years ago

Save shader current state (code/inputs) on local machine.

It will allow to keep shader history and (view/restore) shader if necessary.

ttoinou commented 5 years ago

An automatic way to connect your shader to a .git would be great

patuwwy commented 5 years ago

You mean private github repository? Sounds nice but requires github account

EthanLowenthal commented 3 years ago

I think ttoinou is suggesting making a local git repository with the shader history. Hard to do in an extention, but possible... There is a pure js implementation of git but it runs on node...

ttoinou commented 3 years ago

Yes ! Would be practical. Or just automatic backups create a history and we can make diffs on our own :)

patuwwy commented 3 years ago

My first idea was to save to the database in the browser, e.g. every 5 minutes, or every successful compilation. With option do save/restore backup to/from file