ttmrichter added on 2010-07-10 06:07:24:
I have to agree with this. Every time I look at trying to amend or clean up any of the HTML/CSS stuff in Fossil I kind of shrink away because it's scattered everywhere. If the HTML/CSS stuff were in one place and treated like, say, a language resource file for i18n it would be easier to update, fix, amend, enhance, etc. Fossil's HTML/CSS handling.

eric added on 2010-07-10 09:50:07:
I think what you are asking for is, in effect, the creation or adoption of a templating language. This would make layout easier at the expense of making functionality changes more difficult (i.e. code _and_ template). A bad idea in my opinion.

CSS is already separate, and it would be good if every HTML object had a class attribute, but that's it.

ttmrichter added on 2010-07-10 10:46:20:
I'm not asking so much for a templating language as just having all the HTML and CSS in one place. Where the code currently has HTML fragments all over the place, I'm advocating keeping the HTML in a single documented resource file (perhaps just a C file with a bunch of named string variables or a hash map with well-known key names) so that it's easier to find the snippets and edit them as needed.