Return-Path: 
 <modperl-return-28125-apmail-modperl-archive=apache.org@perl.apache.org>
Delivered-To: apmail-modperl-archive@apache.org
Received: (qmail 15586 invoked by uid 500); 28 Aug 2002 06:51:54 -0000
Mailing-List: contact modperl-help@apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:modperl-help@perl.apache.org>
list-unsubscribe: <mailto:modperl-unsubscribe@perl.apache.org>
list-post: <mailto:modperl@apache.org>
Delivered-To: mailing list modperl@perl.apache.org
Received: (qmail 15565 invoked from network); 28 Aug 2002 06:51:53 -0000
Message-ID: <005901c12f8e$a8d557e0$463b313e@mkdocf3ztot0ep>
From: <jhiver@mkdoc.com>
To: "Narins, Josh" <josh.narins@lehman.com>,
	<modperl@perl.apache.org>
References: <7723AD8015FDD411B13F00508BE31C141193893A@exnyc01.lehman.com>
Subject: Re: Done before?
Date: Tue, 28 Aug 2001 07:57:09 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

> I like XML, but not XSLT.
Same here.

> I like XHTML.
It's only slightly less horrible than HTML but yeah... shame that XHTML 1.1
has to be served as application/xml, which no version of IE supports :-(

> The only XHTML compliant templating/content management system I have
> seen is in Java, it's called Java/XMLC, by enhydra.
Interesting, I'll have to take a look.

> I do not like Java, and I do not like the overall feel from the Java/XMLC
> mailing list.
Hey, Java is cool. It's just that Perl is Way Better :-)

> Before I proceed, are there ANY content management/templating systems that
> RELY EXCLUSIVELY on TAG ATTRIBUTE (name="value") nomenclature
> to allow interaction between template and perl code?

I wrote a module inspired by the Zope Page Template TAL specification [1]
which uses only tag attributes. It can process XML (using XML::Parser)  or
HTML (using HTML::TreeBuilder), and outputs either XML or more
specifically XHTML (for tags like input or br which __HAVE__ to be self
closing)...

The module is called Petal (for Perl TAL). It's on CPAN. [2]. It's still
under
development but it's getting very workable now. There is also a Petal
mailing
list [3].

> Are there any that don't follow that model, but are 100% XHTML compliant?

Petal uses extra attributes which you can declare a namespace for. For
example,
let's say that you have the following object.

package Node;

sub parent();
sub children();
sub id();
sub title();


Here is a fragment of Petal code that could operate on the following
structure:

<h1 petal:content="here/title">Current node title</h1>
<div petal:condition="true:here/children">
  <p>List of child nodes:</p>
  <ul>
    <li id="someDummyID"
         petal:repeat="child here/children"
         petal:content="encode:here/title"
         petal:attributes="id string:${here/id}-node">Dummy node Title for
WYSIWYG editors</li>
    </li>
  </ul>
</div>

You can send this to HTML tidy, or use frontpage and dreamweaver, and
attributes will be
preserved. There are many more features to Petal, but it's all documented as
POD and there
are many use cases on the mailing list archives.

[1] http://www.zope.org/Wikis/DevSite/Projects/ZPT/TAL
[2] http://www.cpan.org/authors/id/J/JH/JHIVER/
[3] http://lists.webarch.co.uk/pipermail/petal/

Cheers,
--
IT'S TIME FOR A DIFFERENT KIND OF WEB
================================================================
  Jean-Michel Hiver - Software Director
  jhiver@mkdoc.com
 +44 (0)114 255 8097
================================================================
VISIT HTTP://WWW.MKDOC.COM - Don't visit http://www.webmatrix.net/