Merric Mercer wrote:
> I'm still a little uncertain of how to put a wrapper around a generic
> view. Given the following code below how does one handle pagination and
> other
> work that generic views does automatically.
>
> from django.views.generic.list_detail import object_list
>
> def generic_wrapper(request):
> qs = Articles.objects.filter(user = request.username)
> return object_list(request, qs)
With the magic of Python you can easily pass all the arguments that were
passed into your wrapper into a generic view without knowing what they are:
def generic_wrapper(request, queryset, *args, **kwargs):
queryset = Article.objects.filter(user=request.username)
return object_list(request, queryset, *args, **kwargs)
A queryset is listed among all the params explicitly because it's easier
to deal with when it's not among either args or kwargs.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
