On Fri, 2009-02-13 at 20:19 -0800, zinckiwi wrote:
> Thanks Malcolm.
>
> > Define "didn't seem to work"?
> > ...
> > Have a look in django/templates/defaulttags.py for examples of argument
> > parsing in the built in tags for Django.
>
> I'm sure it was a gap in my knowledge, since you're obviously right
> about the built-in tags. I'll take a look at them. I was doing
> something like this in the tag's associated Node:
>
> ---
> t = get_template("path/to/template.html")
> c = Context({"forms": [form1, form2]})
> return t.render(c)
> ---
>
> But I couldn't seem to get anything returned. As I say -- gap in my
> knowledge. I've never tried doing templates "manually" like that.
If you're doing that in the render() method, it look roughly correct.
You return a string from that method, which is inserted verbatim into
the template output. To debug that, I would save t.render(c) in a string
and print it out on the console to verify that something is being
generated (as well as returning it to the template). It could well be
that nothing's being rendered for some reason.
> > What problem are you trying to solve here?
> > ...
> > When you're *using* Context, though, the
> > implementation details aren't relevant. You just treat it as a
> > dictionary and you'll be given the most locally scoped value for the key
> > you request.
>
> I had assumed as such when I started. If I recall, the problem I ran
> into treating Context like a dictionary was with this code:
>
> ---
> forms = []
> for key, value in context.items():
> if key == "form" or key.endswith("_form"):
> forms.append(value)
> ---
>
> I tried "context.iteritems()" and just plain "context" but as I recall
> all three errored ("RequestContext' object has no attribute 'items'",
> RequestContext' object has no attribute 'iteritems'" and "need more
> than 1 value to unpack", respectively).
True, it's not a complete dictionary replacement, mostly likely because
all that functionality isn't generally needed (and would be a bit fiddly
to implement). I cut some corners when saying "treat it like a
dictionary". That's true for the normal situation where you're looking
up and/or setting values.
Thing is, it's not particularly usual to iterate over everything in the
context in most situations (and if you look at the source in
django/templates/context.py, a RequestContext is just a tiny subclass of
Context, so it's the latter you need to look at). If you want to do
that, you're going to have to iterate over each dictionary in the
Context.dicts attribute manually (the most local scope if the first item
in that list).
I'd would prefer an "explicit" solution of specifying the forms to
examine directly in the template tag. It will read a bit more cleanly in
three months when you want to debug things, too. You may well end up
with a case of multiple forms on the page and *not* wanting to aggregate
all the errors into one place -- imagine a case like your current
situation plus a separate "contact us" form in a sidebar, say.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
