Le lundi, 28 juil 2003, à 21:27 Europe/Paris, Jean-Michel Hiver a écrit
:
Also, with TT you have to use the filter 'html' to XML encode your
variables. Petal does it by default, and you need to use the TALES
'structure' keyword to NOT encode.
You don't *have* to use the 'html' filter in TT. I wro
On Mon, 28 Jul 2003, Aleksandr Guidrevitch wrote:
> May be I'm a bit late here... But is there any sence in artifical XML
> templating languages since there is XSLT ? Just wonder whether there are
> cons other than long learning curve and performance issues ?
Well, in the case of just TAL/Petal,
Hi, All
May be I'm a bit late here... But is there any sence in artifical XML
templating languages since there is XSLT ? Just wonder whether there are
cons other than long learning curve and performance issues ?
Alex Gidrevich
I suggest y'all check out Tapestry
http://jakarta.apache.org/tapestry
to see a really nice happy medium. It uses a templating language
similar to TAL but much more flexible (and useful, in my mind) than
rigid XML. All its templates can be used in things like Dreamweaver
and GoLive with getti
> If you like a more straightforward approach, TT also lets you write:
>
>
> $some_content
>
>
> See, I knew there would be something that we would agree on! :-)
:)
> > But at the risk of breaking compatibility with some validators / XML
> > tools / etc.
>
> It still looks like
Jean-Michel Hiver wrote:
> something like:
>
>
>
>
>
> Which is completely impossible to validate and IMHO very hard to read.
Agreed. The following is easier to read, IMHO, and is also valid XML markup.
[% some_content %]
>dir="ltr"
> petal:attributes="ltr language_
Matt Sergeant wrote:
> At it's core, XML is a very elegant syntax for defining a rich dataset
> of nodes
It's a syntax for defining a dataset of nodes that all conform to XML's
ideas about what a dataset of nodes looks like. I'm not convinced about
rich or elegant.
:-)
> > and you find your
On Mon, 28 Jul 2003, Andy Wardley wrote:
> Jean-Michel Hiver wrote:
> > Because Petal templates have to be well-formed XML,
>
> XML syntax is crufty at best.
There's a lot in XML that is needless, but like perl still has a dump()
function, we just say "don't use that then". At it's core, XML is a
> XML syntax is crufty at best. It requires you to be strict and tediously
> correct with every character.
So what. It's not like you can afford to forget that many curly braces
or semicolons (well, except those at the end of a block) with Perl. That
doesn't make it useless does it?
> You have
Jean-Michel Hiver wrote:
> Because Petal templates have to be well-formed XML,
This is the sticking point for me, I'm afraid. I can see some of the
benefits of having templates written in well-formed XML markup, but I
can't see past the drawbacks.
XML syntax is crufty at best. It requires
> > First of all, it is an implementation of TAL. TAL is a very clever open
> > specification for WYSIWYG-friendly templates written by the Zope people.
>
> Do you have a URL for further reading on TAL?
Yep.
http://www.zope.org/Wikis/DevSite/Projects/ZPT/TAL
> > Petal has an active community a
>Do you have a URL for further reading on TAL?
I found one:
http://www.zope.org/Wikis/DevSite/Projects/ZPT/TAL
Regards,
Kitch
> - Original Message -
> From: "Jean-Michel Hiver" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Thursday, July 24, 2003 1:46 PM
> First of all, it is an implementation of TAL. TAL is a very clever open
> specification for WYSIWYG-friendly templates written by the Zope people.
D
> I know everybody's defending their fave templating system... I guess I
> can't resist: I have to jump in and defend my baby :)
>
> So why is Petal better than anything else?
Oops, I got a bit carried away...
As a side note, Petal is probably not "better" than anything else, but
"different". If
> I've been considering using a template system for an app that I'm
> working, but decided against it as the designers who would be putting
> the actual pages together (look n feel) use Adobe GoLive which does
> 'bad things' to non-html stuff (at least in my experience).
I know everybody's defendi
> You missed it:
> http://search.cpan.org/author/SAMTREGAR/HTML-Template-2.6/Temp
late.pm#NOTES
Ah. When the section begins "If you're a fanatic about valid HTML" it
becomes more clear why I missed that. :-)
Thanks,
Fran
[EMAIL PROTECTED] wrote:
Change that to:
You mean don't you? Or did I miss the
secret stealth hide-your-tags-in-html-comments feature? :-)
You missed it:
http://search.cpan.org/author/SAMTREGAR/HTML-Template-2.6/Template.pm#NOTES
- Perrin
003-07-23 4:00 AM
To: Patrick Galbraith
Cc: [EMAIL PROTECTED]
Subject: Re: templating system opinions (axkit?)
On Mon, 21 Jul 2003, Patrick Galbraith wrote:
Anyone on this list use AxKit? I'm curious how it pans out.
I like the idea of XSLT/XML, though I find myself trying to read
What you have created for your own use is almost exactly what HTML::Template does. We have used it for a year without any major problems between us and the HTML designer. Its fast and supports loops and if statements. Its probably worth your while to check it out.
As far as XSLT goes, we're
> Change that to:
>
>
You mean don't you? Or did I miss the
secret stealth hide-your-tags-in-html-comments feature? :-)
-Fran
On Wed, 23 Jul 2003, Hauck, William B. wrote:
> What i've done is just use completely external html files with
> html-compliant comments indicating the data field. (example ). My application just reads in the html
> on startup and does a series of substition statements over the file
> as necessar
k Galbraith
Cc: [EMAIL PROTECTED]
Subject:Re: templating system opinions (axkit?)
On Mon, 21 Jul 2003, Patrick Galbraith wrote:
> Anyone on this list use AxKit? I'm curious how it pans out.
>
> I like the idea of XSLT/XML, though I find myself trying to read between
> the li
Hi Matt,
On Wed, 23 Jul 2003, Matt Sergeant wrote:
> The main reason I like AxKit is it prevents me from screwing up [snip]
> I just write straight perl code. I barely notice that I'm using XML.
Can you give us in a couple of sentences your take on the state of XML
in general and AxKit in parti
On Mon, 21 Jul 2003, Patrick Galbraith wrote:
> Anyone on this list use AxKit? I'm curious how it pans out.
>
> I like the idea of XSLT/XML, though I find myself trying to read between
> the lines of hype vs. something that's actually very useful. I don't know,
> so I don't have any opinions. I do
Hi Jesse,
> -Original Message-
> From: Jesse Erlbaum [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 21, 2003 8:50 PM
> To: 'Patrick Galbraith'
> Cc: [EMAIL PROTECTED]
> Subject: RE: templating system opinions (axkit?)
>
>
> Hi Patrick --
>
> &
On Mon, 2003-07-21 at 12:14, Patrick Galbraith wrote:
> I get so tired of Java types talking about how "perl is just a scripting
> language.. it's not an application platform/server like
> Dynamo/WebSpere/". I even tried to crack
> a particular Orielly java book and was turned off on a statement
"Jesse Erlbaum" <[EMAIL PROTECTED]> wrote:
>It's mostly hype in my experience. And not even very useful hype, like
>Java or PHP, which are actually real things which people might want to
>use.
>
>XSLT seems to be XML geeks' answer to CSS+templating. As if CSS wasn't
>very successful, as if the wo
Anyone on this list use AxKit? I'm curious how it pans out.
I used it for http://www.nikki-site.com (sorry, Japanese-only site).
This site uses exactly 4 pure-mod_perl handlers, and everything else
eventually goes through AxKit (excuse the site design, as far as
development goes that is a one-
Jesse Erlbaum wrote:
Hi Patrick --
I like the idea of XSLT/XML, though I find myself trying to
read between
the lines of hype vs. something that's actually very useful.
I don't know,
so I don't have any opinions. I do know I'd like to use
XSLT/XML so as to
have a project to use it for, henc
Hi Patrick --
> I like the idea of XSLT/XML, though I find myself trying to
> read between
> the lines of hype vs. something that's actually very useful.
> I don't know,
> so I don't have any opinions. I do know I'd like to use
> XSLT/XML so as to
> have a project to use it for, hence learn
Anyone on this list use AxKit? I'm curious how it pans out.
I like the idea of XSLT/XML, though I find myself trying to read between
the lines of hype vs. something that's actually very useful. I don't know,
so I don't have any opinions. I do know I'd like to use XSLT/XML so as to
have a projec
31 matches
Mail list logo
