Return-Path: 
 <dev-return-22143-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org>
Delivered-To: apmail-forrest-dev-archive@www.apache.org
Received: (qmail 73755 invoked from network); 13 Jan 2006 11:11:15 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 13 Jan 2006 11:11:15 -0000
Received: (qmail 17194 invoked by uid 500); 13 Jan 2006 11:11:14 -0000
Delivered-To: apmail-forrest-dev-archive@forrest.apache.org
Received: (qmail 17145 invoked by uid 500); 13 Jan 2006 11:11:13 -0000
Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@forrest.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@forrest.apache.org>
List-Post: <mailto:dev@forrest.apache.org>
Reply-To: dev@forrest.apache.org
List-Id: <dev.forrest.apache.org>
Delivered-To: mailing list dev@forrest.apache.org
Received: (qmail 17134 invoked by uid 99); 13 Jan 2006 11:11:13 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jan 2006 03:11:13 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [212.247.154.33] (HELO swip.net) (212.247.154.33)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jan 2006 03:11:11 -0800
X-T2-Posting-ID: sqekuHx5EEXz8PMiWfS+nn/CVSJ13AovswB5l38CkqQ=
X-Cloudmark-Score: 0.000000 []
Received: from [83.180.146.147] (HELO [192.168.2.5])
  by mailfe02.swip.net (CommuniGate Pro SMTP 5.0.2)
  with ESMTP id 85010704 for dev@forrest.apache.org;
 Fri, 13 Jan 2006 12:10:46 +0100
Subject: Re: common.fv not working - have I missed something?
From: Thorsten Scherler <thorsten@apache.org>
To: dev@forrest.apache.org
In-Reply-To: <eab855560601121506q2cb9aa46h@mail.gmail.com>
References: <eab855560601111641l76f4684v@mail.gmail.com>
	 <43C61B05.20301@pcotech.fr> <1137057704.8452.3.camel@localhost>
	 <eab855560601120151n588fe4caj@mail.gmail.com>
	 <eab855560601120210y62b6468by@mail.gmail.com>
	 <1137061785.8452.42.camel@localhost>
	 <eab855560601121506q2cb9aa46h@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Date: Fri, 13 Jan 2006 12:10:44 +0100
Message-Id: <1137150645.8297.19.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.1.1 
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

El vie, 13-01-2006 a las 12:06 +1300, Paul Bolger escribi=C3=B3:
> > > <forrest:css url=3D"styles.css" media=3D"screen" theme=3D"pult"/>
> >
> > Actually that is only interesting for the theme switcher and optional.
>=20
> The dispatcher docs  (howto-structurer-dsl) says
>=20
> (attribute:theme) 3. the theme, "pelt" is the default theme (another
> is the "common" theme). Change this if you are using your own theme.
>=20
> Which to me means 'if you want to use css from a theme other than the
> default set that here'.

=C2=BF? Css actually is just a special contract format. Like always for
common you can reuse the css contract not only in common but as well in
a custom theme.

The only difference is that you are linking to more/other css files in
the {customTheme}.fv. ...and like always in the dispatcher we have
fallbacks implemented.

forrest-trunk/whiteboard/plugins/org.apache.forrest.plugin.output.themer
$ cat locationmap.xml
...
<!-- generic match for theme ressources like css and js. -->
    <!--=20
      {1} name
      {2} extension (note we assume e.g. PATH/css/{1}.css)
      -->
    <match pattern=3D"themes/**.*">
      <select type=3D"exists">
        <location
src=3D"{lm:themer.project.dir}/{project:theme}/{2}/{1}.{2}" />
        <location
src=3D"{lm:themer.project.dir}/{defaults:theme}/{2}/{1}.{2}" />
        <location
src=3D"{project:themer}/resources/themes/{project:theme}/{2}/{1}.{2}" />
        <location
src=3D"{project:themer}/resources/themes/{defaults:theme}/{2}/{1}.{2}" />
        <location
src=3D"{defaults:themer}/resources/themes/{project:theme}/{2}/{1}.{2}" />
        <location
src=3D"{defaults:themer}/resources/themes/{defaults:theme}/{2}/{1}.{2}" />
      </select>
    </match>
...

> In a recent post you wrote about using multiple themes. I didn't
> really understand how this could be done. Could you clarify please.
>=20

=C2=BF? Multiple views can you post what I wrote. You can use one theme at =
a
time. You can switch themes with the branding-theme-switcher.ft on the
fly, but you cannot use multiple views otherwise.

> > > but Forrest ignoring them and just looking in the common/css director=
y.
> >
> > hmm, have you modified your locationmap?
>=20
> No I haven't. Wouldn't redirecting using locationmap be a sort of
> 'bulldozer' solution?

No, with the locationmap you can override everything what I wrote above
and in the other mail about fallbacks in the dispatcher. That means if
you use your custom locationmap you override the core.

> Right at the moment I'm finding the whole theme setting/defining
> procedure quite confusing. =20

Hmm, ....

> Wouldn't it make sense to set the project
> theme in forrest.properties,=20

Yeah that is how it is done.

> and then have all views, css locations
> etc cascade from that unless specifically overridden?=20

see my other mail and this since we have based the dispatcher 100% on
the locationmap you are free to override core behavior very easy.

> This would mean
> you could make a copy of a theme, put it in your project themes/
> directory, set the theme in forrest.properties, and then - barring
> putting an .fv file in your xdocs/ directory - do all theme fiddling
> within the theme copy.

That is exactly how it is working. Remember I wrote:
> > If you do and want a fallback for pult you can
> > a) add it to {yourProject}/.../themes/pult.fv
> > b) add it to {yourProject}/.../xdocs/pult.fv

Now a) is the place where you normally would add it.

salu2
--=20
thorsten

"Together we stand, divided we fall!"=20
Hey you (Pink Floyd)