On Friday, January 12, 2018 at 1:38:12 PM UTC-8, hire....@gmail.com wrote: > > A revisiting of the CSS situation would not only be worthwhile in light of > the many Genshi templates needing reworked with the migration to jinja2, it > would also be good to go through and setup some proper variables in place > for things like color palates that can propagate throughout the site. I'm > in the midst of assembling a Trac instance at work just now, and adjusting > it to match our company style guide involved repeating a lot of separate > individual color value changes. There are also cases in the current setup > where you'll see something like ticket.css overriding the colors from > style.css & trac.css on some of its elements, but not all of them, leading > to incoherently mixed color schemes. > > Similarly, as I've been getting our suite of plugins put together, they > often have their own CSS for their templates that replicate elements of the > default Trac look rather than inheriting it from the style.css,trac.css, or > similar style sheets present in the core trac instance, such that another > round of scrutiny to do things like replace > certain-instances-of-white-but-not-all-of-them have to be done for each > plugin. > > A more coherent inheritance approach would make the whole thing both more > maintainable and more easily extensible. They are supposed to be cascading, > after all. > > I've got a couple of projects coming up this spring that will involve > Bootstrap, and would relish the chance to get to know it better. If you > folks at Logical want to start a Bootstrap-implementing branch, I'd be > happy to join in as well. If it's something that could be merged back in > time for 1.4, it could make the many plugin maintainers needing to update > their templates work that much easier. > > -- Jonathan Laufersweiler > > St. Louis, MO > > Just to repeat here what was said in #11953, rather than creating a branch you'll be better off writing a theme for Trac. If you find things along the way that we can do to improve the experience of adding a them, please let us know. https://trac.edgewall.org/wiki/TracInterfaceCustomization https://trac-hacks.org/wiki/ThemeEnginePlugin
Trac 1.4 is pretty much finished up, but there are some issues that could be addressed for Trac 1.6, even if we don't go so far as to introduce an entirely new theme and/or JS framework. We'd want to look at the tradeoffs of using different frameworks. I've been interested in Vue.js, but haven't spent time with it. - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
