This should help:
http://www.b-list.org/weblog/2006/nov/16/django-tips-get-most-out-generic-views/
Say you've got this in "yourproj.yourapp.views" (assuming there's a
ForeignKey on Thing2):
from django.views.generic import date_based
from yourproj.yourapp.models import Thing1
from yourproj.yourotherapp.models import Thing2
def your_object_detail_view(request, year, month, day, slug):
q1 = Thing1.objects.all()
q2 = Thing2.objects.filter(thing1__slug=slug, public=True)
params = {
'queryset': q1,
'date_field': 'date_field',
'year': year,
'month': month,
'day': day,
'slug': slug,
'extra_context': {
'sub_thingies': q2
}
}
return date_based.object_detail(request, **params)
This would allow you to pass any related & public stuff from Thing2
into a detail view for Thing1 (assuming your slug_field is called
'slug' and your date_field is called 'date_field).
Hope that helps!
On Thu, Mar 27, 2008 at 10:09 AM, Michael Newman <[EMAIL PROTECTED]> wrote:
>
> I was just messing around with my sites urlconf to keep it organized
> and manage clean things up a bit. I make use of generic views quite a
> bit and they really save me a lot of time. One of the things that I
> noticed however as I was trying to combine a lot of "info_dicts" was
> that the generic views (except archive_day) don't accept extra key
> word arguments.
>
> I realize that passing extra arguments to a function is less than
> ideal, but sometimes it is nice to have one "info_dict" that defines
> paginate, date_field, slug, etc. for model views. Obviously this
> caused problems with a lot of the generic view functions, but that
> easily rectified by adding **kwargs as an extra argument.
>
> I don't know if this is something that would be right to have in the
> default views, but I was interested in starting a conversation to the
> pros and cons to this approach.
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
