On Sat, 21 Apr 2001, Joachim Zobel wrote:
Hi.
I try to understand why and if this XML/XSL stuff is useful. Is it that
transformations (XSL) of XML to HTML can be used instead of the usual HTML
templates (eg. Template-Toolkit)?
Partly. But XSLT is also able to transform documents, which
Matt Sergeant [EMAIL PROTECTED] writes:
The one thing I think AxKit does really well, that other
templating solutions aren't really designed for, is allowing you
to build your whole web site with that solution. So for example,
Mason and EmbPerl are really great for building the dynamic parts
On 23 Apr 2001, Michael Alan Dorman wrote:
Errr, respectfully, I think you underestimate Mason's capabilities.
Not really. I've researched Mason quite a bit, and I talk with Jon every
ApacheCon/OSSCON about how we can bring together the Mason and AxKit
synergy. Now Jon has been to my talk, we
Matt Sergeant [EMAIL PROTECTED] writes:
It depends a *lot* on the type of content on your site. The above
www.dorado.com is brochureware, so it's not likely to need to be
re-styled for lighter browsers, or WebTV, or WAP, or... etc. So your
content (I'm guessing) is pure HTML, with Mason used
Mason and AxKit solve different but related problems. The former a
code-aware component system with process semantics that lend itself to
easily scoping a component's applicability, the latter a transformation
engine. It would be nice to see a framework published that uses the best
of both
Michael Alan Dorman wrote:
Matt Sergeant [EMAIL PROTECTED] writes:
It depends a *lot* on the type of content on your site. The above
www.dorado.com is brochureware, so it's not likely to need to be
re-styled for lighter browsers, or WebTV, or WAP, or... etc. So your
content (I'm
On Mon, 23 Apr 2001, Ian Kallen [EMAIL PROTECTED] wrote:
Mason and AxKit solve different but related problems. The former a
code-aware component system with process semantics that lend itself to
easily scoping a component's applicability, the latter a
transformation engine. It would be
On 23 Apr 2001, Michael Alan Dorman wrote:
Well I will say that you made an excellent point that hadn't really
occured to me---I use XML + XSL for a lot of stuff (the DTD I use for
my resume is a deeply reworked version of one I believe you had posted
at one time), but not web sites, in part
On Mon, 23 Apr 2001, Matt Sergeant wrote:
The alternative of course it to just plug them both
together - AxKit and Mason play nicely together using
Apache::Filter (though it's a bit slow).
with version 2.3 of the java servlet api, you can now create
input and output filters, just like the
Hi.
I try to understand why and if this XML/XSL stuff is useful. Is it that
transformations (XSL) of XML to HTML can be used instead of the usual HTML
templates (eg. Template-Toolkit)? Can this do what a template engine can
do? Where are the limitations? Is there something it can't do?
10 matches
Mail list logo
