CSS variables so you do not have to diff css templates every time you upgrade

[Bryan Sammers]

1. Use variables in css templates so you do not have to diff them once you upgrade.

[Matt]

Ah. I was wondering how long it would take for this to be raised. It's actually be raised in the past but there is renewed interest because vB4 does this.

Now, I think there is value in the system but I don't think it's worth implementing. We had discussed this at length during development for IP.Board 3. Rikki was pushing for it initially as he saw value in making large colour changes with a single update.

Now, while he was writing the CSS he decided that a variable system would largely be useless as the variable would only be used one or twice in the entire style sheet due to the way it is structured. Add to that the minor inconvenience of having to cache and recache the data each time you change a variable's definition.

Indeed, one could consider the hex code a variable in itself. It takes a moment to search and replace all instances of #123abc, for example.

Having said that, we are planning some 'things' that will make keeping templates and CSS up-to-date post-upgrade much easier.

[Bryan Sammers]

Having said that, we are planning some 'things' that will make keeping templates and CSS up-to-date post-upgrade much easier.

Thanks.Having a unique design is important. The last years I just installed the update and the design was taken care of. IPB would be a big step downwards in that matter. It offers lots of userful stuff on the other hand (url whitelist, IP.Content) that's more than worth considering it, though.

The easiest way may be the automatic three way diff system where the system merges without having the user to interfere. I think there are some public available solutions availabe. Taht would address both style and css changes.