Thanks for the clarifications everyone. It seems less crazy now ;)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To
I would agree with you about not being able to evaluate arbitrary
expressions is awkward, not to mention surprising, and, because of
unnecessary keyword creep, even adds clutter unnecessarily.
You may wish to take a look at Evoque Templating http://evoque.gizmojo.org/
that allows arbitrary
Hi Chris,
> Just out of curiosity, is there a reason why the templating constructs
> can't evaluate arbitrary expressions? It seems terribly awkward to me
> that {% if %} can only evaluate variable names, while you need the
> separate operator {% ifequals %} to test for equality, and for some
>
Well, if you really need arbitrary logic in your templates, but like the
django template syntax, you should take a look at Mako[0], but it might
require some work in your views.
But this separation of presentation (logic) and (business) logic is
intentional, and if I have understood everything
On Sun, Jul 13, 2008 at 3:01 AM, Chris <[EMAIL PROTECTED]> wrote:
>
> Just out of curiosity, is there a reason why the templating constructs
> can't evaluate arbitrary expressions? It seems terribly awkward to me
> that {% if %} can only evaluate variable names, while you need the
> separate
Just out of curiosity, is there a reason why the templating constructs
can't evaluate arbitrary expressions? It seems terribly awkward to me
that {% if %} can only evaluate variable names, while you need the
separate operator {% ifequals %} to test for equality, and for some
reason it doesn't
6 matches
Mail list logo
