Hi,
I think in that case best solution would be to make TALES more
powerful, but I wonder how much powerful? Should I add math
expressions? String concatenation? Should I allow passing of function
arguments? What the syntax should be like?
Maybe you can find some inspiration from the Nevows
On 25-11-2009 at 08:49:18 tarjei tar...@nu.no wrote:
Hi,
I think in that case best solution would be to make TALES more
powerful, but I wonder how much powerful? Should I add math
expressions? String concatenation? Should I allow passing of function
arguments? What the syntax should be like?
On 24-11-2009 at 23:43:16 Werner li...@mollentze.co.za wrote:
Given this, one can speculate about a more leal-life example, which even
a new TAL user would easily be able to pick up:
option tal:attributes=selected compare:item/value,saved/value
tal:content=item/value/option
Just my 2
Simply because it allows for multiple modifier parameters (of which some
can be optional), which in turn can allow for more flexibility in
certain kinds of modifiers, e.g:
tal:block
tal:content=fullName:name/title,name/first,/name/last/tal:block
Kornel Lesiński wrote:
On 24-11-2009 at
On 25-11-2009 at 11:35:43 Werner li...@mollentze.co.za wrote:
Simply because it allows for multiple modifier parameters (of which some
can be optional), which in turn can allow for more flexibility in
certain kinds of modifiers, e.g:
tal:block
