and on top of that I want people to be able to edit
templates easily in dreamweaver, frontpage, etc
and send templates thru
HTML tidy to be able to always output valid XHTML.
If you are an OO-advocate, you would hide the presentation format in
objects, e.g. Table, String, and Link.
I'm curious though, why you've chosen to implement it as a handler for
XML::Parser rather than as a SAX Handler (or even better, a Filter)? What
SAX buys (among other things) is the ability for folks to invisibly use
whatever XML parser is installed, including a pure Perl implementation.
On Wed, 17 Jul 2002, Jean-Michel Hiver wrote:
My only problem deals with template caching. Currently Petal does the
following:
* Generate events to build a 'canonical' template file
* Convert that template file to Perl code
** Cache the Perl code onto disk
* Compiles the Perl code as a
Jean-Michel Hiver writes:
My only problem deals with template caching. Currently Petal does the
following:
* Generate events to build a 'canonical' template file
* Convert that template file to Perl code
** Cache the Perl code onto disk
* Compiles the Perl code as a subroutine
** Caches
I wonder how much code you would save if you wrote the templates in
Perl and let the Perl interpreter do the above.
I recommend that you read this Page:
http://www.perl.com/pub/a/2001/08/21/templating.html?page=2
I'm an OO-advocate, I believe in proper separation of logic, content and
Jean-Michel Hiver writes:
I wonder how much code you would save if you wrote the templates in
Perl and let the Perl interpreter do the above.
I recommend that you read this Page:
http://www.perl.com/pub/a/2001/08/21/templating.html?page=2
Please read the Application Servers section of:
On Wed, 17 Jul 2002, Rob Nagler wrote:
Petal lets me do that. If that's not of any use to you, fine. The world
is full of excellent 'inline style' modules such as HTML::Mason,
HTML::Embperl and other Apache::ASP.
These all work on the assumption that the template is written in HTML.
On Wednesday 17 July 2002 22:06, Rob Nagler wrote:
Apologies to those who are tired of the *ML vs. Perl debate.
We might get tired if the vs in there made any sense.
--
Robin Berjon [EMAIL PROTECTED] -- for hire: http://robin.berjon.com/
Windows may be pretty. And easy. But it has no depth
Rob Nagler wrote:
Apologies to those who are tired of the *ML vs. Perl debate.
I think you're confusing the issue. You're not talking about in-line
Perl vs. templating languages, but rather templating vs. a whole
different concept.
Jean-Michel clearly wants to use HTML-based templates, and
Dave Rolsky [EMAIL PROTECTED] wrote:
On Wed, 17 Jul 2002, Rob Nagler wrote:
Petal lets me do that. If that's not of any use to you, fine. The world
is full of excellent 'inline style' modules such as HTML::Mason,
HTML::Embperl and other Apache::ASP.
These all work on the assumption that
At 10:41 AM 07/16/2002 +0100, Jean-Michel Hiver wrote:
Hi list,
I am glad to announce the first release of Petal, the Perl Template
Attribute Language module. You will find a rather copious
documentation here:
http://search.cpan.org/doc/JHIVER/Petal-0.1/lib/Petal.pm
It should be
11 matches
Mail list logo