On Wed, 2008-03-05 at 11:16 +0200, Lauri Ahonen wrote:
>
>
> On 3/4/08, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
>
> It's also the thin edge of the wedge in some sense: Django's
> templating
> language is intentionally super-simple. Presentation stuff
> only in
> tempates, all selection/business logic in the views. So by the
> time your
> context gets to the template you already know which values are
> going to
> be displayed and don't have to look them up in some other
> variable.
>
>
> Then why "random"? Why "first"? Why "dictsortreversed"? I know
> existing functionality doesn't automaticly justify new functionality,
> but the templates can contain quite a bit of logic already.
The start of your second sentence is very much the point: existing
filters don't make the case for adding new stuff. There's always going
to be more things we can add. You could use that argument to try and
justify adding another 500 filters. There's also never going to be a
clear line about what to add and when not to and will appear to be some
inconsistency. It doesn't matter, since it's so easy to include stuff of
your own that you might want (and to share it with others without
altering core).
Remember that any framework carries with it historical functionality.
That shouldn't be used as an invitation to add more ("first" is purely
presentational, so it's not even related to this).
Malcolm
--
If you think nobody cares, try missing a couple of payments.
http://www.pointy-stick.com/blog/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
