Yes this helps, and it works, sort of. The resulting updated container
is the entire page, minus the actual data.
So I'm wondering, should I use render_to_response (really
HttpResponse) to return the rendered HTML,
or should I use something else in response to the Ajax.Updater
request?
Thanks again.
Ken....
On Oct 2, 5:15 pm, Rock <[EMAIL PROTECTED]> wrote:
> No. Typically you would make a stand-alone template that does not
> extend anything else. This template only renders the contents of the
> container in question. It can be used by your AJAX view to create an
> updated container which can be passed back to the browser. But the
> same template can also be included by a child template (or templates)
> at the appropriate place to perform the original rendering of that
> container on full pages as required. So your child template now
> "includes" this same template:
>
> {% include "my_dynamic_container.html" %}
>
> Hope that helps...
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
