Andreas Jung wrote:
--On 12. Februar 2006 19:18:51 +0100 Max M <[EMAIL PROTECTED]> wrote:
Title
I could write this:
Title
That's really syntactical sugar. The purpose of the tal: names is clearly
to tell the parser to do _something_ with the value of an attribute. Now
should a parser
--On 12. Februar 2006 19:18:51 +0100 Max M <[EMAIL PROTECTED]> wrote:
Title
I could write this:
Title
That's really syntactical sugar. The purpose of the tal: names is clearly
to tell the parser to do _something_ with the value of an attribute. Now
should a parser guess if the value of a
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
On another note, I think that tal:de
Philipp von Weitershausen wrote:
Jim Fulton wrote:
Some recent discussions on the distutils-sig mailing list have
helped me to understand some issues related to the ways we
extend the Zope application server. Traditionally, in Zope 2,
you extended Zope by "dropping" product packages into a spe
Rob Jeschofnik wrote:
Jim Fulton wrote:
In summary, I think we need *both* approaches, as they serve different
needs.
I'd have to agree... so +1
.. but I'd suggest that the application/plugin should have a way of
defining which ways it can (or prefers, if it can't be enforced) to be
includ
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 · +
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
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
Hoeve
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 python expression
