On Tue, Mar 4, 2008 at 1:37 PM, Lauri Ahonen <[EMAIL PROTECTED]> wrote:
> Is there a sound technical reason not to add a filter, ie. is there a
> performance penalty involved? Or is there a fundemental problem with the
> design that I had in the first posting? I'm going to be adding this
> functionality to my own copy if the reasons are purely political. For me,
> "we can't think of a good keyword" is not a good reason to leave out
> functionality. Fortunately the open source model is perfect for this kind of
> disagreement :-)
Coming up with an easy way to use it is the key, and making sure that
it doesn't muddy the waters too much; one of the biggest problems
people seem to run into with the template system is assuming that it's
like PHP or Rails' ERB templates, where the host programming language
is just mixed in with HTML (witness people occasionally asking on IRC
why stuff like '{% if foo.bar(baz) / quux > 3 %}' doesn't work). But
of course, Django templates aren't just Python mixed in with HTML, and
that's deliberate.
So there's a fine line to walk here between making it easy and
intuitive, and keeping it from misleading people into thinking "oh,
it's just like the Python equivalent", because it probably won't be in
significant ways.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
