Hi guys, I've got a dilema, that I need some help resolving I think. As you know I've been doing some new concepts for the koha templates, and have (as per usual) inadvertantly done some things that I think involve more than just changing the CSS. Specifically, * on the opac homepage making the language options *not* a drop but instead clickable links * generally re-arranging the "order" things I've also added in some new functionality, but I'm happy to let that go :-) SO my question is a ground level "how do the templates work" If I think there are things "wrong" with the CSS templates, that can't be fixed in styles, what should I do? If I get changes made to the CSS template, what will break? Over the last couple of years there have been some specific aspects of the layout of the pages that clients have consistently wanted changed, and while we did make a version of templates that addressed those issues for 2.0, of course they don't work now with 2.2. There are some issues, which are essentially one of colour, font, size, etc and they are easily addressed. But other issues - where essentially I think something is in the "wrong place" or the "wrong sort of interface" - ie links not drop downs and vice versa - what should I do. I can get it coded into "katipo" templates, but as I understand it, unless Paul you adopt those changes to your templates, when we upgrade, it may all fall appart? Should I "bug" architecture issues with particular pages, and perhaps supply the soloutions? OR is everyone else basically happy with how they are? Help :-) cheers R
Rachel Hamilton-Williams a écrit :
I've got a dilema, that I need some help resolving I think.
I think your problem has no solution... There are 2 things (no, 3) 1 Some lists are "hardcoded" in perl script. Thus, you can't change the template to have a checkbox list, or some links. All those template variable are called CGIxxx (CGIbranch => the list of branches). This is a Perl & template problem that can be solved, but it's quite tricky to have a list with a default value with templates. 2 The general organisation of datas on screen. This is a template problem. If your library want a list of language in top, and another on the bottom left, then you must have a specific template. 3 The colors & fonts & lines/boxes... For those, the CSS template should help (with the opacstylesheet systempreference to have an external css). You can change almost what you want as stylesheet. But a H2 (header 2) will be a H2, everywhere in the code. So, you should say to your customers that the cost depends on what they want exactly. And let them choose (and maybe lower their needs. For example selecting the language with a listbox or a link is not a major difference. -imho-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
participants (2)
-
Paul POULAIN -
Rachel Hamilton-Williams