openstyles / stylus

Stylus - Userstyles Manager
https://add0n.com/stylus.html
GNU General Public License v3.0
5.45k stars 305 forks source link

[Feature Request] Add a "local versioning" for our Usertyles. #801

Open decembre opened 5 years ago

decembre commented 5 years ago

I don't know if it very clear: I have an userstyle for AMO which lost a little improvement after some other change i made. I don't remember which change affect it and i can't find older version of my userstyle to compare.

Because Userstyles.og don't provide historic of old version , It should be great to keep old version of installed userstyles (without showing them in the active stylus panel). By example, choose which version to keep / delete (as archive) and which should be active (and only visible in the Stylus panel). Like that i can revert back to an older version of an usertyle. PS; Normally i keep an old version before adopt definitively a newer. But that give a very long list of usertyeles which became difficult to manage, so i deleted them.

eight04 commented 5 years ago

Because Userstyles.og don't provide historic of old version , It should be great to keep old version of installed userstyles (without showing them in the active stylus panel).

I didn't get it. How does it relate to USO? Do you mean that if USO supports version history then you don't need this feature?


As a developer, I develop my styles as usercss, which are hosted on Github. Therefore I (and other users) can access old versions easily.

decembre commented 5 years ago

Thanks, but i use always Stylish with Waterfox (yes i know Stylus is better but i find it less usefull for editing a large CSS code). I use Stylus for Chrome and Firefox Quantum only.

And sometime i install some userstyles from Userstyles.org... "As developer" we can use usercss: Yes , but Stylus is new-bee too, no? In an other hand , i make effort to sharing my userstyles and the principal site for that is userstyles.org.

The idea of "a local versioning" (i don't find a better expression with poor english) can be useful for everybody: All in one place (not need to verify in an other place and easy testing). But that's just an idea: i know it's easy to imagine a "Swiss Knife but difficult to make it usable... :-)

narcolepticinsomniac commented 5 years ago

I'm not 100% sure what he's taking about either, but aside from hosting styles on Github, this seems like something which might also relate to a "revision" feature for sync, which I'd be a big fan of.

I doubt that I'd personally find it useful all that often, but it should be a cure-all for any random DB failure or user error. Browser bugs, third-party software, and user error will never stop coming up with new and creative ways to screw with DBs, so redundancy is probably the best option.

All the hosts give you at least a couple/few GBs, which should be plenty to allow for a pretty extensive revision history.

tophf commented 4 years ago

We won't be implementing "local versioning" per se, but we can show a rollback icon in the manager after an update for some time. The duration in days of the old style can be customized in the options, 0 would disable the feature, 7 might be the default value.