On 16 December 2013 15:14, Eric Ladner <[email protected]> wrote:
> I know the goal is to not change the upstream trac source, but simple
> things like minor CSS changes, where should those be implemented to not
> affect trac?
>
> Example: in 0.7, when viewing a source file via changeset, the Timestamp,
> Author and Message labels are absolute positioned to the left side of the
> window (very noticeable with a wide monitor). Setting it to "float: left"
> gracefully fixes the problem, but the only way I can seem to get it to take
> effect is by changing diff.css under the trac tree.
>
> Another lower level example.. When viewing change sets, sometimes the
> source path name is extremely long and goes off the screen to the right
> (the header "Changeset # in {product} for {SVN path}". So I figured I'd
> hack in the jQuery TextFill plugin to reduce only the source name to a
> maximum of 1170 pixels (width of current template content area). This
> requires modifying trac/trac/versioncontrol/templates/changeset.html,
> though, which is bad. Plus it hard codes some constants into the source
> like the font height in pixels, the width of the page, etc.
>
> Is there a better way for modifying templates, html, css, etc than going
> back to the trac source?
> --
> Eric Ladner
>
We've got the Bloodhound Theme for changes like that:
https://issues.apache.org/bloodhound/browser/trunk/bloodhound_theme/bhtheme/htdocs
CSS should generally go into the bloodhound.css file. We're not using any
Trac styles at this point, everything comes from that one file.
jQuery plugins could also be added here and via the theme templates:
https://issues.apache.org/bloodhound/browser/trunk/bloodhound_theme/bhtheme/templates
Looking forward to those contributions,
Joe
