On Mon, 2005-06-27 at 10:33 -0700, Diwaker Gupta wrote:
> > Without per directory we need three files for every page - bad.
>
> I agree. If Forrest requires me to create 3 files for each page, I'm
> going to be concerned.
>
Yeah, I will try to implement it today.
One question:
<map:match pattern="prepare.view.**">
<map:select type="exists">
<!--
Here we will have to test, whether the requested page needs a
specific view.
This will be assumed as soon there is a .fv
e.g. index.xml + index.fv
-->
<map:when test="{project:content.xdocs}{1}.fv">
<map:generate src="{project:content.xdocs}{1}.fv"/>
</map:when>
Now after this match we need to add the directory default view. How can
I determine the dir part (substring-before the last '/') in that match.
Has somebody an idea?
> > With per directory config we need three files for each directory - good.
>
> And of course, Forrest should always fall back to a default
> configuration should these files be not present. IMHO, per file
> configuration should be made possible (I'm sure there are some use
> cases where this is required), but not mandated; and a per directory
> configuration should be preferred; while the default stays how it is
> now (or something close)
Yes, the default.fv from the view-skin is the ultimate fallback always.
The processing should become:
1) page-specific
2) dir-specific
3) project-default
4) view-skin-default
Views *are* and *should be* fully functional even if the user do not add
any config files. If (s)he provide them they will change the default
behavior.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
