Hi Dorian, Paul, and everyone else,
I think Dorian has it right here. I have to admit to not having tried this,
but I cant see why it wont work.
Dorian wrote:
So style.css goes to <serverroot>/<theme>/<lang>/styles/
and you can include it with <link rel="stylesheet" type="text/css"
href="">
or with <link rel="stylesheet" type="text/css" href=""themelang">/styles/style.css">
That should work really well. An Paul, the templating mechanism is
completely invivisible to the browser: HTML::Template will get the correct
theme/path setting and put it into the page before it gets sent to the
browser. The stylesheet just has to be in the right place in the filesystem
under the <serverroot> (htdocs directory). The stylesheet line above could
even be in the top include :-)
yes. The problem, for me, was that templates are not on <serverroot>
because, as stated later, the templates where not in koha-html. Now everything
is clear...
On the matter of filesystem structure:
<serverroot>/<theme>/<lang>/
./images
./includes
./styles
./jscripts
./help
./catalogue
./members
./whatever...
This means that each theme is effectively almost a virtual server in
terms of file structure (I think I have this right Dorian?). This would
require a change in current CVS thinking.
This is exactly right. In terms of the existing cvs tree, there has been one
strange development....
All the templates, includes, images etc should be in the above structure
under either:
koha/koha-tmpl/intranet-tmpl/
or
koha/koha-tmpl/opac-tmpl/
The strange thing is that the koha-tmpl tree is in the koha main branch. It
should probably have been in koha-html :-(
I didnt notice fast enough to change it. Maybe later? As for the old
koha-html cvs tree: it dies. slowly, perhaps painfully. But most of that
stuff will be replaced by the new koha-tmpl stuff. We will know when koha is
properly templated when non of the koha-html files is needed.
That's what i noticed and troubled me a lot... now, it's clear...