rs.
Is there a way to do this in Django without breaking the abstraction layer?
--
Arnaud
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send e
ey correspond better to the desired layout. This would allow
transfering some such manipulations from views to templates where I
feel they belong more naturally.
If there is an interest for this I can provide the patch and follow
what procedure is customary for django (which I am not familiar wi
es this *layout* decision to take place in the view
unless one writes a custom tag.
Of course this is a more general problem that my suggestion does not
solve completely but it has helped me in some cases to move layout
decisions from views to templates.
--
Arnaud
--~--~-~--~~-
elf doing that a lot too until I thought I'd done it
enough times :)
This is one of the motivations for me to change this : to get clarity
in the template without extra code in the view (code which is only
shuffling around data structures to make them fit with the
rather than the rows.
If people think 1. is good but 2. and 3. are confusing I will be glad
to submit a patch for 1. only. As someone pointed out I can always
have my own custom tags.
then to obtain the same functionality as 2. and 3. one could have as
suggested by Russell above:
2'. {% zi
hey are a widget for, but I don't know how
that would work as several fields can share the same widget.
-- Arnaud
[1] http://www.marooned.org.uk/qmm/games/bingo/new/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups