Feature suggestion: webskin in .znc #654
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/znc#654
Reference in new issue
Block a user
As per the title, I think that allowing a user to place a webskin in .znc/webskins would be a good idea as the user can then easily keep custom skins between versions.
Basically /usr/local/share/znc/webskins/ or /usr/share/znc/webskins/ or $zncInstallationPath/webskins is read from for skins and then .znc/webskins is read and does not override any skins that are in the other locations.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29109612-feature-suggestion-webskin-in-znc?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).-1, if only because there's no guarantee the web skins will work with major version changes. If the entire webskin structure is completely redone, and cleaned up and standardized, then those 'custom skins' can break and then there's other issues. (While I agree partly with the 'it'd be great to keep them from version to version', I disagree because future changes can break functionality of such skins)
The skins should be reworked in such a way that they end up being nothing but CSS files. There is no reason to have HTML/anything else in a skin.