Hi folks,
I have been spending some time looking at the Trac templates and style
sheets, and have a couple of questions:
The style bindings seem to be suffering from "divitis" and "classitis",
as Jeffrey Zeldman calls it (in "Designing with Web Standards"): There
are far too many classes used, and those classes have rather long names
like "br-summary-col" or "wiki-history-link". Properly taking advantage
of CSS contextual selectors should drastically reduce the number of
distinct classes: you'd have selectors like ".browser td.summary" and
".wiki #history :link" instead of the above two examples. On the other
hand -- here comes the "divitis" part -- Trac currently overuses divs
and spans for structures that could more easily (and more semantically
correct) be expressed by using standard HTML tags such as definition
lists.
As I will soon be creating a customization of the Trac layout for our
in-house use of Trac, I'm thinking about cleaning up the templates and
style sheets so that they are more lightweight and easier to work with.
I would love to contribute those changes back to the Trac community.
So the question is: do you think that's a good idea? Would such changes
be accepted by the Trac dev team?
Cheers,
Chris
--
Christopher Lenz
/=/ cmlenz at gmx.de
I have been spending some time looking at the Trac templates and style
sheets, and have a couple of questions:
The style bindings seem to be suffering from "divitis" and "classitis",
as Jeffrey Zeldman calls it (in "Designing with Web Standards"): There
are far too many classes used, and those classes have rather long names
like "br-summary-col" or "wiki-history-link". Properly taking advantage
of CSS contextual selectors should drastically reduce the number of
distinct classes: you'd have selectors like ".browser td.summary" and
".wiki #history :link" instead of the above two examples. On the other
hand -- here comes the "divitis" part -- Trac currently overuses divs
and spans for structures that could more easily (and more semantically
correct) be expressed by using standard HTML tags such as definition
lists.
As I will soon be creating a customization of the Trac layout for our
in-house use of Trac, I'm thinking about cleaning up the templates and
style sheets so that they are more lightweight and easier to work with.
I would love to contribute those changes back to the Trac community.
So the question is: do you think that's a good idea? Would such changes
be accepted by the Trac dev team?
Cheers,
Chris
--
Christopher Lenz
/=/ cmlenz at gmx.de