Hey Randal --
Maybe because it competes with OpenInteract, which is far
more established.
I don't really think OI and CGI-App are in competition at all. OI
attempts to be a uber-framework, a la Mason -- or maybe more like
ColdFusion or WebObjects.CGI::Application just focuses on web
I'm curious as to why the combination of CGI::Application and
HTML::Template hasn't taken off ... CGI::Application seems to allow a
software developer to create an entire CGI app that can be stored and
distributed as a module on CPAN, but only a couple such app/modules
have been so added
Dave == Dave Baker [EMAIL PROTECTED] writes:
Dave I'm curious as to why the combination of CGI::Application and
Dave HTML::Template hasn't taken off ... CGI::Application seems to allow a
Dave software developer to create an entire CGI app that can be stored and
Dave distributed as a module
::Application offers out of the box, but it may well end up being
worthwhile to just extend rather than convert. I really appreciate the
simple philosophy that HTML::Template and CGI::Application follow.
One question, how do you judge that OpenInteract is more established? Is
does look like it is actively
On Wed, 23 Jul 2003, Eric wrote:
do it all type of system. That is what made me avoid Mason, it just blew my
head off for complexity. Now it is true, I am looking for a bit more than
There's a fine book about it.
www.masonbook.com
Just an unbiased opinion ;)
-dave
::Application offers out of the box, but it may well end up
being worthwhile to just extend rather than convert. I really appreciate
the simple philosophy that HTML::Template and CGI::Application follow.
OpenInteract definitely does more for you. But it also has (IMO) a
fairly sophisticated way
Dave Rolsky wrote:
There's a fine book about it.
www.masonbook.com
Just an unbiased opinion ;)
Hey, I'd be happy to write a book about OpenInteract ;-)
Chris
--
Chris Winters ([EMAIL PROTECTED])
Building enterprise-capable snack solutions since 1988.
CHANGES
- New Feature: HTML::Template will combine HTML_TEMPLATE_ROOT
environment variable and path option if both are
available. (Jesse Erlbaum)
- New Feature: __counter__ variable now available when
loop_context_vars is set (Simran
CHANGES
- Added support for HTML::Template 2.6's new DEFAULT attribute.
- Added support for HTML::Template 2.6's new __counter__ variable.
- Updated mailing-list information to reflect move from vm.com
to sourceforge.net
- Fixed bug where tmpl_var's with the escape attribute would
cause
This module provides an extension to HTML::Template which allows
expressions in the template syntax. This is purely an addition - all
the normal HTML::Template options, syntax and behaviors will still
work.
Expression support includes comparisons, math operations, string
operations
-31 at 07:13, Sam Tregar wrote:
CHANGES
- New Feature: HTML::Template will combine HTML_TEMPLATE_ROOT
environment variable and path option if both are
available. (Jesse Erlbaum)
- New Feature: __counter__ variable now available when
Greetings.
On Mon, 19 Aug 2002, Pierre Vaudrey wrote:
with the following starnge error (The Title is displayed but not the
vignette.gif file)
[Mon Aug 19 07:22:24 2002] [error] Missing right curly or
square bracket
at /Library/WebServer/Documents/perl/vignette.gif line 1,
at
Le mardi 20 août 2002, à 09:32 AM, Alessandro Forghieri a écrit :
Greetings.
On Mon, 19 Aug 2002, Pierre Vaudrey wrote:
with the following starnge error (The Title is displayed but not the
vignette.gif file)
[Mon Aug 19 07:22:24 2002] [error] Missing right curly or
square bracket
at
this image separate from HTML::Template, just by typing
the URL into your browser?
-sam
I'm trying to run the following HTML::Template simple example :
use HTML::Template;
# open the html template
my $template = HTML::Template-new(filename = treeTest.tmpl);
# fill in some parameters
$template-param(Title = Pierre,IMAGE_SRC = vignette.gif);
# send the obligatory
Pierre Vaudrey wrote:
I'm trying to run the following HTML::Template simple example :
[...]
Could anybody help me to fix it ?
Pierre, you are asking an HTML::Template question at the wrong forum,
seems that this is the place where you want to ask this instead:
http://search.cpan.org/author
HTML::Template::JIT - a just-in-time compiler for HTML::Template
CHANGES
- Added support for case_sensitive option to new().
- Added new print_to_stdout option to new() to have output
printed to STDOUT as it is generated.
- Added support for ESCAPE. Template syntax support is now
HTML::Template - a Perl module to use HTML Templates
CHANGES
2.5
- Doc Fix: added reference to new HTML::Template website at
http://html-template.sourceforge.net
- Bug Fix: global_vars fixed for loops within loops
- Bug Fix: include paths were broken under Windows (David Ferrance
HTML::Template::JIT - a just-in-time compiler for HTML::Template
CHANGES
- Added support for loop_context_vars.
- Added support for global_vars.
- Fixed bug in loop param handling that made loop variables
case-sensitive.
DESCRIPTION
This module provides a just-in-time compiler for HTML
HTML::Template::JIT - a just-in-time compiler for HTML::Template
DESCRIPTION
This module provides a just-in-time compiler for HTML::Template.
Templates are compiled into native machine code using Inline::C. The
compiled code is then stored to disk and reused on subsequent calls.
HTML
CHANGES
- Added register_function() class method add functions globally.
(Tatsuhiko Miyagawa)
- Fixed broken cache mode.
DESCRIPTION
This module provides an extension to HTML::Template which allows
expressions in the template syntax. This is purely an addition - all
the normal HTML
CHANGES
- Fixed bug where numeric functions all returned 1.
(reported by Peter Leonard)
- Improved performance over 300% with a new grammar and expression
evaluator.
- Enhanced grammar to support call(foo 10) syntax.
DESCRIPTION
This module provides an extension to HTML::Template which
random results --
sometimes it would get the right parameters return the correct page
contents, other times it would mangle the parameters but, generally, it
would display an incorrect but valid page (i.e. ask for foo?p=bar and get
back foo?p=blat).
Turns out that a call to 'use HTML::Template
On Mon, 18 Dec 2000, Eric Cholet wrote:
ANNOUNCEMENT: NEW VERSION: HTML::Template 2.1
Does it support ELSIF yet?
Nope, but you can build your own now with the new filter option. I expect
someone to post up an "ELSIF" = "ELSE IF" filter to the HTML::Template
mailinglist any time now.
-sam
ANNOUNCEMENT: NEW VERSION: HTML::Template 2.1
HTML::Template - a Perl module to use HTML Templates
Does it support ELSIF yet?
--
Eric
Hi.
I'm using HTML::Template v2.0, IPC::SharedCache 1.3, IPC::ShareLite 0.08,
Storable 1.0.6. I've discovered that if I turn on the "global_vars" option in
HTML::Template, then Storable cant serialize the template so that it can be
placed in the cache.
e.g.:
my $tmpl = HTML
ANNOUNCEMENT: NEW VERSION: HTML::Template 2.0
HTML::Template - a Perl module to use HTML Templates
CHANGES
2.0
- New Feature: new 'search_path_on_include' option (Jody Biggs)
- New Feature: much requested variable __ODD__ added to set of
loop_context_vars.
- New Feature: new 'no_includes
On Sep 4, 2:46pm, Sam Tregar wrote:
[% FOREACH thing = list %]
a href="[% thing.url %]"b[% thing.name %]/b/a
[% END %]
That isn't really much better, in my opinion. It's still too much of a
departure from the HTML around it.
That's the point. It's not HTML markup so you should make
On Mon, 4 Sep 2000, Marc D. Spencer wrote:
o There are actually 3 groups involved, and separation of function
as much as possible allows the three groups to work independently on
a project without requiring concurrent editing of the same file.
- HTML coders
-
Hi all,
On Tue, 5 Sep 2000, Matt Sergeant wrote:
Thats the whole point of these discussions...
I'm not sure that there's any point to these discussions.
Do you think this one could go off-List now?
73,
Ged.
[EMAIL PROTECTED] (Marc D. Spencer) writes:
I have to chime in a little (also noting that we have drifted a bit
off the original topic...)
While working for a large company as the Chief Architect for the web
group I was faced with the same need to investigate template options
- within
"GWH" == G W Haywood [EMAIL PROTECTED] writes:
GWH Do you think this one could go off-List now?
No; I find it quite useful to help form my own descision on what sort
of templating system to use with mod_perl apps.
Vivek Khera wrote:
"GWH" == G W Haywood [EMAIL PROTECTED] writes:
GWH Do you think this one could go off-List now?
No; I find it quite useful to help form my own descision on what sort
of templating system to use with mod_perl apps.
I'm also finding it useful. There have been many
On Tue, 05 Sep 2000 10:39:37 -0400, Drew Taylor wrote:
I'm also finding it useful. There have been many useful ideas/concepts
thrown about that I intend to use in the template comparison.
Seconded. Lots of useful stuff in this thread, and has been giving me a lot of
information about other
Hi all,
On Tue, 5 Sep 2000, Drew Taylor wrote:
"GWH" == G W Haywood [EMAIL PROTECTED] writes:
GWH Do you think this one could go off-List now?
No; I find it quite useful to help form my own descision on what sort
of templating system to use with mod_perl apps.
I'm also finding it
"G.W. Haywood" wrote:
Hi all,
On Tue, 5 Sep 2000, Drew Taylor wrote:
"GWH" == G W Haywood [EMAIL PROTECTED] writes:
GWH Do you think this one could go off-List now?
No; I find it quite useful to help form my own descision on what sort
of templating system to use with mod_perl
There are several points that we should consider before we can succesfully
compare different templating systems. Performance, Ease of use, Code
maintainability, Learning curve and the "Programming eficiency" (lines of
code you have to write to have your job done) are some (good?) examples.
A
To which HTML::Template responds: "Sure you know Perl, but does the HTML
designer you're working with?" HTML::Template has a simple, HTML-esque
syntax for its template files that is aimed at HTML designers.
I still think that this:
? foreach $name (@names) { ?
Name:
On Mon, 4 Sep 2000, Nelson Correa de Toledo Ferraz wrote:
I agree that one shouldn't put lots of code inside of a template, but
variables and loops are better expressed in Perl than in a "little
crippled language".
You and I are programmers and we agree. However once you move to a larger
"Nelson" == Nelson Correa de Toledo Ferraz [EMAIL PROTECTED] writes:
Nelson And the first one has two major advantages: 1) requires less
Nelson code in the Perl modules and 2) allows designers to know how
Nelson Perl looks like.
Is this a codeword for "share our pain"?
pain"? :)
Perhaps any HTML Template Comparison sheet should also show how to
write a loop like that... I know Template-Toolkit would be a syntax
somewhat in between the two, for example, while Mason would be more
Perl-like.
I've been working with JSPs lately, and I'd use something like:
j
On Mon, 4 Sep 2000, Billy Donahue wrote:
I've been working with JSPs lately, and I'd use something like:
jsp:useBean name="someIterator" type="java.util.Iterator"
dadadada:iterator iterator="%= someIterator %"
table
tr
thName/th
thAddress/th
/tr
hand-off date, i.e.
five days to do fifteen budgeted days' work in order to make the launch date.
I had more success with Sam's HTML::Template package. The sitebuilders
seemed to better understand how to work with its simpler concept, although
I had to stay away from HTML::Template's looping c
On Mon, 4 Sep 2000, Nelson Correa de Toledo Ferraz wrote:
I still think that this:
? foreach $name (@names) { ?
Name: ?=$name? P
Job: ?=$job{$name}? P
? } ?
Is cleaner (well, as much as perl can be :-)) than this:
TMPL_LOOP NAME=EMPLOYEE_INFO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Sep 2000, Matt Sergeant wrote:
That said, I am a mod_perl novice, and I don't know if there's anything
equivalent or better than this in the mod_perl world.
Well to stick the AxKit oar in, yes, of course there's something better...
On Mon, 4 Sep 2000, Matt Sergeant wrote:
You and I are programmers and we agree. However once you
move to a larger shop where you'll find non-programmers
editing templates, the HTML-ish loop looks more sensible
than an entirely new language, unfortunately.
i used to believe this argument. i
HTML template scheme. But infinitely
more powerful.
--
Matt/
Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org | AxKit: http://axkit.org
On Mon, 4 Sep 2000, Billy Donahue wrote:
Which is close enough to HTML that the HTML people
should understand it. You never really have to "break
character" while writing presentation pages. I prefer
the custom tags approach to the embedded code approach..
See, in Java you're better off
On Mon, 4 Sep 2000, Matt Sergeant wrote:
In AxKit your developers design custom "taglibs" that
allow you to design your own tags however you want them
to appear. There's a built in taglib for SQL, which
allows you to produce XML from a DBI database, but
writing taglibs is relatively easy.
brian moseley [EMAIL PROTECTED] writes:
i used to believe this argument. i was all up on the xslt
bandwagon. and then i took the question to our html dept.
and they unanimously preferred perl.
Looking for better paid jobs, I'd guess... ;-)
--
Dave Hodgkinson,
On Mon, 4 Sep 2000, brian moseley wrote:
On Mon, 4 Sep 2000, Matt Sergeant wrote:
In AxKit your developers design custom "taglibs" that
allow you to design your own tags however you want them
to appear. There's a built in taglib for SQL, which
allows you to produce XML from a DBI
,
scary and new.
Or are you talking about XSLT vs Perl? If so then I'd
agree - XSLT is mightily scary compared to a simple HTML
template scheme. But infinitely more powerful.
*raises eyebrow*
please expand on that last comment.
On Mon, 4 Sep 2000, brian moseley wrote:
ah. well anyway, it's ubiquitous, and everybody's got
it. everybody that counts, anyway, imo.
mr bungle redundant .. redundant .. redundant
On Mon, 4 Sep 2000, Nelson Correa de Toledo Ferraz wrote:
I still think that this:
? foreach $name (@names) { ?
Name: ?=$name? P
Job: ?=$job{$name}? P
? } ?
Is cleaner (well, as much as perl can be :-)) than this:
TMPL_LOOP NAME=EMPLOYEE_INFO
enough like what everybody's used to, to not be big,
scary and new.
Or are you talking about XSLT vs Perl? If so then I'd
agree - XSLT is mightily scary compared to a simple HTML
template scheme. But infinitely more powerful.
*raises eyebrow*
please expand on that last comment.
I
"Paul J. Lucas" wrote:
And I still think that:
DIV CLASS="employee_info"
Name: SPAN CLASS="text::name"John Q. Public/SPANBR
Job: SPAN CLASS="text::job"mod_perl guru/SPAN
/DIV
is cleaner still: *pure* HTML (no fake elements)
That's because you're a Perl programmer. The template syntax wasn't
designed for your tastes. It was designed for the HTML designers you will
eventually have to work with - wether while you're actually on the project
or when it moves into maintainance and needs design changes.
That's a
On Mon, 4 Sep 2000, Perrin Harkins wrote:
"Paul J. Lucas" wrote:
And I still think that:
DIV CLASS="employee_info"
Name: SPAN CLASS="text::name"John Q. Public/SPANBR
Job: SPAN CLASS="text::job"mod_perl guru/SPAN
/DIV
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Sep 2000, Paul J. Lucas wrote:
And I still think that:
DIV CLASS="employee_info"
Name: SPAN CLASS="text::name"John Q. Public/SPANBR
Job: SPAN CLASS="text::job"mod_perl guru/SPAN
/DIV
On Mon, 4 Sep 2000, Nelson Correa de Toledo Ferraz wrote:
That's because you're a Perl programmer. The template syntax wasn't
designed for your tastes. It was designed for the HTML designers you will
eventually have to work with - wether while you're actually on the project
or when it
On Mon, 4 Sep 2000, Matt Sergeant wrote:
I was questioning whether or not your HTML people found
Perl easier than some taglib scheme like HTML::Template,
or whether you meant they found it easier than XSLT.
ah yes. xslt vs mason, specifically.
again. With XSLT you can markup your article
On Mon, 4 Sep 2000, Perrin Harkins wrote:
"Paul J. Lucas" wrote:
And I still think that:
DIV CLASS="employee_info"
Name: SPAN CLASS="text::name"John Q. Public/SPANBR
Job: SPAN CLASS="text::job"mod_perl guru/SPAN
/DIV
On Mon, 4 Sep 2000, brian moseley wrote:
On Mon, 4 Sep 2000, Matt Sergeant wrote:
To a HTML monkey, all those curly brackets, question
marks and dollars are magical. All you've done is reduce
some keystrokes. Looks fine to a perl programmer, looks
like a modem init string to a
On Mon, 4 Sep 2000, Billy Donahue wrote:
Great, as long as there's no loops or anything but straight up text
replacement... I don't like this approach at all!
What I showed *was* a loop; read my other follow-up.
What if you need to actually USE the `class' attribute of your HTML
"Paul J. Lucas" wrote:
What about conditionals and loops though?
Wouldn't they break the "preview" ability?
No: for loops, you just get one iteration; for conditionals, you
get the result as if the condition were true.
Thanks for the explanation. I can still think of
On Mon, 4 Sep 2000, Matt Sergeant wrote:
b) We all meet different people. The people I've worked
with, even people proficient in Javascript, flip their
lid when they get forced to look at things like $_ and
regexps when they know of easier systems out there. And
I know what SF is like -
On Mon, 4 Sep 2000, brian moseley wrote:
On Mon, 4 Sep 2000, Matt Sergeant wrote:
b) We all meet different people. The people I've worked
with, even people proficient in Javascript, flip their
lid when they get forced to look at things like $_ and
regexps when they know of easier
I was trying to stay out of this one, but...
brian moseley wrote:
% for my $thing (sort @list) {
a href="% $thing-{url} %"b% $thing-{name} %/b/a
% }
[...]
there are no sophisticated or mysterious constructs in those
examples...
Just two kinds of data structures, hash de-referencing
On Mon, 4 Sep 2000, Perrin Harkins wrote:
I can still think of situtations in applications I've worked on where there
were mutually excusive chunks of HTML that would have looked funny with this
approach, but it gets you about 95% of the way towards a previewing system
for free. Cool.
On Mon, 4 Sep 2000, Perrin Harkins wrote:
Embedded perl is absolutely the best answer sometimes, but don't
underestmate the value of turning your example into this:
[% FOREACH thing = list %]
a href="[% thing.url %]"b[% thing.name %]/b/a
[% END %]
That isn't really much better, in my
On Mon, 4 Sep 2000, Matt Sergeant wrote:
Thats not how SQL taglibs work in things like AxKit and
Cocoon. The taglib generates a data structure, which
gets processed in the next stage of the pipeline (this
is more efficient than it sounds, but the efficiency is
hidden from the user).
oh
On Mon, 4 Sep 2000, Perrin Harkins wrote:
[% FOREACH thing = list %]
a href="[% thing.url %]"b[% thing.name %]/b/a
[% END %]
what's the value? you have to write a parser and then
interpret the instructions. that's what eval() is for! and
your syntax is no prettier or easier to understand
According to Steve Manes:
At 11:26 AM 9/4/00 -0300, Nelson Correa de Toledo Ferraz wrote:
I agree that one shouldn't put lots of code inside of a template, but
variables and loops are better expressed in Perl than in a "little
crippled language".
Your example makes perfect sense to me.
I love this perennial thrash. My 2 cents: don't underestimate the value
of having mobility in the separation of "engineer" and "production" ('HTML
Monkey', as it's been previously referred too, ee ee). Mason's ability to
have components that are all Perl, all FooML or a mix in the two allows
"Paul J. Lucas" wrote:
And I still think that:
DIV CLASS="employee_info"
Name: SPAN CLASS="text::name"John Q. Public/SPANBR
Job: SPAN CLASS="text::job"mod_perl guru/SPAN
/DIV
is cleaner still: *pure* HTML (no fake elements) that
Nah
You do not want the Perl to look like the HTML at all so the HTML
designers aren't confused.
Also - why put so much perl into the page at all?
[- use mymodule.pm -]
Sam Tregar wrote:
On Mon, 4 Sep 2000, Perrin Harkins wrote:
Embedded perl is absolutely the best answer
On Mon, 4 Sep 2000, Eric L. Brine wrote:
Great idea, but just one note; ':' is not legal in CSS class names. In
fact, underscores are not even allowed in CSS class names!
So? They aren't CSS class names. The are in fact legal
class names according to the HTML spec.
I have to chime in a little (also noting that we have drifted a bit
off the original topic...)
While working for a large company as the Chief Architect for the web
group I was faced with the same need to investigate template options
- within the discussion of Build or Buy. And yes, JSP (and
ELB Great idea, but just one note; ':' is not legal in CSS class names.
ELB In fact, underscores are not even allowed in CSS class names!
PL So? They aren't CSS class names.
In the preview mode, they are treated as such, so in effect they are.
Therefore, the document claims does not conform
On Mon, 4 Sep 2000, Eric L. Brine wrote:
ELB Great idea, but just one note; ':' is not legal in CSS class names.
ELB In fact, underscores are not even allowed in CSS class names!
PL So? They aren't CSS class names.
In the preview mode, they are treated as such, so in effect they are.
brian moseley wrote:
On Mon, 4 Sep 2000, Perrin Harkins wrote:
[% FOREACH thing = list %]
a href="[% thing.url %]"b[% thing.name %]/b/a
[% END %]
what's the value?
It's easier for some people to understand and write without help from an
engineer.
you have to write a parser and
t use it?"
To which HTML::Template responds: "Sure you know Perl, but does the HTML
designer you're working with?" HTML::Template has a simple, HTML-esque
syntax for its template files that is aimed at HTML designers. Keep the
Perl in your modules and keep the HTML in your template
and the document will grow. When I
have a draft, I'll post it to the list.
I'm new to this list, and I'd like to make a small contribution to the
HTML Template Comparison Sheet.
I've been using Text::Template for some time now, and I really enjoy using
it because 1) it's fast, 2) it's small, just 28kb
Matt Sergeant wrote:
On Tue, 15 Aug 2000, Gunther Birznieks wrote:
Is there an ETA on when this will be out?
I know everyone is busy, but I just figured I would ask. There have been
hundreds of template messages generated in the last weeks on this topic,
and then it seems to have
Matt Sergeant wrote:
If nobody is working on it, I suggest just getting 1 or 2 paragraph
synopsis from template authors about thier product. Just compile those
together and then let it evolve as people see other people's paragraphs
and think "Hey I should have mentioned X too...".
I would
it to the list.
I'm new to this list, and I'd like to make a small contribution to the
HTML Template Comparison Sheet.
I've been using Text::Template for some time now, and I really enjoy using
it because 1) it's fast, 2) it's small, just 28kb and 3) it uses Perl as
scripting language.
From
On Tue, 15 Aug 2000, Gunther Birznieks wrote:
Is there an ETA on when this will be out?
I know everyone is busy, but I just figured I would ask. There have been
hundreds of template messages generated in the last weeks on this topic,
and then it seems to have gone a bit quiet (as usual).
Whilst we're on the subject of templates, would anyone care to comment
on how they fit with content-negotiated documents? I'm looking at
a document for multiple language using Apache
MultiViews. (index.html.es, index.html.jp etc). Does this even work
with SSI or Apache::SSI?
TIA,
Dave
--
Is there an ETA on when this will be out?
I know everyone is busy, but I just figured I would ask. There have been
hundreds of template messages generated in the last weeks on this topic,
and then it seems to have gone a bit quiet (as usual).
Was someone (or somepersons) committed to doing
On Tue, 15 Aug 2000, Gunther Birznieks wrote:
Was someone (or somepersons) committed to doing this or is the project
seeking volunteers or both?
Drew Taylor [EMAIL PROTECTED] was working on the first cut, and I was
planning to add some things on to that. As with The Guide, I'm sure that
all
NAME
HTML::Template - a Perl module to use HTML Templates
CHANGES
1.4
- New feature: new() option 'shared_cache' enables experimental IPC
shared memory caching!
- TMPL_IF now works on TMPL_LOOP variables.
- Public CVS server available at www.sourceforge.net.
- Bug Fix from Doug Steinwand
NAME
HTML::Template - a Perl module to use HTML Templates
CHANGES
1.3
- Omnibus regex patch from Matthew Wickline: a faster and more robust
parse().
- New tag: TMPL_UNLESS, the opposite of TMPL_IF.
- Numerous bug fixes: mixed-case filenames in includes, recursive
TMPL_INCLUDEs, reporting
ANNOUNCEMENT: NEW VERSION: HTML::Template 1.2.1
NAME
HTML::Template - a Perl module to use HTML Templates
CHANGES
1.2.1
- Added multi-parameter and hash-ref syntax for param() calls.
- Added DTD-compliant !-- TMPL_* -- syntax patch from
Matthew Wickline - Thanks
ANNOUNCEMENT: NEW VERSION: HTML::Template 0.96
NAME
HTML::Template - a Perl module to use HTML Templates
CHANGES
0.96
- Added "ESCAPE=1" option to TMPL_VAR to HTML-escape
variable values. (Peter Marelas, thanks!)
- more bug fixes (David Glasses, Jam
NAME
HTML::Template - a Perl module to use HTML Templates
CHANGES
1.1
- Lifted requirement that TMPL_INCLUDEs be alone on a line
- Added "path" option to new() to manipulate search path for
templates.
- bug fixes
DESCRIPTION
This modul
95 matches
Mail list logo
