On Mon, Jul 09, 2001 at 02:07:21PM -0400, Perrin Harkins took time to write:
I think that CGI::FastTemplate does all of that.
Please have a look at it, and see if everything you need is not
already in it.
It's a good module for CGI, since it doesn't rely on caching/compiling
techniques,
At 20:19 09.07.01 +0200, you wrote:
It's your decision, but I think you waste your time while you make all the
experiences the other had made during the last 3-5 years. I think it would
more helpfull if you help to improve the other modules (for example makeing
them easier to install etc.)
Yea, I tried that, but it was still unhappy. There are apparently a
couple of other tweaks that needed to be done. I didn't think too
much about it; after the first error, I went looking for information
and found the patch.
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/textproc/eperl/Makefile
hi, i'm sure many of us have had situations like this,
but that doesn't mean that everyone who wants to do
some templating is going to fall into the same trap
every time.
to clarify what i mean by 'simple':
- trivial to install and to use
- small disk footprint
10 modules total. preferably 1
hi, i'm sure many of us have had situations like this,
but that doesn't mean that everyone who wants to do
some templating is going to fall into the same trap
every time.
The problem is that not every feature comes off looking like a trap.
- trivial to install and to use
It's rare that I need
On Mon, Jul 09, 2001 at 12:00:58PM -0400, [EMAIL PROTECTED] took time to write:
to clarify what i mean by 'simple':
- trivial to install and to use
- small disk footprint
10 modules total. preferably 1
- small memory footprint
this is usually the first bottleneck i see with
I think that CGI::FastTemplate does all of that.
Please have a look at it, and see if everything you need is not
already in it.
It's a good module for CGI, since it doesn't rely on caching/compiling
techniques, just simple regex stuff. It will use a lot less RAM than tools
that compile
to clarify what i mean by 'simple':
- trivial to install and to use
That's important
- small disk footprint
10 modules total. preferably 1
disks are cheap, so it doesn't matter if you take one or two MB
- small memory footprint
this is usually the first bottleneck i see with
On Monday 09 July 2001 20:19, Gerald Richter wrote:
to clarify what i mean by 'simple':
- trivial to install and to use
That's important
Tough some are easy to use and hard to install :) The latter is less
important imho, when a module is hard to install it's usually justified
somehow,
Hi there,
On Sat, 7 Jul 2001, Todd Finney wrote:
We use ePerl for a fair number of things, and I have yet to run into
something we needed of which it was not capable.
Didn't I read somewhere that there were security concerns?
Just asking.
Ditto.
73,
Ged.
At 06:16 PM 7/7/2001 -0700, brian moseley wrote:
On 7 Jul 2001, Randal L. Schwartz wrote:
Yes. Writing a templating system in Perl is trivial.
Writing a *useful* templating system in Perl is
demonstratably hard.
unless you keep application features in a separate layer
from the templating
We use ePerl for a fair number of things, and I have yet to run into
something we needed of which it was not capable. What are you
thinking of?
It's not a question of it not being capable, it's just that most people seem
to choose one of the more full-featured tools. There's lots of talk
on 7/8/01 2:46 AM, Gunther Birznieks at [EMAIL PROTECTED] wrote:
In addition one of the criteria for useful to me is fast. If the
template system is slow, it's quite annoying. However, this goes against
other people's ideas of useful being full featured. As Steven Wright
says (paraphrased) if
At 07:47 AM 7/8/01, Ged Haywood wrote:
On Sat, 7 Jul 2001, Todd Finney wrote:
We use ePerl for a fair number of things, and I have yet to run
into
something we needed of which it was not capable.
Didn't I read somewhere that there were security concerns?
There was a fix made in 1998
At 02:40 PM 7/8/01, Perrin Harkins wrote:
We use ePerl for a fair number of things, and I have yet to run
into
something we needed of which it was not capable. What are you
thinking of?
It's not a question of it not being capable, it's just that most
people seem
to choose one of the
On Sat, Jul 07, 2001 at 06:00:24PM -0400, Geoffrey Young wrote:
I actually use Text::Template for all my templating (sigh), and have such a
wrapper (save just a bit of custom code). I basically implement the HASH
version and use a PerlInitHandler to set up the substitutions using pnotes.
I
Yes. Writing a templating system in Perl is trivial. Writing a
*useful* templating system in Perl is demonstratably hard.
I too have written a templating system.
About a year ago I wrote a simple module called dbq.pm. It performed
database queries. Basically, you could mock up a simple
. It is intended for someone with
basic templating needs, or for someone who wants a
bare-bones building-block to subclass and to add any
other methods to.
i'd like to use the name Apache::SimpleTemplate.
if anyone wants to see the current pod:
http://peter.nyc.ny.us/simpletemplate/pod.html
all thoughts
yes, i have *yet another* templating mechanism for
mod_perl, and i'd like to add it to CPAN if there are
no major objections.
I hate to be a naysayer, but this doesn't look sufficiently different from
the other options to merit adding it to CPAN. The trouble is, there are
already too many of
I hate to be a naysayer, but this doesn't look sufficiently different from
the other options to merit adding it to CPAN.
hi, thanks for your comments. i was expecting some such
naysaying, and understand your point. but, i still
disagree and think that simplicity *is* a valid
difference. i had
On Sat, 7 Jul 2001 [EMAIL PROTECTED] wrote:
Text::Template probably is the most similar existing
package, but it is not made for mod_perl. someone well-
versed in mod_perl could build a mod_perl wrapper of it
fairly quickly, but they or especially someone new to
mod_perl shouldn't have to.
-Original Message-
From: brian moseley
To: [EMAIL PROTECTED]
Sent: 7/7/01 5:34 PM
Subject: Re: Apache::SimpleTemplate
On Sat, 7 Jul 2001 [EMAIL PROTECTED] wrote:
Text::Template probably is the most similar existing
package, but it is not made for mod_perl. someone well-
versed
On Sat, 7 Jul 2001, brian moseley wrote:
if such a wrapper did exist, would you use it?
if it doesn't, why don't you write one yourself?
maybe.
i did use Text::Template in the first iteration of
this, but it was considerably faster to parse the
templates internally. (i don't remember how
At 06:10 PM 7/7/01, Perrin Harkins wrote:
if i'm not mistaken, Apache::ePerl builds a new
interpreter, which also seems like overkill for many
needs.
It's pretty easy to install, really. However, it's not very popular
these
days because it doesn't have all the features people end up
On 7 Jul 2001, Randal L. Schwartz wrote:
Yes. Writing a templating system in Perl is trivial.
Writing a *useful* templating system in Perl is
demonstratably hard.
unless you keep application features in a separate layer
from the templating system (eg the servlet api ;)
25 matches
Mail list logo
