Support existing "full themes"

[Madis0]

Assume that a user wants to have a "full theme" like MaterialFox while keeping the flexibility of reStyle.

What if reStyle had an option (automatic check would be harder) to be compatible with that, by keeping everything in chrome folder intact, appending any reStyle userstyles by adding an @include tag that references an external, user-defined file - like reStyle already does for development - and modifying that?

It sounds a bit confusing but overall I mean respecting the current contents of the file, instead of forcing the user to install everything through reStyle.

[NiklasGollenstede]

First off: This should already work, since reStyle only edits/adds its own section in the userChrome.css. Install that theme (by copying); restart Firefox or disable/enable chrome styles in reStyle, which adds reStyles section to the new userChrome.css; restart Firefox; profit.

---

It won't really help with this situation in particular, but it might indeed be nice to place reStyles chrome styles in a seperate, linked file. Or even in its own dir with an index file and individual styles per user style, e.g. as <profileDir>/chrome/reStyle/<styleFileName>-<styleUrlHash>.css.

That shouldn't be too much work, but I have almost no time at the moment.