From f5b7a77d7f8bc22391a4987e1420da06cc374254 Mon Sep 17 00:00:00 2001 From: Dan Scott Date: Fri, 13 Apr 2012 09:59:36 -0400 Subject: [PATCH] Templatizing CSS? Why not! Signed-off-by: Dan Scott --- eg2012_tpac.txt | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/eg2012_tpac.txt b/eg2012_tpac.txt index 4eb2778ab..e4d900547 100644 --- a/eg2012_tpac.txt +++ b/eg2012_tpac.txt @@ -119,7 +119,6 @@ TT Syntax - Conditionals and Loops ------------------------------------------------------------------------------ - Template Toolkit Syntax: I18N ----------------------------- @@ -183,12 +182,14 @@ Overriding Templates Example Common customizations - styles ------------------------------ - * CSS files live in /openils/var/web/css/skin/default/opac/ - * TODO: add a CSS example - - -Common Modifications --------------------- + * CSS lives in `/openils/var/web/opac/css/skin/default/style.css` + ** Could then create variants for each required skin and point + to it from the template overrides + * Or you could template the CSS itself: + . Hack EGWeb.pm to return content-type "text/css" for some file names + . Define colors in templated CSS based on CGI.virtual_host() value + . Change templates/opac/parts/base.tt2 to point to the templated CSS + . Stop maintaining many slight variations of the same CSS Debugging TPAC -------------- -- 2.11.0