On 8/23/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
> * The template system being "dumbed down" for designers? Going to call
> BS on that too. The real complaint here seems to be that the template
> system doesn't include a programming language, and personally I don't
> think it should. If there are things that someone runs into that they
> find themselves needing to use the same custom template tag over and
> over again in many different projects, then that needs to be submitted
> for possible inclusion in the default tags.
>
I don't think this reflects the way django and custom tags are really
used. Looking at the admin code much of it has stuff like {%
output_all "blah" %}. Its all well and good to say that templates
should be pure and should not have a programing language but the
reality is that many people work around this by creating a very tight
coupling between their code and the templates to the point where the
templates no longer specify the layout or styles at all - and piece
together all the objects that the code has assembled. Of course it
greatly depends on the project but I believe that calling tags with
arguments in templates would allow for complex templates that still
stand alone.
Joel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
