Re: [htmltmpl] RFC: Template Tag Attributes

[Timm M. <tm...@ag...>]

At 07:23 PM 6/2/04 +0400, Alex Kapranoff wrote:
>   I'd suppose supplying your filter program with a list of exclusions
>(regexps or whatever). If a particular file your program is run
>against is in the list then do not index it. This is much more easier
>compared to tagging all <TMPL_INCLUDE> constructs and is flexible too.
>Think that you could just exclude all qr/_header\.tmpl$/

We wouldn't need to tag all the TMPL_INCLUDE tags.  A reasonable default 
should be "no search".  It's also possible someone will want a given 
include indexed on one page but not anther.


>   And there's of course a question whether you really want to index
>templates which are metadata of your website or its content.

See my reply to Phillip.


>* Timm Murray <tm...@ag...> [June 02 2004, 17:55]:
> > I have a project which involves changing our current pages using SSI
> > #includes into using an HTML::Template-based solution instead.  The
> > question of how to search these templates came up, and I've suggested 
> using
> > htdig:// with a filter program that will convert the templates into text
> > for indexing.
> >
> > Inevitably, there will be certain pages using TMPL_INCLUDE tags.  I 
> imagine
> > that most of these will contain data that will not want to be searched 
> for,
> > such as footers, and therefore my filter program can simply ignore
> > them.  However, I don't feel safe in making the blanket assumption that
> > /all/ included files don't need to be searchable.
> >
> > Is it possible to add a flexible attribute system to the current
> > HTML::Template design?  I'm thinking of something like this:
> >
> > <TMPL_INCLUDE NAME="file.txt" SEARCHABLE="no">
> >
> > The additional attribute(s) could be ignored by HTML::Template, but hold
> > meaning for external programs that need additional information on the
> > template tag.
> >
> > I'm sure it can be done with a filter, but frankly, I think that's a
> > cop-out solution, being that the current filter mechanism does not have a
> > way to hook into HTML::Template's parser.
>
>--
>Alex Kapranoff.
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by the new InstallShield X.
> From Windows to Linux, servers to mobile, InstallShield X is the one
>installation-authoring solution that does it all. Learn more and
>evaluate today! http://www.installshield.com/Dev2Dev/0504
>_______________________________________________
>Html-template-users mailing list
>Htm...@li...
>https://lists.sourceforge.net/lists/listinfo/html-template-users