On Mon, 27 Nov 2000, Christoph Reck wrote:
> How about templates/includes to be analog to layouts|navigations|screens
> and have all template stuff at one location from here links could be
> made to the real locations, e.g. `ln -s / templates/includes/root` joke;)
>
> I would guess that normally #includes are done to non-template content,
> and therefore will need additional propietary paths added to the VL.props...
Yes, #include's are for non-VTL content, or VTL content that
is not parsed. If you #include a file with VTL content it will
not be interpreted. Good for VTL tutorials :-)
And there are properties controlling the include paths. You
will be able to have multiple include paths and I would like
to add the ability to selectively turn caching on/off for
each of these paths.
> > Does anyone one have a preference for the directory
> > that will contain a set of standard includes? You
> > can have multiple include paths and caching/non-caching
> > options will be available for each of those paths, but
> > if we can agree on one location within the webapp I
> > can set up that one standard location.
>
> :) Christoph
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
>
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
