On 7/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> {% for slave in master.slave_set %}
> {{ slave.init_dict }}
> {{ slave.dict_keyA }}
> {{ slave.dict_keyB }}
> {{ slave.dict_keyC }}
> {% endfor %}
Mmm, if you know which master you'll be dealing with, you could still
have a readied slave_set given to the template context.
If not, you're in template tags territory. :)
The documentation for template tags could use some work, but it's not
that tough to get a handle on.
...
> BTW, I already have the answer to my specific problem, I just
> wanted to push the discussion a bit further, to better
> understand the philosophy behind Django.
I am probably not the best to answer on philosophy except to say that
templates are intentionally simplified so that designers can be
productive without needing to know the difference between
deterministic and non- and between cheap and expensive operations.
:-) I think a template tag would go more with the grain here.
--~--~---------~--~----~------------~-------~--~----~
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 unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
