Balazs Ree wrote:
On Mon, 13 Feb 2006 18:59:32 +0100 Martijn Faassen wrote:
Jean-Marc Orliaguet wrote:
I've being working on integrating Balazs Ree's CTAL interpreter recently
(added tests, fixes, etc.). CTAL is the equivalent of TAL but for
javascript.
I just googled around for this, and
Martijn Faassen wrote:
Right, that was my motivation too - I googled around for
javascript-based templating languages but realized there wasn't really
anything. Of course XSLT can be used this way too, but TAL is kinda neat
too. Still, I couldn't think of much practical use for this. Perhaps
Benji York wrote:
Martijn Faassen wrote:
Right, that was my motivation too - I googled around for
javascript-based templating languages but realized there wasn't
really anything. Of course XSLT can be used this way too, but TAL is
kinda neat too. Still, I couldn't think of much practical
Jean-Marc Orliaguet wrote:
[snip description of cross-template communication]
that's an anti-pattern
Agreed.
--
Benji York
Senior Software Engineer
Zope Corporation
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub:
Tonico Strasser wrote:
(Again with the right quote, sorry.)
Jean-Marc Orliaguet wrote:
That's exactly what I'm saying: if templates did not try to create
their own data layer, the 'li_repeat' macro could get the data from
the model (instead it has to rely on cross-template communication)
On 2/13/06, Tonico Strasser [EMAIL PROTECTED] wrote:
Looking forward to see explicit ZPTs soon :)
Me too. I'd also like the macros to be called rather than expanded, so
that any error messages report the error in the macro rather than in
an expanded main template. This should be possible if we
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tonico Strasser wrote:
I'm interested in your opinion about parameters for macros.
Do you think this is explicit enough?:
ul tal:define=list main_navigation
li metal:use-macro=macros/li_repeat/
/ul
Or do you think
In 'normal' tal we often refactor our defines to improve efficiency.
When something is called more than once in a template, we define it at
the beginning, and then use it multiple times. This improves
performance dramatically of course.
kit
--
kit BLAKE
Infrae · infrae.com · +31 10 243 7051
Balazs Ree wrote:
Sat, 11 Feb 2006 21:03:21 +0100 keltezéssel Jean-Marc Orliaguet azt
írta:
I almost felt that something was missing, because I'm so used to inserting
tal:define in page templates. But now I realize that this is a mistake.
There was a discussion recently on the list about
kit BLAKE wrote:
In 'normal' tal we often refactor our defines to improve efficiency.
When something is called more than once in a template, we define it at
the beginning, and then use it multiple times. This improves
performance dramatically of course.
kit
--
kit BLAKE
Infrae · infrae.com ·
--On 12. Februar 2006 19:18:51 +0100 Max M [EMAIL PROTECTED] wrote:
a href=#
tal:attributes=href here/absolute_url;
title here/title;
id here/getId
tal:content=here/TitleTitle/a
I could write this:
a href=here/absolute_url id=here/getId
Andreas Jung wrote:
--On 12. Februar 2006 19:18:51 +0100 Max M [EMAIL PROTECTED] wrote:
a href=#
tal:attributes=href here/absolute_url;
title here/title;
id here/getId
tal:content=here/TitleTitle/a
I could write this:
a
12 matches
Mail list logo