Hi Mark,
"Mark Stosberg" <[EMAIL PROTECTED]> wrote...
>
> HTML::Template currently supports 4 formats
> for the input file, with three different APIs
> to specify it [...] I find these more verbose
> and confusing than it needs to be. [...]
> Before proceeding further, I wanted to get
> some feedb
"Damien Clark" <[EMAIL PROTECTED]> wrote:
> I would like to extend HTML::Template to allow the user to implement
> their own arbitrary escape functionality. [...] I am proposing the
> following changes to the HTML::Template API and template format:
>
> . Extend the syntax for to
> include user p
Hi Tim,
Tim Walters <[EMAIL PROTECTED]> wrote:
> We've discovered a problem... [and sent a patch and a test]
Nice catch!
> It would be great if this could be folded into the official
> distribution.
Finding and fixing *and* writing the test... I'm guessing your
contribution will be welcomed!
Hi Dan,
Dan Horne <[EMAIL PROTECTED]> wrote:
> One way is to use H::T filters. You could have something like
> and in your code, and use the filter functionality to remove
> the tags and enclosed content. There will be a performance hit - it
> works okay for me but YMMV
>
> Dan
...? REM?? RE
Jason Purdy <[EMAIL PROTECTED]> wrote:
What I usually do is add another step and instead of stopping at the
template, I pass the template's output into HTML::FillInForm, which is
great for filling out ANY input fields (pop-up menus, etc).
- Jason
+1 to Jason's HTML::FillInForm recommendation.
Has anyone tried this XS implementation of HTML::Template?
http://search.cpan.org/~viy/HTML-Template-Pro-0.50/
I'm interested to hear whether it is really "10-25 times faster" than
pure-perl HTML::Template and/or really 1-3 times faster than H::T with
caching under mod_perl...
-dave
---
Offer Kaye <[EMAIL PROTECTED]> wrote:
> [...] I would like to use it as a regular Perl script, to generate
> static HTML pages. I know this *can* be done, since I tried it on the
> example provided in the documentation. But I'm wondering whether
> HTML::Template is really suitable for this kind of
Gabriel Fortuna <[EMAIL PROTECTED]> wrote:
>
> I want to document how the templates work and which switches
> should be used in the code and where to control my page displays. If I use
> the normal comment style, it shows up in my html source,
obviously.
> Is there any other mechanism that could b
Kenny Smith <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED] wrote:
> > What I really meant was convert the SSI include tag in
> > *run-time* to an HTML include and process it as such. I
> > hope this better explains it.
>
> Hi Roy,
>
> Ah, I understand what you need. Checkout the documentation on
Kenny Smith <[EMAIL PROTECTED]> wrote:
>
> Is the only way to catch the internal H::T errors (like "attempt to
> set parameter 'extra_urls' with a scalar - parameter is not a
> TMPL_VAR!") by doing all of my H::T inside an eval and checking the
> magic error variables?
yes, but not *all* of your
Mike Carlton <[EMAIL PROTECTED]> wrote:
> Does anyone have suggestions on how to cleanly code up a monthly
> calendar application with H::T?
>
> I've currently got a perl script that generates an html table and the
> cell contents -- this works fine, but is a royal pain to update the
> html. So i
"Sam Tregar" <[EMAIL PROTECTED]> wrote:
>
> >
>
> I really don't like putting expressions into the NAME attribute. I think
> EXPR, as used in HTML::Template::Expr, is a better choice.
i don't like having a complex expression in the value of an attribute called
"name", either. if the patch real
12 matches
Mail list logo
