On Nov 15, 1:10am, Sam Tregar wrote:
Rather, I think that most of the simplicity of HTML::Template comes from
its strictly "one-way" interface. The template file contains only
output-oriented structures.
Indeed. Embedded Perl processors are great for embedding Perl in your
web documents.
On Mon, Nov 15, 1999 at 12:23:29PM -0800, Joshua Chamas wrote:
Leslie Mikesell wrote:
What I'm looking for is a 'nestable' way of handling the logic
flow and HTML construction that will allow a page to be used
as a stand-alone item (perhaps displayed in a frameset) or
included in
Sam Tregar wrote:
The only question I'm really itching to answer is which template system is
fastest? Maybe I should cook up a benchmark suite. I suppose the hardest
part about that will be finding a set of templates/scripts that constitute
roughly equal tasks. What do you all think?
Both Matt Gerald a few
months back suggested they were going to put together a more
realistic benchmark, but don't know where they are with it.
I have started with this job, but my time wasn't eounght to get it to an
point where I can release it. There are so much other things I had to do
On Mon, 15 Nov 1999, Leslie Mikesell wrote:
What I'm looking for is a 'nestable' way of handling the logic
flow and HTML construction that will allow a page to be used
as a stand-alone item (perhaps displayed in a frameset) or
included in another page, but when it is included I'd like to
On Mon, 15 Nov 1999, Joshua Chamas wrote:
Sam Tregar wrote:
The only question I'm really itching to answer is which template system is
fastest? Maybe I should cook up a benchmark suite. I suppose the hardest
part about that will be finding a set of templates/scripts that constitute
Leslie Mikesell wrote:
What I'm looking for is a 'nestable' way of handling the logic
flow and HTML construction that will allow a page to be used
as a stand-alone item (perhaps displayed in a frameset) or
included in another page, but when it is included I'd like to
have the option of
On Sun, 14 Nov 1999, Leslie Mikesell wrote:
I think a lot of unnecessary complexity comes from the fact that
most of the template systems (and apache modules in general) want
to output the html as a side effect instead of accumulating the
page in a buffer or just returning a string containg
On Nov 15, 1:10am, Sam Tregar wrote:
Rather, I think that most of the simplicity of HTML::Template comes from
its strictly "one-way" interface. The template file contains only
output-oriented structures.
Indeed. Embedded Perl processors are great for embedding Perl in your
web
