forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: [PATCH] customizable skins, greater configurability, image di r fixes, miscellanea
Date Sat, 14 Sep 2002 09:07:58 GMT
On Fri, Sep 13, 2002 at 05:38:35PM +0400, Piroumian Konstantin wrote:

> > How do you generate breadcrumbs.js? XSLT would be yucky. Perhaps leave
> > the @tokens@ in, and have:
> I mean, that we don't need JavaScript at all to generate those links. Is
> there any hidden meaning in that JS that I have missed or is it just for
> generating the 'global-path' that we can see at the top of every page?

There are 3 optional preset links. Forrest uses them for linking to, then, then the project's own homepage.
They're set with @link1.href@, @link2.href@ etc.

In general, there will always be static parts of a skin that need to be
customized for a project, and tokens seems a decent way to do it.

Another example I just came across is the forrest-site/css/page.css,
which contains:

.menu li  { list-style-image: url('images/label.gif'); font-weight : bold; }
.menu ul ul li .sel { list-style-image: url('images/current.gif'); font-weight : normal; }
.menu ul ul li  { list-style-image: url('images/page.gif'); font-weight : normal; }

Notice those page-relative images :/ It would be nice if we could have
@root@/images/label.gif, and then have @root@ replaced *by the sitemap*
when page.css is requested. Hence the possible necessity of something

> > <map:match pattern="breadcrumbs.js">
> >   <map:read src="skins/.../breadcrumbs.js"/>
> >   <map:transform type="filter">
> >     <map:parameter name="filtersfile" value=""/>
> >   </map:transform>
> > </map:match>
> > 
> > if that's possible..


View raw message